Language Selection

English French German Italian Portuguese Spanish

Interviews

Pi2D2 interview

Filed under
Linux
Interviews
Sci/Tech

It was a pretty long project. I didn’t work on it full time, obviously, but I probably worked on it over a period of six months, and most of the time was writing the software. A lot of the software was written in Python – like the controls for the webcam, the soundboard and everything – so most of the time was getting the software running and getting the kinks worked out. Like where if it loses a Wi-Fi connection it tries to rejoin and things like that. So, yeah, I definitely want to revisit it, and obviously the second time round you can do it a lot better than you did the first, so I’d like to go back.

Read more

How Red Hat is Transforming from a Server-Client to Cloud-Mobile Leader

Filed under
Red Hat
Interviews

Red Hat has become a role model for other companies by writing a success story based on open source software and Linux, without a single proprietary component in the soup.

The company continues to evolve and transform itself with the changing times to remain a leader, and not simply relevant, unlike many other software giants that are struggling in the market.

Read more

Jeffrey McGuire From Acquia Explains Drupal 8, the GPL, and Much More

Filed under
Interviews
Drupal

Jeffrey McGuire

Tux Machines has run using Drupal for nearly a decade (the site is older than a decade) and we recently had the pleasure of speaking with Jeffrey A. "jam" McGuire, Open Source Evangelist at Acquia, the key company behind Drupal (which the founder of Drupal is a part of). The questions and answers below are relevant to many whose Web sites depend on Drupal.

1) What is the expected delivery date for Drupal 8 (to developers) and what will be a good point for Drupal 6 and 7 sites to advance to it?

 

Drupal 8.0.0 beta 1 came out on October 1, 2014, during DrupalCon Amsterdam. It’s a little early for designers to port their themes, good documentation to be written, or translators to finalise the Drupal interface in their language – some things are still too fluid. For coders and site builders, however, it’s a great time to familiarise yourself with the new system and start porting your contributed modules. Read this post by Drupal Project Lead, Dries Buytaert; it more thoroughly describes who and what the beta releases are and aren’t good for: “Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs, and who are prepared to rebuild their test sites from scratch when necessary. Beta releases are not recommended for non-technical users, nor for production websites.”

 

With a full Release Candidate or 8.0.0 release on the cards for some time in 2015, now is the perfect time to start planning and preparing your sites for the upgrade to Drupal 8. Prolific Drupal contributor Dave Reid gave an excellent session at DrupalCon Amsterdam, “Future-proof your Drupal 7 Site”, in which he outlines a number of well-established best practices in Drupal 7 that will help you have a smooth migration when it is time - as well as a number of deprecated modules and practices to avoid.

 

2) What is the importance of maintaining API and module compatibility in future versions of Drupal and how does Acquia balance that with innovation that may necessitate new/alternative hooks and functions?

 

The Drupal community, which is not maintained or directed by Acquia or any company, has always chosen innovation over backward compatibility. Modules and APIs of one version have never had to be compatible with other versions. The new point-release system that will be used from Drupal 8.0.0 onwards - along with new thinking among core contributors and the broader community - may change this in future. There has been discussion, for example, of having APIs valid over two releases, guaranteeing that a Drupal 8 module would still work in Drupal 9 and that a Drupal 9 module would work in Drupal 10. Another possibility is that this all may be obviated in the future as moves toward broad intercompatibility in PHP lead to the creation of PHP libraries with Drupal implementations rather than purely Drupal modules.

 

3) Which Free/libre software project do you consider to be the biggest competitor of Drupal?

 

The “big three” FOSS CMSs – Drupal, Wordpress, and Joomla! – seem to have settled into roughly defined niches. There is no hard and fast rule to this, but Wordpress runs many smaller blogs and simpler sites; Joomla! projects fall into the small to medium range; and Drupal projects are generally medium to large to huge and complex. Many tech people with vested interests in one camp or another may identify another project as “frenemies” and compete with these technologies when bidding for clients, but the overall climate between the various PHP and open source projects is friendly and open. Drupal is one of the largest free/libre projects out there and doesn’t compete with other major projects like Apache, Linux, Gnome, KDE, or MySQL. Drupal runs most commonly on the LAMP stack and couldn’t exist or work at all without these supporting free and open source technologies.

 

NB – I use the term “open source” as synonymous shorthand for “FOSS, Free and Open Source Software, and/or Free/libre software”.

 

4) Which program -- proprietary or Free/libre software -- is deemed the biggest growth opportunity for Drupal?

 

Frankly, all things PHP. Drupal’s biggest growth opportunity at present is its role as an innovator and “meta-project” in the current “PHP Renaissance”. While fragmented at times in the past, the broader PHP community is now rallying around common goals and standards that allow for extensive compatibility and interoperability between projects. For the upcoming Drupal 8 release, the project has adopted object-oriented coding, several components from the Symfony2 framework, a more up-to-date minimum version of PHP (5.4 as of October 2014), and an extensive selection of external libraries.

 

