Drupal 8.0.5 released

Drupal 8.0.5, a maintenance release with numerous bug fixes (no security fixes), is now available for download.
See the Drupal 8.0.5 release notes for a full list of included fixes.

Download Drupal 8.0.5
Upgrading your existing Drupal 8 sites is reco…

Top 10 contributing customers

We spent a lot of time thinking about how to highlight the organizations in our Marketplace that are actively contributing to the project. There are some awesome Drupal shops and hosting partners out there that are making a huge difference.

Service providers that you see in the marketplace are only part of the story of how Drupal is built.

Last week, we launched a new list of organizations on Drupal.org that shows every profile that has been created for an organization. This includes companies, universities, nonprofits, governments and more. These are our customers and community organizations that use Drupal to power their web experiences. By giving their developers time to contribute code back to the community, they are helping to ensure the project gets the best ideas from the most diverse group of makers and builders.

While the new view shows all organizations, I was able to pull out the top 10 customers—organizations that do not sell Drupal services or hosting—and community organizations (e.g. community from a region).

So who have been most active among this type of organization over the last 90 days?

  1. Examiner.com – 56 issue credits
  2. Pfizer – 29 issue credits
  3. Freitag – 19 issue credits
  4. Drupal Ukraine Community – 17 issue credits
  5. ARTE G.E.I.E. – 15 issue credits
  6. University of Waterloo – 13 issue credits
  7. Card.com – 13 issue credits
  8. Gemeente Venlo – 11 issue credits
  9. Dennis Publishing – 9 issue credits (and they are Drupal Association members to boot!)
  10. NBCUniversal – 7 issue credits

Check out the full list of every organization with a profile on Drupal.org. Keep in mind, we can only track issue credits when issue participants credit an organization and when maintainers award those credits.

Only organizations with a profile on Drupal.org can be credited. Confirmed users can add new organizations.

We are all excited to see where this takes us and what we can learn about how organizations that use Drupal are giving back.

If your company or organization wants to give back in ways other than contributing in the code and issue queues, consider becoming an organization member, joining one of our supporter programs, or sponsoring a DrupalCon or camp.

Report: 3.5 Million HTTPS Servers Vulnerable to DROWN

A report released Tuesday on the DROWN vulnerability raises concerns about possible attacks that could expose encrypted communications. DROWN is a serious vulnerability that affects HTTPS and other services using SSL version 2, according to the team of security researchers who compiled the report. The protocols affected are some of the essential cryptographic protocols for Internet security.

GNOME: GUADEC 2016 to happen from August 12–14 in Karlsruhe, Germany

Schloss Karlsruhe. Photo Credit: Keiko S. (flickr @craxler)

We’re happy to announce that the 2016 edition of GUADEC will be held in Karlsruhe, Germany from August 12–14, at the Karlsruhe Institute of Technology, a world-renowned research and educational institution.

Karlsruhe is located in southtwest Germany near the Franco-German border and is nicknamed the “fan city” because its streets are built radially around the palace tower. This beautiful and historic city is also home to the two highest courts in Germany, and several of Germany’s intitutions of higher learning.

“We are proud to have GUADEC in Karlsruhe this year and look forward to welcoming the GNOME community in our beautiful city. With the Gulaschprogrammiernacht (GPN) we have a large hacker congress in the city and having GUADEC here will further strengthen the local open source community.” — Benjamin Berg, local organizer

Join us!

Do you have an idea or project you’d like to share with the community during this year’s GUADEC? Stay tuned. We’ll announce a call for participation soon.

If your company or organization would like to sponsor GUADEC, you can find information on sponsorship opportunities in our Sponsors page at GUADEC.org, or contact us at sponsors@guadec.org and we are happy to discuss it with you.

If you would like to join our team of volunteers to help organize future GUADECs, please subscribe to the GUADEC mailinglist. We would love to have you on board!

Photo: “Nacht in Karlsruhe” by Heiko S., CC-BY-NC 2.0

GNOME Foundation: Minutes of the Board Meeting of February, 23th, 2016

= Minutes for Tuesday, February 23th 2016, 20:00 UTC =

Next meeting date Tuesday, March 1st, 20:00 UTC

== Attending ==

* Rosanna Yuen
* Alexandre Franke
* Shaun McCance
* Cosimo Cecchi
* Andrea Veri
* Jeff F. T.
* Ekaterina Gerasimova

== Reg…

Development: GNOME 3.19.91 beta tarballs due (and more)

Hello all,

We would like to inform you about the following:
* GNOME 3.19.91 beta tarballs due
* String Freeze

Tarballs are due on 2016-02-29 before 23:59 UTC for the GNOME 3.19.91
beta release, which will be delivered on Wednesday. Modules which wer…

The Downside of Linux Popularity

Popularity is becoming a two-edged sword for Linux. The open source operating system has become a key component of the Internet’s infrastructure, and it’s also the foundation for the world’s largest mobile OS, Google’s Android. Widespread use of the OS, though, has attracted the attention of hackers looking to transfer the dirty tricks previously aimed at Windows to Linux.

WordPress 4.5 Beta 1

WordPress 4.5 Beta 1 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.5, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]

Neverware Brings Windows Into Its Anti-Aging Fold

Neverware on Thursday announced the addition of dual-boot support, allowing its CloudReady operating system and Microsoft Windows to run on the same computer. The feature preserves existing data on computers. Adding it to CloudReady — which lets PCs and Apple computers function like Google Chromebooks — will let users keep their existing computer configuration or access Google’s environment.

GNOME Foundation: Minutes of the Board Meeting of February, 16th, 2016

= Minutes for Tuesday, February 16th 2016, 20:00 UTC =

Next meeting date Tuesday, February 23th, 20:00 UTC

== Attending ==

* Rosanna Yuen
* Alexandre Franke
* Ekaterina Gerasimova
* Shaun McCance
* Cosimo Cecchi
* Allan Day
* Andrea Veri
* J…

GNOME Foundation: Minutes of the Board Meeting of February, 09th, 2016,

= Minutes for Tuesday, February 9nd 2016, 20:00 UTC =

Next meeting date Tuesday, February 16th, 20:00 UTC

== Attending ==

* Rosanna Yuen
* Alexandre Franke
* Ekaterina Gerasimova
* Shaun McCance
* Cosimo Cecchi
* Allan Day
* Jeff F. T.

== Re…

GNOME Foundation: Minutes of the Board Meeting of February, 2nd, 2016

= Minutes for Tuesday, February 2nd 2016, 20:00 UTC =

Next meeting date Tuesday, February 9th, 20:00 UTC

== Attending ==

* Jeff F.T.
* Rosanna Yuen
* Alexandre Franke
* Ekaterina Gerasimova
* Shaun McCance
* Cosimo Cecchi
* Allan Day

== Regr…

Development: GNOME 3.19.90 beta tarballs due (and more)

Hello all,

We would like to inform you about the following:
* GNOME 3.19.90 beta tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of release notes begins

Tarballs…

The Document Foundation announces LibreOffice 5.1

Immediately available for Linux, MacOS X and Windows

wall51smallBerlin, February 10, 2016 – The Document Foundation announces LibreOffice 5.1, a full featured open source office suite which compares head-to-head with every product in the same category, while standing out with superior interoperability features.

LibreOffice 5.1 offers a completely reorganized user interface, and several improved features targeted at enterprise deployments: better support for ODF 1.2, interoperability with proprietary document formats and file management on remote servers.

LibreOffice has been downloaded 120 million times since the launch in January 2011. The office suite is deployed by large organizations in every continent, with …

Sliske’s Scoreboard | Weekly D&D

Earn XP lamps and begin to uncover what Sliske is up to!

BTS Video | Sliske’s Scoreboard

Also featuring Gone in Sliske Seconds with Mod Osborne & RuneMetrics Q&A Recap.

GNOME: Endless joins the GNOME Advisory Board

ORINDA, CA – February 3, 2016 – The GNOME Foundation is pleased to announce that Endless, creator of the Endless computer and operating system, has joined the GNOME Foundation advisory board. The Advisory Board is a body of stakeholder organizations and companies who support the GNOME Project by providing funding and expert consultation. The board includes Google, Intel, the Linux Foundation, and the Free Software Foundation, among others.

“We are very excited to join the GNOME Foundation advisory board,” said, Jonathan Blandford, VP Engineering at Endless and GNOME advisory board member. “The goals of the GNOME Foundation are perfectly aligned with the goals of Endless; to create a technology platform for the general public that is designed to be elegant, efficient, and easy to use.”