On the one hand, Drupal being at the heart of the action in PHP-Land allows it and its community of innovators to make a more direct impact and spread its influence. On the other hand, it is now also able to attract even more developers from a variety of backgrounds to use and further develop Drupal. A Symfony developer (who has had a client website running on Drupal 8 since summer 2014) told me that looking under the hood in Drupal 8, “felt very familiar, like looking at a dialect of Symfony code.”

 

NB – I use the term “open source” as synonymous shorthand for “FOSS, Free and Open Source Software, and/or Free/libre software”.

5) To what degree did Drupal succeed owing to the fact that Drupal and all contributed files are licensed under the GNU GPL (version 2 or 3)?

 

“Building on the shoulders of giants” is a common thread in free and open source software. The GPL licenses clearly promote a culture of mutual sharing. This certainly applies to Drupal, where I can count on huge advantages thanks to benefitting from more than twelve years of development, 100k+ active users, running something like 2% of the Web for thousands of businesses, and millions of hours of coding and best practices by tens of thousands of active developers. Our code being GPL-licensed and collected in a central repository on Drupal.org has allowed us to build upon the strengths of each other’s work in a Darwinian environment (”bad code dies or gets fixed” - Jeff Eaton) where the best code rises to the top and becomes even better thanks to the attention of thousands of site owners and developers. The same repository has contributed to a reputation economy where bad actors and dubious or dangerous code has little chance of survival.

 

The GPL 2 is business friendly in that the license specifically allows for commercial activity and has been court tested. As a result, there is very little legal ambiguity in adopting GPL-licensed code. It also makes clear cases for when code needs to be shared as open source and when it doesn't (allowing for sites to use Drupal but still have "proprietary" code). The so-called “Web Services Loophole” caused some controversy and discussion, but also opened the way to SaaS products being built on free/libre GPL code. Drupal Project Lead Dries Buytaert explained this back in 2006 (read the full post here):

 

“The General Public License 2 (GPL 2), mandates that all modifications also be distributed under the GPL. But when you are providing a service through the web using GPL'ed software like Drupal, you are not actually distributing the software. You are providing access to the software. Thus, a way to make money with Drupal is to sell access to a web service built on top of Drupal. This is commonly referred to as the web services loophole.”

 

Business models remain challenging in a GPL world; nothing is stopping me from selling you GPL code, but nothing is stopping you from passing it on to anyone else either. App stores, for example, are next to impossible to realise under these conditions. Most Drupal businesses are focused on value add services like site building, auditing and consulting of various kinds, hosting, and so on, with a few creating SaaS or PaaS offerings of one kind or another.

 

NB – I use the term “open source” as synonymous shorthand for “FOSS, Free and Open Source Software, and/or Free/libre software”.

 

6) What role do companies that build, maintain and support Drupal sites play in Acquia's growth and in Drupal's growth?

 

Acquia was the first company to offer SLA-based commercial support for Drupal (a Service Level Agreement essentially says, “In return for your subscription, Acquia promises to respond to your problems within a certain time and in a certain manner”). The specifics of response time and action vary according to the level of subscription, but these allowed a new category of customer to adopt Drupal: The Enterprise.

 

Enterprise adoption – think Whitehouse.gov, Warner Music, NBC Universal, Johnson & Johnson – of Drupal resulted in increased awareness and therefore even further increased adoption (and improvement) of the platform over time. Everyone who delivers a successful Drupal project for happy clients improves Drupal for everyone else involved. The more innovative projects there are, the more innovation flows back into our codebase. The more happy customers there are, the more likely their peers are to adopt Drupal, too. Finally, the open source advantage also comes into play: it behooves Drupal service providers to give the best possible service and deliver the highest-quality sites and results. If they don’t, there is no vendor lock-in and being open source at scale also means you can find another qualified Drupal business to work with if it becomes necessary. Acquia and the whole, large Drupal vendor ecosystem simultaneously compete, cooperatively grow the project (in code and happy customer advocates), and act as each other’s safety net and guarantors.

 

NB – I use the term “open source” as synonymous shorthand for “FOSS, Free and Open Source Software, and/or Free/libre software”.

 

7) How does Acquia manage and coordinate the disclosure of security vulnerabilities, such as the one disclosed on October 15th?

Acquia as an organisation is an active, contributing member of the Drupal community and it adheres strictly to the Drupal project’s security practices and guidelines, including the Drupal project’s strict procedure for reporting security issues. Many of Acquia’s technical employees are themselves active Drupal contributors; as of October 2014, ten expert Acquians also belong to the Drupal Security Team. Acquia also works closely with other service providers, whether competitors or partners, in the best interests of all of us who use and work with Drupal. This blog post, “Shields Up!”, by Moshe Weizman explains how Acquia, in cooperation with the Drupal Security Team and some other Drupal hosting companies, dealt with the recent “Drupalgeddon” security vulnerability.