The Endless computer is the world’s first fully functioning desktop PC designed to bring the next four billion people into the information age.

“Endless is using GNOME in innovative ways to help close the digital divide. We’re excited to have them share their vision on the GNOME advisory board.” said Shaun McCance, President of the GNOME Foundation Board of Directors.

The nonprofit GNOME Foundation is an independent organization committed to supporting the advancement of the GNOME Project and software freedom. It provides financial, organizational and legal support to the GNOME Project and helps determine its vision and roadmap. GNOME software is used by millions of people around the world.

More information about GNOME and the GNOME Foundation can be found at www.gnome.org

WordPress 4.4.2 Security and Maintenance Release

WordPress 4.4.2 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.4.1 and earlier are affected by two security issues: a possible XSS for certain local URIs, reported by Ronni Skansing; and an open redirection attack, reported by Shailesh Suthar. Thank you […]

Luca Toma KDE Interview


Luca Toma

Google Code In is our annual project to give tasks to school pupils to contribute to KDE projects. One task this year is to write a Dot article and top Code In student Stanford L has interviewed WikiToLearn contributor and Sysadmin Luca Toma.

Please tell us a little about yourself
I am a second year physics student studying at the University of Milan Bicocca. I’ve been passionate about computers since the age of 10, especially the part of sysadmin / networking.

What do you do for a living?
Currently, I am a student and I work within an office that deals with management of business systems and website development.

What do you do for KDE?

At this time my contribution in KDE is WikiToLearn, my role is the system administrator. I take care of the maintenance of the infrastructure and server project.

How did you get into computer programming?
I started programming when I was 12 years of age, I was intrigued by a friend working on a GNU/Linux distribution using Bash, just like in the movies. I started with VB6, after which was passed on to C / C ++, in order and PHP.

Do you have any advice for people who would like to pursue computer programming as a major?
My advice is to write the code on what you know to be able to understand what you want and to be able to make the most out of it.

Who is your role model, and why?
I do not have a well-defined role model because I try to take inspiration from the best of all. Einstein created a model for what concerns thinking in their own way and I think it is extremely important to be able to solve problems in the best way.

What are some ways you motivate yourself?
One thing that motivates me is to do my best.
I think if each one of us always did their best in situations, it would be the best for everyone.

Do you have a vision, like where do you want KDE in general to be in 5 years and sysadmin in particular?
I hope that KDE will become a reference point for all those who want to learn computer science.
A community that is able to support projects (e.g. WikiToLearn) while providing all necessary resources, both in terms of computing power, and that of access to the necessary knowledge but also as a community in which to grow.
From the perspective of a sysadmin, to be able to provide the right environment is necessary to continue and pursue their development

Introducing a new Community Initiatives Process

One of the most important lessons of 2015 for the Engineering Team here at the Drupal Association is that we need better ways to engage with you, the community. We realized we need better tools and ways to communicate with you about our current priorities, how you can influence those priorities, and how you can help make Drupal.org and the Drupal project better than ever.

All of the work we do stems from the mission of the Drupal Association. It’s our duty and responsibility to unite a global open source community to build and promote Drupal. As the home of that community, and the codebase, Drupal.org is perhaps the most critical piece of that mission, and at the most basic level all of the initiatives we prioritize must support that goal.

As part of reviewing our work in 2015, and in the interests of being transparent with the Drupal Community, we revamped the Drupal.org Roadmap. As you can see, we chose to focus on the few, most important initiatives that we have the capacity to execute on in the near term. We’re also including upcoming initiatives that we will move into as the active work is completed, but not as many as we had previously displayed. An important lesson of the past year is that we have to be Agile on the macro scale as well as on the micro. The needs of the community can change rapidly and we need to be able to respond.

Current

These are the initiatives the Drupal Association technology staff is focused on now.

Next

These are the initiatives the Drupal Association staff will work on or support once the Current initiatives are completed. The order of these initiatives may change.

We’ve also added some new iconography to indicate where some of these initiatives come from.

Initiatives with the tools ( ) icon represent essential support and maintenance work. This can mean paying down technical debt in the Drupal.org codebase, performing server maintenance, or implementing cost saving measures to help fund the rest of our mission driven work.

Initiatives with the community ( ) icon represent initiatives that were directly proposed by members of the community and/or are being supported by volunteer work from the community.