Free software hacker on open source telemetry project for OpenStack

Filed under
Interviews
OSS

Julien Danjou is a free software hacker almost all of the time. At his day job, he hacks on OpenStack for eNovance. And, in his free time, he hacks on free software projects like Debian, Hy, and awesome. Julien has also written The Hacker's Guide to Python and given talks on OpenStack and the Ceilometer project, among other things.

Prior to his talk at OpenStack Summit 2014 in Paris this year, we interviewed him about his current work and got some great insight into the work going on for the Ceilometer project, the open source telemetry project for OpenStack.

Read more

Interview with Rose Morgan

Filed under
KDE
Interviews

Well, since I started using linux- about the start of this year. And I love them! I like how people work together and it has a sense of community rather than “here’s this stupidly overpriced piece of software and hahaha we don’t care about you or your opinions about it.”

Read more

Q&A: Jackie Yeaney at Red Hat Decodes Open Source

Filed under
Red Hat
Interviews

Advertising Age: Where did the name Red Hat come from?
Ms. Yeaney: Red Hat co-founder Marc Ewing, who developed a Linux operating system distribution product that eventually became Red Hat, attended Carnegie Mellon University. When he was on campus, he used to wear a red cap his grandfather gave him. When people had issues with computer software, they'd say, "Go find the guy with the red hat," and the name stuck. Except now it's a fedora.

Read more

The Companies That Support Linux: DataCentred

Filed under
Linux
Interviews

Companies are increasingly turning to cloud services to build and deliver their applications, but those that want to use an open source cloud may find it more difficult to set up and maintain. Service-providers such as UK-based DataCentred can more efficiently set up an enterprise cloud using open source software, at scale.

Read more

On a quest for a new logo and open design at Mozilla

Filed under
Interviews
Moz/FF

Sean Martell understands this. As Art Director for Mozilla, he’s one part of a team behind Mozilla’s visual design. Lately, he’s been involved in redesigning Mozilla’s iconic logos. Instead of working behind closed doors, Martell and his colleagues have opened up the design process to get the help of the wider Mozilla community.

Read more

INTERVIEW: THOMAS VOSS OF MI

Filed under
Interviews
Ubuntu

Not since the days of 2004, when X.org split from XFree86, have we seen such exciting developments in the normally prosaic realms of display servers. These are the bits that run behind your desktop, making sure Gnome, KDE, Xfce and the rest can talk to your graphics hardware, your screen and even your keyboard and mouse. They have a profound effect on your system’s performance and capabilities. And where we once had one, we now have two more – Wayland and Mir, and both are competing to win your affections in the battle for an X replacement.

We spoke to Wayland’s Daniel Stone in issue 6 of Linux Voice, so we thought it was only fair to give equal coverage to Mir, Canonical’s own in-house X replacement, and a project that has so far courted controversy with some of its decisions. Which is why we headed to Frankfurt and asked its Technical Architect, Thomas Voß, for some background context…

Read more

A cultural shift towards dynamic cloud environments

Filed under
Interviews
OSS

Where I see open source failing is when the goal is only for companies to maximize profits and minimize costs without taking a broader view of their product. I am not naïve, companies exist to make a profit but they need to figure out how to maximize their leverage by participating in open source which involves creating a healthy project that extends farther than their own self interest. I often say those that miss the point are taking the Tom Sawyer, “Paint my fence” approach to opens source. The ones that benefit the most are those that take the Beautiful Mind/John
Nash (referring to his theories in game theory) where contributors act in both their own best self interest as well as the best interest of the community.

Read more

Syndicate content

More in Tux Machines

Linux Foundation on Value of GNU/Linux Skills

  • Jobs Report: Rapid Growth in Demand for Open-Source Tech Talent
    The need for open-source technology skills are on the rise and companies and organizations continue to increase their recruitment of open-source technology talent, while offering additional training and certification opportunities for existing staff in order to fill skills gaps, according to the 2018 Open Source Jobs Report, released today by The Linux Foundation and Dice. 87% of hiring managers report difficulty finding open-source talent, and nearly half (48%) report their organizations have begun to support open-source projects with code or other resources for the explicit reason of recruiting individuals with those software skills. After a hiatus, Linux skills are back on top as the most sought after skill with 80% of hiring managers looking for tech professionals with Linux expertise. 55% of employers are now also offering to pay for employee certifications, up from 47% in 2017 and only 34% in 2016.
  • Market value of open source skills on the up
    The demand for open source technology skills is soaring, however, 87% of hiring managers report difficulty finding open source talent, according to the 2018 Open Source Jobs Report which was released this week.
  • SD Times news digest: Linux Foundation releases open-source jobs report, Android Studio 3.2 beta and Rust 1.27
    The Linux Foundation in collaboration with Dice.com has revealed the 2018 Open Source Jobs Report. The report is designed to examine trends in open-source careers as well as find out which skills are the most in demand. Key findings included 83 percent of hiring managers believes hiring open source talent is a priority and Linux is the most in-demand open-source skill. In addition, 57 percent of hiring managers are looking for people with container skills and many organizations are starting to get more involved in open-source in order to attract developers.