Don’t all the initiatives come from the community?

Yes, all of our priorities come from the needs of the community – but the community is a loose collective of many different groups of people with many different needs and priorities.

The needs of Drupal newcomers are vastly different from those of the Drupal Core Maintainers. The needs of our documentation editors are different from the needs of those providing support on the forums. And all of these needs must cohere with a larger product and design vision for Drupal.org to make this home of the community a cohesive, efficient, and beautiful place to be.

The Drupal Association Engineering Team can be thought of as the maintainers for Drupal.org and the sub-sites. It’s our duty to synthesize these diverse needs and to prioritize the major initiatives that will have the highest impact for the community. It’s also our job to make the architectural decisions for Drupal.org to ensure that every aspect of the site is functional/useable, consistent, and maintainable.

Most of our priorities, therefore, we set ourselves by bringing all of these factors together and doing the best we can to have the biggest impact, not just on the most vocal parts of the community, but also on those parts that are sometimes siloed or overlooked.

All that said, the community is absolutely a vital part of creating our initiatives. The maintainers for any other project on Drupal.org do not act alone – they accept feedback and contributions from other contributors, while at the same time making key architectural decisions, reviewing patches, and ultimately deploying that work in the form of new releases. We do the same with our initiatives.

Community Volunteers and Community Initiatives

There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we’d like to beta test some new ideas to make these processes more formal, consistent, and transparent.

The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind. There is a strong record of community volunteers helping to improve Drupal.org, just a few examples from the last year include: u/mlhess and u/nnewton helping with infrastructure; to u/michelle helping to clean up spam; to u/dddave and others in the webmasters queue; or u/mshmsh5000 who helped with Drupal Jobs feature development.

If you have expertise (and not just in code!) and are ready for guidance from the Drupal Association engineering team as to how you can help, you can offer your assistance as a volunteer.

Learn about Volunteering

I should also note – we strongly encourage most volunteers to first consider giving back to the Drupal project itself, but we are certainly happy for help with Drupal.org

The second way to influence the Drupal.org roadmap is to develop a community initiative. If you (and perhaps a small team of others in the community) have some expertise in a particular area, and have a particular initiative in mind that you would like to work on, you can propose a community initiative.

View Community Initiatives

Community initiatives come in all shapes in sizes: from documentation audits with the help of u/dead_arm; to adding two factor authentication to Drupal.org with u/coltrane; to a much larger task like building and deploying DrupalCI with the help of u/jthorson, u/nickscuch, u/ricardoamaro, u/bastianwidmer and several others. Some initiatives affect a subset of the community, project maintainers, for example, whereas others may affect almost every user.

Why this new process?

The hard lesson we’ve learned over the course of the past year is that we need to be involved early. Even in cases where the community volunteers driving an initiative forward are experts in their area – if Association staff are not involved early in the architectural and planning decisions then what should be a positive, collaborative effort is often slowed down by architectural refactoring and design decision backtracks. That is not fun for anybody, and our immense respect for our community collaborators requires that we set them up for success by getting involved early.

As such, our new community initiatives process has several steps:

  1. Community members plan their contribution in an issue, and identify who (if anyone) is able to volunteer some time to make the contribution.
  2. The community members propose their initiative to the Association – so that we can evaluate it for inclusion on our roadmap. This may include a call with the community members proposing the initiative to talk it through in greater detail.
  3. Association staff evaluate the initiative: prioritize it into the roadmap, postpone it, or–if necessary– reject initiatives that are not a good fit.
  4. Prioritized community initiatives are rolled into the larger Drupal.org roadmap, and monthly or bi-monthly community initiative meetings are scheduled to ensure the work moves forward.
  5. A liaison from the Association engineering team is assigned, to help coordinate architectural decisions, to provide support and access as needed, and to coordinate with the larger team when it is time for the work to be reviewed.

This process is time intensive – and so in general we expect to be able to run only one or maybe two community initiatives at a time, in parallel with our other work. We realize this may be frustrating, but the last year has shown that our most successful initiatives required this close coordination.

This process is new, and will evolve

Finding a good process for working closely with such a diverse and passionate community is not easy—and we aren’t assuming that this new process will be perfect. We’re going to trial this new community initiative process in 2016 with the goal of increasing the transparency of how we prioritize our work, and how the community can help us build a better Drupal.org. We are committed to making this process better.