GNU/Linux Servers as Buzzwords: "Cloud" and "IaaS"

  • Linux: The new frontier of enterprise in the cloud
    Well obviously, like you mentioned, we've been a Linux company for a long time. We've really seen Linux expand along the lines of a lot of the things that are happening in the enterprise. We're seeing more and more enterprise infrastructure become software centric or software defined. Red Hat's expanded their portfolio in storage, in automation with the Ansible platform. And then the really big trend lately with Linux has been Linux containers and technologies like [Google] Cooper Netties. So, we're seeing enterprises want to build new applications. We're seeing the infrastructure be more software defined. Linux ends up becoming the foundation for a lot of the things going on in enterprise IT these days.
  • Why next-generation IaaS is likely to be open source
    This is partly down to Kubernetes, which has done much to popularise container technology, helped by its association with Docker and others, which has ushered in a period of explosive innovation in the ‘container platform’ space. This is where Kubernetes stands out, and today it could hold the key to the future of IaaS.

Ubuntu: Snapcraft, Intel, AMD Patches, and Telemetry

  • SD Times Open-Source Project of the Week: Snapcraft
    Canonical, the company behind operating system and Linux distribution Ubuntu, is looking to help developers package, distribute and update apps for Linux and IoT with its open-source project Snapcraft. According to Evan Dandrea, engineering manager at Canonical, Snapcraft “is a platform for publishing applications to an audience of millions of Linux users.” The project was initially created in 2014, but recently underwent rebranding efforts.
  • Ubuntu 16.04 LTS Now Certified on Select Intel NUC Mini PCs and Boards for IoT Development, LibreOffice 6.0.5 Now Available, Git 2.8 Released and More
    Canonical yesterday announced that Ubuntu 16.04 LTS is certified on select Intel NUC Mini PCs and boards for IoT development. According to the Ubuntu blog post, this pairing "provides benefits to device manufacturers at every stage of their development journey and accelerates time to market." You can download the certified image from here. In other Canonical news, yesterday the company released a microcode firmware update for Ubuntu users with AMD processors to address the Spectre vulnerability, Softpedia reports. The updated amd64-microcode packages for AMD CPUs are available for Ubuntu 18.04 LTS (Bionic Beaver), Ubuntu 17.10 (Artful Aardvark), Ubuntu 16.04 LTS (Xenial Xerus), and Ubuntu 14.04 LTS (Trusty Tahr), "all AMD users are urged to update their systems."
  • Canonical issues Spectre v2 fix for all Ubuntu systems with AMD chips
    JUST WHEN YOU THOUGHT YOU'D HEARD THE END of Spectre, Canonical has released a microcode update for all Ubuntu users that have AMD processors in a bid to rid of the vulnerability. The Spectre microprocessor side-channel vulnerabilities were made public at the beginning of this year, affecting literally billions of devices that had been made in the past two decades.
  • A first look at desktop metrics
    We first announced our intention to ask users to provide basic, not-personally-identifiable system data back in February. Since then we have built the Ubuntu Report tool and integrated it in to the Ubuntu 18.04 LTS initial setup tool. You can see an example of the data being collected on the Ubuntu Report Github page.

Most secure Linux distros in 2018

Think of a Linux distribution as a bundle of software delivered together, based on the Linux kernel - a kernel being the core of a system that connects software to hardware and vice versa – with a GNU operating system and a desktop environment, giving the user a visual way to operate the system via a graphical user interface. Linux has a reputation as being more secure than Windows and Mac OS due to a combination of factors – not all of them about the software. Firstly, although desktop Linux users are on the up, Linux environments are far less common in the grand scheme of things than Windows devices on personal computers. The Linux community also tends to be more technical. There are technical reasons too, including fundamental differences in the way the distribution architecture tends to be structured. Nevertheless over the last decade security-focused distributions started to appear, which will appeal to the privacy-conscious user who wants to avoid the worldwide state-sanctioned internet spying that the west has pioneered and where it continues to innovate. Of course, none of these will guarantee your privacy, but they're a good start. Here we list some of them. It is worth noting that security best practices are often about process rather than the technology, avoiding careless mistakes like missing patches and updates, and using your common sense about which websites you visit, what you download, and what you plug into your computer. Read more