Web Design and Development
Look at our Roadmap highlighting how this work falls into our priorities set by the Drupal Association staff with the direction from the Board and collaboration with the community.Drupal.org Updates Following the Conversation
One of the most requested features from a wide swath of the community has been a better way to follow content on Drupal.org and receive email notifications. The issue queues have had this follow functionality for some time, but the implementation was quite specific to issues, and not easily extensible to the rest of the site.
Because of the volume of content on Drupal.org we have to be careful that our implementation will scale well. We now use a notification system based on the Message stack which functions much more generically and therefore can be applied to many content types on Drupal.org.
Follow functionality is now available for comments on Forum topics, Posts (like this one), Case Studies, and documentation Book Pages.
In the future we intend to extend this follow functionality to include notification of new revisions (for relevant content types, particularly documentation).Community Elections for the Board
Nominations for the position of At-Large Director from the community are now open. There are two of these positions on the board, each elected on alternating years. For this year's elections process we've made several small refinements:
- Candidates are now no longer required to display their real names on their candidate profile. We will now default to the Drupal.org username.
- Candidates do not have to provide a photo, we will default to a generic avatar.
- There is now an elections landing page with complete details about the elections process.
We encourage members of the community to nominate themselves!Drupal.org Enhancements
A number of smaller enhancements made it into the January sprints as well. One of the key ones was the ability to configure an arbitrary one-off test in the issue queues against a custom branch. This is a small step towards ensuring that the DrupalCI testing framework will support the wider testing matrix required for feature branching, so that Drupal can always be shippable.
We also spent some time in January reviewing the results of the documentation survey that was placed on all existing documentation pages on the site. This information is helping to inform the next big item on the roadmap - improved Documentation section on Drupal.org.
Finally, we've continued our battle against spam with the help of Technology Supporter, Distil Networks. We've seen some very promising results in initial trials to prevent spam account registrations from happening in the first place, and will continue to work on refining our integration.Sustaining support and maintenance DrupalCon New Orleans Full -Site Launched!
In January we also launched the full -site for DrupalCon New Orleans with registration and the call for papers. As part of this launch, Events.drupal.org now supports multiple, simultaneous event registrations with multiple currencies, payment processors, and invoice formats. This was a significant engineering lift, but has made Events.drupal.org even more robust.
DrupalCon New Orleans is happening from May 9-13th, and will be the first North American DrupalCon after the release of Drupal 8!DrupalCon Dublin
The next European DrupalCon will also be here before you know it, and we've been working with the local community and our designer to update the DrupalCon Dublin splash page with a new logo that we will carry through into the design for the full-site once that is ready to launch.Permissions for Elevated Users
In January we also focused on auditing the users with elevated privileges on Drupal.org, both to ensure that they had the permissions they needed, and to enforce our principle of least-access. Users at various levels of elevated privileges were contacted to see if they were still needed, and if not those privileged roles were removed.
The following privileges were also fixed or updated: webmasters can now view a user's' public ssh keys; content moderators can administer comments and block spam users without user profile editing privileges. We also fixed taxonomy vocabulary access and now both content moderators and webmasters have access to edit tags in various vocabularies such as Issue tags, giving more community members access to clean those up and fight duplicates or unused tags.Updates traffic now redirects to HTTPS
SSL is now the default for FTP traffic from Drupal.org and for Updates.drupal.org itself. This helps to enforce a best practice of using SSL wherever possible, and helps to address an oblique attack surface where a man-in-the-middle could potentially hijack an update for someone running their Drupal installation on an unprotected network (i.e. development environments on a personal laptop in a coffee shop).Devwww2 Recovery
Drupal.org pre-production environments were affected by some instability in January, particulary the devwww2 server. A combination of a hard restart due to losing a NIC on the machine and some file-system level optimizations in the database containers lead to corruption on the dev site databases. Drupal.org infrastructure engineers restored the system and recovered the critical dev sites, and while some instability continues the system has been recovering more cleanly as they work to resolve the issue permanently.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects.
Drupal 8.0.3 and Drupal 7.42, maintenance releases with numerous bug fixes (no security fixes), are now available for download.Download Drupal 8.0.3
Download Drupal 7.42
Upgrading your existing Drupal 8 and 7 sites is recommended. There are no major nor non-backwards-compatible features in these releases. For more information about the Drupal 8.x release series, consult the Drupal 8 overview. More information on the Drupal 7.x release series can be found in the Drupal 7.0 release announcement.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 8 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.
There are no security fixes in these releases of Drupal core.Bug reports
Drupal 8.0.x and 7.x actively maintained, so more maintenance releases will be made available, according to our monthly release cycle.Change log
Drupal 8.0.3 contains bug fixes and documentation and testing improvements only. The full list of changes between the last 8.0.x patch release and the 8.0.3 release can be found by reading the 8.0.3 release notes. A complete list of all changes in the stable 8.0.x branch can be found in the git commit log.
Drupal 7.42 contains bug fixes and minor new features. The full list of changes between the last 7.x patch release and the 7.42 release can be found by reading the 7.42 release notes. A complete list of all changes in the stable 7.x branch can be found in the git commit log.Update notes Planet DrupalDrupal version: Drupal 7.xDrupal 8.x
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.Issues 1. #2551607: [meta] Path forward for Composer support 2. #2533684: Create 'Documentation' Section 3. Update content style guide 4. Create Bluecheese pattern library 5. #2559711: [meta] Drupal.org (websites/infra) blockers to Drupal 8.0.0, 8.1.0, etc. 6. Make ads served through DfP contextual Planned
These are the initiatives the Association will work on once the Current initiatives are completed. The order of these initiatives may change.Issues 1. #1487662: Create 'Develop with Drupal' Section 2. #2533804: Create 'Support' Section 3. #1288470: Create 'Community' Section 4. #1414988: Create 'Contribute' Section
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 simply 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.
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.
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:
- Community members plan their contribution in an issue, and identify who (if anyone) is able to volunteer some time to make the contribution.
- 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.
- Association staff evaluate the initiative: prioritize it into the roadmap, postpone it, or--if necessary-- reject initiatives that are not a good fit.
- 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.
- 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.
It’s a great time to be part of the Drupal Association. We’ve done some amazing work in the last few years, and we’re in a great position to work with the community to continue to improve and grow fully into our mission. As a Drupal Association At-Large Director, you’d be in the center of the action. The At-large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today.Nominate Yourself Today
The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc. You can learn more about what’s expected of a board member in this post and presentation.
Directors are expected to contribute around five hours per month and attend two in-person meetings per year (financial assistance is available if required). All board members agree to meet the minimum requirements documented in the board member agreement.
Today we are opening the self-nomination form that allows you to throw your hat in the ring. We're looking to elect one candidate this year to serve a two-year term.How to Nominate Yourself
To nominate yourself, you should be prepared to answer a few questions:
- About Me: Tell us about yourself! Your background, how you got into Drupal, etc.
- Motivation: Why are you applying for a board position? What initiatives do you hope to help drive, or what perspectives are you going to try and represent?
- Experience: What Drupal community contributions have you taken part in (code, camps, etc.)? Do you have experience in financial oversight, developing business strategies, or organization governance?
- Availability: I am able to travel to three in-person board meetings per year (either self-funded, or with financial sponsorship)
- IRC Handle
- Twitter Handle
We've also made a few changes to the process based on community feedback from the 2015 election:
- We now display your username, not your given name, on your candidate profile to address privacy concerns that had been raised. Nominees should note that given names are required on legal documentation such as our 990 IRS filings, but we will do our best to preserve your privacy where we can.
- Updated sidebar block has more information about the elections, making it easier to the information you need.
- When you nominate yourself we will ask if you would like to opt-in to share your election results data. Last year was the first time we published full results from the vote data. Candidates that opt-in will have their name displayed next to their vote counts, as in this example from 2015.
We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 3 sessions:Meet the Candidate Web Conferences:
Tue 23 Feb 2016 at 16:00 UTC
- 7 AM PST Tue 23 Feb, US and Canada
- 10 AM EST Tue 23 Feb, US and Canada
- 1 PM Tue 23 Feb, Sao Paulo Brasil
- 3 PM Tue 23 Feb, London
- 11 PM Tue 23 Feb, Beijing
Wed 24 Feb 2016 at 21:00 UTC
- 12 PM PST Wed 24 Feb, US and Canada
- 3 PM EST Wed 24 Feb, US and Canada
- 5 PM Wed 24 Feb, Sao Paulo Brasil
- 8 PM Wed 24 Feb, London
- 4 AM Thu 26 Feb, Beijing
- 7 AM Thu 26 Feb, Sydney Australia
Thu 25 Feb 2016 at 01:00 UTC
- 4:00 PM PST Thu 25 Feb, US and Canada
- 7:00 PM EST Thu 25 Feb, US and Canada
- 9:00 PM Thu 25 Feb, Sau Paulo Brasil
- 12:00 AM Fri 26 Feb, London
- 8:00 AM Fri 26 Feb, Beijing
- 11:00 AM Fri 26 Feb, Sydney Australia
The nomination form will be open February 1, 2015 through February 20, 2015 at midnight UTC. For a thorough review of the process, please see our announcement blog post.
If you have any questions, please contact Holly Ross, Drupal Association Executive Director. For the sake of keeping conversational threads in one place, the comments on this news item have been closed. Please comment on the original post on the Drupal Association website.
Flickr photo: Clyde RobinsonFront page news: Drupal News
Without a doubt, 2015 was one of the Drupal community's best years. We continued to grow and change from being on an island to more of a peninsula. We also released the best Drupal version ever.
If you look back at our predictions for 2015, the Drupal 8 release was one of the most predicted events for the year. Now the question is: what we will be doing in 2016?
Will we have a decoupled Drupal? Will Drupal 9 be released? Will we see a "Drupal 6 Legacy Support" program? It is that time of year when you—yes, you—can predict the future of Drupal; take a look at your crystal ball and describe what you see. Share your deepest thoughts on what will happen for us as a community, what will happen to our code, and the difference our work might make.
On December 29, 2000, I made a code commit that would change my life; it is in this commit that I called my project "Drupal" and added the GPL license to it.
The commit where I dubbed my website project "Drupal" and added the GPL license.
A couple weeks later, on January 15, 2001, exactly 15 years ago from today, I released Drupal 1.0.0 into the world. The early decisions to open-source Drupal and use the GPL license set the cornerstone principles for how our community shares with one another and builds upon each other's achievements to this day.
Drupal is now 15 years old. In internet terms, that is an eternity. In 2001, only 7 percent of the world's population had internet access. The mobile internet had not entered the picture, less than 50% of the people in the United States had a mobile phone, and AT&T had just introduced text messaging. People searched the web with Lycos, Infoseek, AltaVista and Hot Bot. Google -- launched in 1998 as a Stanford University research project -- was still a small, private company just beginning its rise to prominence. Google AdWords, now a $65 billion business, had less than 500 customers when Drupal launched. Chrome, Firefox, and Safari didn't exist yet; most people used Netscape, Opera or Internet Explorer. New ideas for sharing and exchanging content such as "public diaries" and RSS had yet to gain widespread acceptance and Drupal was among the first to support those. Wikipedia was launched on the same day as Drupal and sparked the rise of user-generated content. Facebook and Twitter didn't exist until 4-5 years later. Proprietary software vendors started to feel threathened by open source; most didn't understand how a world-class operating system could coalesce out of part-time hacking by several thousand developers around the world.
Looking back, Drupal has not only survived massive changes in our industry; it has also helped drive them. Over the past decade and a half, I've seen many content management systems emerge and become obsolete: Vignette, Interwoven, PHP-Nuke, and Scoop were all popular at some point in the past but Drupal has outlived them all. A big reason is from the very beginning we have been about constant evolution and reinvention, painful as it is.
Keeping up with the pace of the web is a funny thing. Sometimes you'll look back on choices made years ago and think, "Well, I'm glad that was the right decision!". For example, Drupal introduced "hooks" and "modules" early on, concepts that are commonplace in today's platforms. At some point, you could even find some of my code in WordPress, which Matt Mullenweg started in 2003 with some inspiration from Drupal. Another fortuitous early decision was to focus Drupal on the concept of "nodes" rather than "pages". It wasn't until 10 years later with the rise of mobile that we started to see the web revolve less and less around pages. A node-based approach makes it possible to reuse content in different ways for different devices. In a way, much of the industry is still catching up to that vision. Even though the web is a living, breathing thing, there is a lot of things that we got right.
In the end, I feel fortunate that our community is willing to experiment and break things to stay relevant. Most recently, with the release of Drupal 8, we've made many big changes that will fuel Drupal's continued adoption. I believe we got a lot of things right in Drupal 8 and that we are on the brink of another new and bright era for Drupal.
I've undergone a lot of personal reinvention over the past 15 years too. In the early days, I spent all my time writing code and building Drupal.org. I quickly learned that a successful open source project requires much more than writing code. As Drupal started to grow, I found myself an "accidental leader" and worried about our culture, scaling the project, attracting a strong team of contributors, focusing more and more on Drupal's end-users, growing the commercial ecosystem around Drupal, starting the Drupal Association, and providing vision. Today, I wear a lot of different hats: manager of people and projects, evangelist, fundraiser, sponsor, public speaker, and BDFL. At times, it is difficult and overwhelming, but I would not want it any other way. I want to continue to push Drupal to reach new heights and new goals.
Today we risk losing much of the privacy, serendipity and freedom of the web we know. As the web evolves from a luxury to a basic human right, it's important that we treat it that way. To increase our impact, we have to continue to make Drupal easier to use. I'd love to help build a world where people's privacy is safe and Drupal is more approachable. And as the pace of innovation continues to accelerate, we have to think even more about how to scale the project, remain agile and encourage experimentation. I think about these issues a lot, and am fortunate enough to work with some of the smartest people I know to build the best possible version of the web.
So, here is to another 15 years of evolution, reinvention, and continued growth. No one knows what the web will look like 15 years in the future, but we'll keep doing our best to guide Drupal responsibly.Drupal News
There’s been a lot of positive feedback and a few questions about the recent changes to the marketplace. I want to take a minute and talk about how the marketplace made it to where it is now and mention some plans for the future of the marketplace on Drupal.org.TL;DR
This is a long post. You may not way to read the whole thing, so here is a condensed version.
We want to highlight individuals and organizations that are actively contributing to Drupal. You can now attribute your work in the Drupal.org issue queues to your employer or a customer. Maintainers can award issues credits to people who help resolve issues with code, comments, design, and more. These credits can roll up to service providers listed in the Drupal Marketplace. (And eventually we want to show customers with credits as well.)
Want to know all the details? Read on.A little history
Back at DrupalCon Austin (2014), Dries presented a sketch of an idea for highlighting organizational contributions to Drupal to myself and several business owners in the Drupal community. Later that week, those initial ideas turned into A method for giving credit to organizations that contribute code to Open Source.
The idea was to use commit messages to highlight organizational contribution. The first draft looked something like this:
$ git commit -am "Issue #n by INDIVIDUAL@AGENCY*CUSTOMER: message."
It was simple and intended to be parsable from our Git logs. However, contribution is about more than just code—and while code contributions are a good place to start, we also needed to ensure that tools for providing attribution and credit would be extensible to non-code contributions as well.
That initial conversation turned into an issue that spawned lots of child issues and ideas for how best to collect data that allowed a user on Drupal.org to attribute their work to an organization.
The resulting conversations didn’t have a simple solution, but the participation in these issues was lively and full of great ideas. Determining the format for commit credit is still an active issue.
A commit credit format alone was not going to get the information onto Drupal.org. Eventually, we settled on a couple of different solutions for tracking organization involvement and pulled all of this together into the current state of the Drupal.org Marketplace.Organizations that support modules, themes, and distributions
First, we added a feature to projects on Drupal.org (modules, themes, distributions) that allowed maintainers to reference organizations that were supporting a module—either by providing time to their developers to give back or by directly funding development.Commit credit user interface
The next part of the work was giving maintainers a better way to create their commit message related to a particular issue. A lot of the complexity of deciding who should get credit for work on Drupal.org was simplified into a UI that showed how many people had participated in an issue, how much each person had participated, and whether that person had uploaded files related to the issue. The UI also generated the Git command that would properly tie the resulting code changes to the issue and people involved. The result for a relatively large issue thread looks like the image below:Attribution
While that effort made it a lot easier to create commit credits, it didn’t solve the problem of attributing issues that didn’t result in code change, nor did it allow people to give credit to the organizations that made it possible for them to work on that issue—by giving them time or by paying for the work directly as a customer.
To do that we had to figure out a way to add organization attribution to the work being done on an issue.
Issues and comments are the primary tools for tracking what needs to be built out in Drupal code. This is where we determine the features, report the bugs, plan out the work, and more. Tracking intent at the point of this interaction was the best way for us to cover the widest range of contribution to Drupal core, modules, themes and distributions.
The resulting UI for attributing a comment to an organization is simple and straightforward.
While the instructions for attributing a contribution are documented, there’s still some confusion about when to attribute a comment to an organization versus a customer.Attributions for organizations
These attributions are to allow a person to attribute their participation in a specific issue to a company that allotted time for them to work on the issue. This is typically an employer that pays that person's salary or wage. This organization must be directly tied to the contributor's user profile on Drupal.org as a current or past employer and the organization must have an organization profile on Drupal.org. (Create an organization profile).
When you use this feature, you are highlighting an organization that is contributing code—or other improvements through the issue queues—to the community.Attributions for customers
When you attribute a customer, you are essentially saying that the work was requested by that customer but you are not employed by them. Typically this means one of three possibilities:
- The customer organization paid the contributor's employer
- The customer organization paid the contributor directly
- The contributor was volunteering for the customer organization
You can select any organization as a customer that has an organization profile on Drupal.org.
When you use the customer attribution, you’re highlighting a different way of contributing to the Drupal ecosystem and often showing relationships between organizations to solve a problem.Marking a comment with "I'm a volunteer"
Making it possible to attribute organizations who have supported contribution also helps us to gather data on purely altruistic contributions. We went round and round on this attribution feature, but in the end, we decided to add “I’m a volunteer” as an explicit attribution option in the attribution UI. It’s deliberately not the default. This is because we want to collect the explicit intent of the users making attributions. While we are now collecting this data, we haven’t yet figured out a great way to show this intent on a contributor's profile.
Possible intent on a comment could include:
- I contributed on my own time as a volunteer and community member.
- On this issue, some of my time was paid for by an employer, but some of my time was my own.
- I contributed this work as a volunteer for one or more customer organizations.
The intent of volunteerism is complex, which is why it is hard to add up into neat little data to show on a profile.
Regardless whether they mark "I'm a volunteer" or not, contributors can still be awarded issue credit by a maintainer for their work on an issue.Attribution versus issue credit versus commit credit, what's the difference?
Attribution is the first step of the process to award an issue credit. The contributor attributes their work to one or more organizations and/or as a volunteer. The next step doesn't come until the maintainer of the project (Drupal core, module, theme, distribution) gets involved in the process.Issue credits
Project maintainers may grant issue credits for issues opened against their projects. At any time during the life of the issue, a maintainer can update the credit UI to credit any of the users who have participated in the issue. Any organizations or customers attributed by those users will be credited as well. When the issue is closed fixed, those assigned credits will appear on the appropriate user and organization profiles.
Issue credits are more comprehensive than just code. They can include reviews, designs, prototypes, or just really helpful comments. The maintainer choses what they want to credit even if the issue does not have code associated with it in the form of a patch. This is a great way to help highlight contributions to policy and work to keep Drupal.org running well.Commit credits
Maintainers can grant commit credits. A commit credit gets added to the Git commit message that accompanies a commit by a maintainer of a project on Drupal.org (Drupal Core, modules, themes, distributions, etc.). Sites like drupalcores.com track this information in the public changelog and use it to highlight contribution numbers based on the number of times a user is mentioned in a commit message.
Commit credits currently can’t be easily tied to organizations, the parsing would be cumbersome and require a lot of precision when maintainers entered the information into Git, which is a big reason why we needed a UI on Drupal.org to help make all the connections and store that information into a database for easy retrieval.Showing contributions on Drupal.org
Right now, there are three ways that contributions show up on Drupal.org: the user profile, the organization profile, and the marketplace. (We have some ideas to expand this that I will detail below.)User profiles
Do you log in to Drupal.org? Great! You have a profile.
On every user profile, we show the total number of issues that a contributor has helped fix in the past 90 days.
You can drill into this information and see the specifics. This is a good way to see a facet of how a person is contributing to Drupal. There are other examples on a user's profile that show other ways they are involved.Organization profiles
Any confirmed user can create an organization page on Drupal.org. Organization profiles are currently related to a single user, but we have plans to roll out additional permissions to relate multiple users to an organization.
On the organization profile, we show the number of issues that an organization has contributed to fixing in the last 90 days.
Organization profiles also show a list of modules that have been supported by that organization, whether that organization is a Drupal Association member or Supporting Partner, and additional self-reported information about their involvement in the Drupal community.
We are currently working to automate more methods for collecting data about how organizations are contributing to the community through DrupalCon and Drupal Camp sponsorships as well as hosting user groups to help support meetups, and giving to Global Training Day events. The number of case studies associated with an organization is another indicator of how much they use Drupal and how they are helping get others to use Drupal by sharing their success stories.Marketplace
We recently rolled out some changes to how the Drupal.org Marketplace is ordered in order to better highlight contributing organizations.
Currently, the marketplace is sorted by number of issue credits awarded to an organization in the last 90 days, then whether the organization is a supporter, then by alphabetical order.
Every organization on the marketplace shows counts of its users on Drupal.org, projects (modules, themes, distributions, etc.) supported, issue credits in the last 90 days, and case studies. We also highlight organizations that are funding the ongoing support and development of Drupal.org by being in our supporting partner programs.Questions we have heard
While most people have been excited about the changes to the Marketplace, there have been several questions.Why is it only Drupal Service providers?
The marketplace was originally created to highlight Drupal service providers that are active in the Drupal community.
A "Contributing Organizations" list is the next step to expand the types of organizations we highlight. There are community members that are already working to highlight customers using Drupal that contribute back, community volunteers, and volunteers that are working for organizations that rely on volunteerism (many camps fall into this category).
These are great ideas. Contributing to those issues is a great way to help us figure out the best way forward.What about "x" contribution type?
Yes, there are many ways that organizations contribute. We are definitely hoping to add in contributions that we can objectively verify. There are so many great things that organizations can do to support Drupal, both the local and worldwide community, and Drupal.org, including:
- Sponsor a DrupalCon
- Help plan a DrupalCon
- Sponsor, organize, or host a Drupal Camp
- Host a Global Training Days event
- Host a local user group/meetup
- Post a case study of a successful Drupal project
- Contribute helpful content to Drupal Planet
There are many other phenomenal ways organizations give back. If you know of one that has objective data that can be added to the algorithm we use to highlight organizations, let us know by creating an issue in theDrupal.org Customizations queue.Why is it so hard to create an organization profile?
We definitely want to improve this process. There are over 650 organization profiles on Drupal.org, so we know that people have figured it out, but it could be much more intuitive.
We have also had a several requests to add permissions to organization profiles so that multiple people can be editors of those profiles and help administer who is allowed to be associated with the organization. Our current method of tying users to organization by using an exact text match is a bit clunky. (If you want your organization to list you as an employee, you must exactly enter the title of the organization as it appears on the organization profile and list that organization as "current".)What about more tools for individual contributions?
We have so many thoughts on how to improve the way we highlight individuals on their profile. We already show issue credits, documentation edits, commits, and lots of self-reported information. There is a lot of objective data to pull from including DrupalCon attendance, whether they have been a speaker at a DrupalCon, translation strings submitted to localize.drupal.org, Drupal Association membership, modules maintained, and many more.
Engagement with the community involves a lot of factors and we want to highlight as many as possible while still making the user profile useful and relatively succinct.Help us make Drupal.org better
In addition to the questions that have come up above, we want your feedback to keep improving the user experience on Drupal.org and make it easier to hightlight the companies that are doing so much to make Drupal the leading platform for the web and the individuals that provide their expertise and commitment to the community. Drop your ideas into the Drupal.org Customizations queue.Front page news: Drupal News
Drupal 8.0.2, a maintenance release with numerous bug fixes (no security fixes), is now available for download. See the Drupal 8.0.2 release notes for a full list of included fixes.Download Drupal 8.0.2
Upgrading your existing Drupal 8 sites is recommended. There are no major nor non-backwards-compatible features in this release. For more information about the Drupal 8.x release series, consult the Drupal 8 overview.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 8 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.
There are no security fixes in this release of Drupal core.Bug reports
Drupal 8.0.x is actively maintained, so more maintenance releases will be made available, according to our monthly release cycle.Change Log
Drupal 8.0.2 contains bug fixes and documentation and testing improvements only. The full list of changes between the 8.0.1 and 8.0.2 releases can be found by reading the 8.0.2 release notes. A complete list of all changes in the stable 8.0.x branch can be found in the git commit log.Update notes
See the 8.0.2 release notes for details on important changes in this release.Known issues
See the 8.0.2 release notes for known issues.Front page news: Planet DrupalDrupal version: Drupal 8.x
I am confident that adopting a client-side framework through progressive decoupling will give us the best of both worlds. Of course, this does not mean I oppose fully decoupling through any other framework; in fact, I believe we should redouble our efforts toward a first-class API-first Drupal. But progressive decoupling means that we will be able to work toward a next-generation user experience without abandoning much of the work we've done so far.
Special thanks to all of the following experts who provided review and input: Miško Hevery (creator of Angular; Google) and Igor Minar (technical lead for Angular; Google); Ed Faulkner (core maintainer for Ember); Amitai Burstein (Drupal and Elm contributor; Gizra); Sebastian Siemssen (Drupal contributor, Elm and React developer; Zensations); and John Albin Wilkins (Drupal 8 mobile initiative lead), Alex Bronstein (Drupal core maintainer; Acquia), Wim Leers (Drupal core contributor; Acquia), and Preston So (Drupal contributor, Acquia).
First, have we decided on the right criteria regardless of the frameworks themselves? This is probably the most important at this stage. While many organizations choose to adopt client-side frameworks for fully decoupled implementations, Drupal is the first to consider layering a framework on top to allow both richly dynamic and more traditional modules to coexist gracefully through progressive decoupling. What issues around templates, rendering, and client-side caching should we incorporate into these criteria? Is there anything missing or overemphasized?
Finally, have we drawn the right conclusions against these criteria? In other words, did we fill out the cells correctly? While they have been reviewed by some of the frameworks' experts, there might be unexpected gotchas or caveats.
At the moment, the most promising candidates in the comparison matrix appear to be Angular 2, Ember, and React, given their technical robustness, relative suitability for progressively decoupled Drupal, and their strong levels of community support and broader adoption. Given that Backbone is already in core and several modules already rely on it, we have included it too.
What we've learned from talking to the different projects is that they are often converging on similar techniques and best practices; they are by and large adding support for Virtual DOM implementations or rehydration (seamless state transfer), and they are all obsessing over small payload size and performance, better testability, etc. Therefore it is important to focus on the fundamental, often philosophical, differences between the projects that will likely be unchanged in time; key architectural differences, their release cadence and stance on backward compatibility, their license, their governance model, their flexibility and learning curve, etc.
From a quick glance at the criteria and our needs, it seems that Ember is currently our best candidate, as it appears to have a slight technical edge overall. Ember 2.0 has an all-new rendering engine named Glimmer, and it has server-side rendering through FastBoot. On the other hand, however, Ember is quite bulky and opinionated (enforcing patterns for code structure) compared to other candidate frameworks. A more fundamental difference is that unlike Angular and React, which have corporate governance and funding, Ember is a community-driven project like Drupal.
While React is lightweight, it needs integration with a variety of other libraries in the React ecosystem to work as a full-fledged implementation, which gives it a steep learning curve from an implementation standpoint. Because React is a relatively young project, best practices are shifting quickly and making it less attractive. The Virtual DOM, among React's most compelling features, has also seen its core ideas filter into other framework projects. But more importantly, React is licensed with what I believe to be a potentially unacceptable patent clause, which states that an organization can no longer use React once it sues Facebook for any (unrelated) patent infringement. This has already generated some concerted pushback from both WordPress's Calypso and React contributors.
Whatever the result of the debate around which client-side framework to adopt, I believe that Drupal needs to move quickly to embrace a framework that will aid development of a progressively decoupled architecture and corresponding user experience improvements. By providing some baseline criteria and including our accomplished community, I have no doubt we can reach this decision quickly but also intelligently.
Special thanks to Preston So for contributions to this blog post.Drupal NewsDrupal version: Drupal 8.x
If your 2015 was anything like mine, it passed by extremely quickly. It was marked by periods of frustration (spammers still love Drupal.org) and elation (Drupal 8 launched, woot!).
- New database cluster was put into service and migrations to that server begin
- User and organization profile improvements (lots more work to be done here, but it was a great start)
- DrupalCon Latin America
- Launch of Drupal Events (<a href="https://events.drupal.org>events.drupal.org) with the site for DrupalCon Los Angeles - all new events sites are hosted from the same installation
- Account creation improvements including a faster 2-step registration that returns users to the site they initiated registration from
- Support for the 2015 community elections for board member at large
- Implementation of Server Density for systems monitoring
- Centralized logging for Druapl.org infrastructure
- Relaunch of the Drupal Newsletter and migration of most Drupal.org mailing lists to Mailchimp
- Responsive breakpoints added to Drupal.org theme—a way better experience for mobile devices
- FTP migration to Fastly
- Issue credits and attribution UI
- Advanced Aggregator deployments began to improve performance of the site
- DrupalCI sprint at the Drupal Association offices in Portland
- "New" indicator for users in their first 90 days to help in welcoming newcomers to the community
- Content strategy project complete and recommendations shared with the community
- Community user role was deployed and the ability to "confirm" a new user
- Try Drupal launches giving evaluators of Drupal an option to quickly try an installation of Drupal provided for free by our hosting partners
- Homepage changes to begin supporting new content strategy
- Moved all major service deployments from BZR to Git (our standard)
- Two-factor authentication deployed for Drupal.org
- DrupalCon Los Angeles
** Presentations on content strategy and issue workspaces
- Updates to the log management to show statistics from updates.drupal.org
- Front page changes to highlight community metrics
- "Plan" issue category is deployed
- Try Drupal refinements
- Organization and user profiles updated to show last 90 days of issue credits
- DrupalCI goes into production
- Signature Supporting Partner program launched
- Updates.drupal.org traffic moved to Fastly CDN
- Interns from Epicodus join the Drupal.org team for 8 weeks
- New Git servers configured and deployed to production to replace aging hardware
- Core patch testing enabled for DrupalCI
- Upgrade of Localize.drupal.org to Drupal 7
- Apache Solr upgrades
- Updates to make issues in project queues easier to quickly read and digest
- Performance profiling on a new integration server leads to site speed improvements
- Drupal.org search improvements
- First content model update with sections and pages deployed
- Solr server high availability improvements
- DrupalCon Barcelona
- Marketplace updates to order organizations by last 90 days of issue credits and supporter status
- Drupal 8 RC1
- DrupalCI becomes the primary test platform for Drupal 8 Core; legacy testing is disabled
- Flag module and administrative views are deployed for a new take on spam fighting
- Drupal 6 & 7 testing are enabled on DrupalCI
- Kicked off the first Drupal.org membership drive
- Breadcrumbs for top level sections to make navigation a bit easier
- Server-side support for contributed Drupal 8 translations on Localize.drupal.org
- Drupal.org development environments now build in under 20 minutes
- All sites are migrated to Fastly for CDN services
- Behind-the-scenes config and code changes for the new Drupal 8 area of the site (drupal.org/8)
- Drupal 8 successfully launched
- Drupal 8 section built with a new theme
- Theme changes to the front page and header associated with Drupal 8 launch
- Download experience changes
- Began testing Distil as a solution to reduce spam account creation on Drupal.org
- 3 new test environments added to DrupalCI
- Published plan for Composer support on Drupal.org
- Old testbots are disabled and all Drupal testing is now run through DrupalCI
- Homepage changes to support the membership campaign
- Presented the new community engagement plan to the board and working groups
That was a lot of work in what was a tumultuous year. Between all the DrupalCon websites, and major updates to some of our existing sub-sites, we launched as many sites as some web development shops—at least the smaller ones.
We made several small but high impact usability improvements to Drupal.org, and built better features to highlight the contributions of individuals and organizations on their profiles. We modernized and hardened our infrastructure. We made Drupal.org a little more beautiful to better promote this amazing software and community that we support to people finding us for the first time. Among all of that…What was the most important work in 2015?
If I had to call out just one thing the Drupal.org team did this year that was essential to the success of Drupal and the community, I would highlight the great work done to launch DrupalCI and make it a production system that could handle our community's unique testing needs.
DrupalCI (the CI stands for Continuous Integration) started as a community initiative. It had been in progress for years as work to replace our aging testbot infrastructure. The old testbots required a manual spin up of new testing servers that were hosted on VMs in a cluster at the Open Source Labs. They were proprietary and rigid. If a testbot went down, it would require manual intervention to free up the queue and allow tests to begin again.
By working closely with the community throughout Q2 and Q3 of 2015, we were able to launch a testing infrastructure that supports multiple testing environments—a feature which has already helped support other projects, like PHP 7—dynamically scales to the testing load, and which is tightly integrated with the Drupal.org issue queues. Overall the new system is much more configurable and far more scalable than the previous system.
Why is testing so vital to the community? Because Drupal 8 represents a much larger code base than Drupal 7. A huge proportion of those new lines of code are tests. Every time a patch is submitted to Drupal Core, up to 15,000+ tests are run—with over 100,000 assertions. Core maintainers and initiative leads need those tests to help them understand how the new code introduced will affect Drupal. Contrib developers can also use DrupalCI to ensure their modules will work well with Drupal.
Though the work to get DrupalCI into production and optimized, we were able to give core maintainers faster and more reliable information about code submitted for inclusion in Drupal.
I honestly believe that without DrupalCI, we would not have had Drupal 8 in 2015. It sped the release of Drupal, which makes it the most accomplishment for our team in 2015.Happy but not satisfied
Larry Garfield (Crell) wrote a blog post shortly after the release of Drupal 8 where he talked about how he was happy that Drupal 8 was released—and feels it is a huge leap forward for the project—but he is not satisfied because he sees how much work is left to be done.
That is the nature of software. It can always be a little better—more performant, more usable, more extendable.
Drupal.org improved in 2015, but the team is far from satisfied. There is so much more work to complete.
At DrupalCon Amsterdam, I outlined the top 7 initiatives that the Drupal.org team would focus on. When I look back on the year, we did not hit all of our goals.
In April, one year into my time at the Drupal Association, I could point back to a lot of accomplishments, but for many, the improvements were not fast enough. By DrupalCon Los Angeles, we had achieved one of our initiative goals, and moved forward many more, but we added four more to our list. In agile project management terms, we burned up (added more work) than we burned down (work completed).
While the fact that more work is requested faster than we could complete it is not unusual, it did make us think, and we learned some lessons. We have to focus on fewer, high impact priorities. We need to plan for the unplannable - we know there will be unforeseen needs from the community and new technology to support that may not exist yet, and we must be flexible enough to respond. We need to build more partnerships and find great solutions with technology providers that are experts in their fields.
We are pretty excited that much of the planning and design work put into 2015 should result in a much more rapid pace of change to Drupal.org in 2016.What's next for Drupal.org
So, we are celebrating all the good things from 2015—there were a lot—but we are also closing the book on what was a challenging year.
Our focus shifts now to supporting the community as we all work to make Drupal 8 successful. We'll be keeping the Drupal.org Roadmap up to date and adding in new initiatives.
As we start the new year, we are still committed to the content strategy work that will make the content creation experience on Drupal.org and sub-sites better. This will improve our documentation as well as make it easier to talk about the benefits of Drupal to decision makers that help choose Drupal as the best content management framework for their organization.
Additionally, we are doing some exciting work to better support Composer on Drupal.org to align us with the rest of the PHP community as well as planning some much needed improvements to our Git workflow and developer tools.
Lastly, we are not done improving how we highlight contributions within the Drupal community. As Dries outlined in Amsterdam, Drupal is a public good. We need to highlight the great work that people around the world are doing in building Drupal and the community that supports it.
We can't wait to get started on 2016!Front page news: Drupal NewsDrupal version: Drupal 7.xDrupal 8.x
Today we released Drupal 8.0.0, the first fully supported release of Drupal 8! This is the biggest update ever to Drupal, our open source content management platform. Here are just a few of the hundreds of improvements in Drupal 8:
- In-context, what-you-see-is-what-you-get (WYSIWYG) editing and previews
- Comprehensive content modeling out of the box with entities, fields, and views
- Customization of content pages and even forms and administrative pages via the administrative interface
- Full translatability and localization out of the box
- Reliable configuration management for safe and straightforward deployment of changes between environments
- Mobile-first, responsive, HTML5 output
- REST-first native web services
- Enhanced accessibility and WAI-ARIA compliance
- Modern PHP standards and practices, with integration of popular libraries such as Composer, Symfony2, Guzzle, and Twig
- Significantly improved front-end performance out of the box
- Enhanced caching and best-of-class integration with CDNs and reverse proxies
- Full compatibility with PHP7, and the PostgreSQL and SQLite databases
- ...And much more!
Drupal 8 in action
With key modules like Views and Entity Reference fully included in Drupal 8 core, and many contributed projects already available for Drupal 8, you can start building new Drupal 8 sites right now, today. You can also use the crowd-sourced Drupal 8 Contrib Porting Tracker to get updates on the status of your favorite modules and themes, or read how you can help.How do I upgrade my current site?
If you have a Drupal 6 or 7 site you want to upgrade, install or update the Upgrade Status module to get a customized, up-to-date report on the status of your modules and themes in Drupal 8. Once you are ready, Drupal 8 core also includes the Migrate module to update existing Drupal 7 and 6 sites to Drupal 8 directly. Migrate is marked "experimental" in Drupal 8.0.0, but will be fully supported in an upcoming release. Read more about how you can migrate from Drupal 6 or 7.
Drupal 8.0.0 marks several changes for Drupal releases. We will add new features to Drupal 8 every six months in minor releases, with bug fix and security release windows every month. The next bugfix release window is December 2, 2015, and next scheduled minor release (Drupal 8.1.0) is planned for mid-April 2016.
The release of Drupal 8 also means that it's time to say a fond farewell to Drupal 6 after eight great years. Drupal 6 will reach its end-of-life (EOL) on February 24, 2016, meaning that it will no longer receive official community support and you should plan to update Drupal 6 sites soon. Refer to the Drupal 6 end-of-life announcement for more information.
Drupal 7 is still fully supported and will remain so for several more years. Read more about the Drupal core release cycle.Found a bug?
With your help, we can find and fix bugs sooner rather than later. If you find a bug in Drupal 8, search for it in the Drupal 8 issue queue, and if you don't find an existing bug report, file a new one.Celebrating the release
Help share and celebrate this milestone for the Drupal community! The Drupal 8 media kit includes the official Drupal 8 press release which has already been translated into many languages. Share this press release with your community, or use the #Drupal8 hashtag to talk about Drupal 8 on social media. Then, join one of over 200 Drupal 8 release parties on six continents.
Drupal 8 core is the work of more than 3300 contributors in over 16,000 Drupal core commits during nearly five years of development, and it is by far the best release of Drupal yet. There are already more than 50,000 Drupal 8 installations, so start yours today!
Build something amazing, for anyone.Front page news: Drupal NewsDrupal version: Drupal 8.x
We are so stoked to announce our partnership with Fastly. Fastly is now serving up all of our traffic from the *.drupal.org domain Drupal sites and related services.Drupal.org is big
Drupal.org and its services handle over 1.5 billion requests per month; this is a massive amount of traffic for an open source project.
Every time cron runs the update service on your Drupal site, it talks to updates.drupal.org. Every time you download a copy of Drupal or any projects on Drupal.org, you talk to ftp.drupal.org. (We see over 400,000 downloads of Drupal core in a typical month—way more around DrupalCons and major community sprints.)
Each month we have over 15 million unique pageviews on Drupal.org—by over 2 million unique visitors.
All of those stats are about to rise significantly with the launch of Drupal 8. Drupal 7 caused a 30% bump in traffic when it was released and we expect even more with the launch of Drupal 8.Fastly is… well… fast
In 2014, we implemented a CDN (content delivery network) for Drupal.org. The impact was immediate. Everything was faster. We met our initial goal of getting Drupal.org sites and services fronted by a CDN.
That CDN solution was a good start, and while it lacked features we didn’t know we needed, it improved our ability to deliver Drupal-generated content as well as packaged projects.
Late in 2014, we were introduced to Fastly. They offered us an opportunity to try out the service for ftp.drupal.org and we haven't looked back.Varnish for the win!
You may already use the open source Varnish for your Drupal sites. Varnish is an HTTP accelerator. Drupal.org began using Varnish in 2009 to reduce load on its web servers. It is a powerful cache that likely sits in front of your web origins. Fastly gives us a globally distributed Varnish cache with all of the features we are familiar with.
Fastly hires maintainers of the Varnish project and are helping move it forward. Drupal 8 cache keys are also a straight correllation to Fastly Surrogate Key purging and Fastly's active involvement is another great example of Fastly working with an open source community (ours!) to build a better experience.
Yay, open source!Open Source Alliance
Speaking of open source, Fastly has an open source alliance that provides free content delivery to projects like Debian, the MIT Media Lab, the W3C, Memcached, Linux Foundation, and more. They have even open sourced some of their technology stack to make it easier for others to build systems with their tools. We love partnering with these sorts of organizations.Supporting Technology Partner
Speaking of partnering, Fastly took their partnership a step further and are helping fund a lot of great work on Drupal.org through commitments to sponsor DrupalCons and even the release of Drupal 8. Look for them at upcoming DrupalCons. Thanks Fastly!How Fastly Works
Fastly’s Global Network consists of Points of Presence (POPs) running Fastly’s custom Varnish software stack. These POPs are spread around the world in strategic locations close to the highest density Internet Exchange Points, ensuring cached content is just a few milliseconds away.
Fastly has a powerful feature that allows us to specify a specific POP as a shield to our origin server. In our case we chose the Seattle POP because of its proximity to our servers at the OSL in Corvallis, Oregon in the United States.
The origin shield configuration means all requests to Drupal.org flow through Fastly’s origin server in Seattle before reaching our Drupal.org origin. If Fastly’s origin server in Seattle has already cached the file, no request to our Drupal.org origin is necessary.
In practice, this allows us to deliver a huge amount of content with an extremely high hit ratio. (See that spike in the GIF below, that's one of those regular times that cron jobs request a ton of content from our updates server. Fastly is just churning along.)
(Fastly made us confident we could put this enormous GIF in our write up.)Faster changes, faster response time
Another advantage to Fastly has been the efficiencies it has given us by allowing us to quickly make changes to how they cache our content. With our previous CDN, changes could take up to 4 hours to propagate through the system. We can now change a Varnish config and reflect those changes in under 5 seconds. That has been a huge help when we need to make a hot fix to production and keep Drupal.org delivering Drupal to the world.Logging and improving our usage stats
Fastly also allows us to stream our logs. This means we can parse those logs and turn them into data. We are already seeing much more reliable project usage statistics with from our new log processing for updates.drupal.org thanks to Fastly’s log streaming.
More accurate logs mean we can provide users with better data to help them to make better decisions about modules, themes and distributions that have the most installations.Next Steps with Fastly
We have been impressed with Fastly, both for their responsiveness and the performance improvements we have seen while using their services. They have given a ton to our community and we can't wait to see where they take Varnish and their open-source-powered service. If you are interested in using Fastly with your own Drupal sites, you can learn more about Fastly on their Drupal.org organization page or sign up for a developer account at Fastly.com—there is even a Fastly module for Drupal7, and one for Drupal8 is on the way!Front page news: Drupal News
As announced in the Drupal 6 extended support policy, 3 months after Drupal 8 comes out, Drupal 6 will be end-of-life (EOL).
On February 24th 2016, Drupal 6 will reach end of life and no longer be supported.What this means for you:
- Drupal 6 will no longer be supported by the community at large. The community at large will no longer be creating new projects, fixing bugs in existing projects, writing documentation, etc. around Drupal 6.
- There will be no more core commits on Drupal 6.x to the official tree. (see What if I have a Drupal 6 site still)
- The security team will no longer provide support or Security Advisories for Drupal 6
- All Drupal 6 releases on project pages will be flagged as not supported.
- At some point in the future update status may stop working for Drupal 6 sites.
The version of Drupal you choose for your upgrade will depend on how complex your site is, what contributed modules you need, and other factors. Many modules have been built in to Drupal 8. For example, Views and a WYSIWYG editor come as a part of Drupal 8, which means that some sites can move to Drupal 8 much sooner. Find out more about Drupal 8.
Drupal 8 core also provides a Migration path directly from Drupal 6 as an experimental feature, so sites can update directly to Drupal 8 using either a user interface or with Drush. See Executing a Drupal 6/7 to Drupal 8 upgrade for more details. The Migrate feature will be fully supported in a later minor release of Drupal 8.
Drupal 7 remains fully supported, so Drupal 6 sites can also update to Drupal 7 using the core update feature when that is a better fit. Drupal 7 is estimated to be supported until Drupal 9 is released, or later. For more information follow: [policy, no patch] Drupal 7 (and 8) EOL timing.What if I have a Drupal 6 site still?
You should plan to upgrade your site as soon as possible. For sites not updated before February 24th 2016, the Security Team is working with some vendors who are willing to provide paid support for Drupal 6 sites beyond February 24th, 2015. We will announce the details of this in early January. If you are a vendor that would like to look into doing this, please read D6 LTS Vendors policy.Front page news: Drupal NewsDrupal version: Drupal 6.x
Based on our experience with our successful release candidates, we are confident to announce that Drupal 8.0.0 will be released on November 19, 2015! Until then, we will continue publishing Drupal 8 release candidates with the latest fixes. See the first release candidate announcement for more details on the release candidate phase, or download the latest release candidate (RC2) for a preview of the release.Port your modules/themes and update translations
We are working on both the release announcement and the press release in English. However we do need volunteers to help translate it to their language. The final translations will be posted on Drupal.org at time of release.
If you can help promote the release on Twitter on November 19th and 20th in your respective time zones, Paul Johnson is looking for you. When tweeting about Drupal 8, be sure to use the hashtag #drupal8.Parties around the globe!
We also need you to throw a party! Organize a local meetup on the week (or even better the exact date) with sweets, sessions, shirts, stickers or whatever fits to spice it up. Make sure to let the community know, so it shows up on the world map on Drupical.com We also suggest you follow @celebr8d8 and promote your party and share your party stories with #celebr8d8.
Finally, thanks to the nearly 3,300 people who contributed to the codebase of Drupal 8 as well as hundreds of others who organized events, conducted usability tests, mentored contributors, found sponsors, etc.—in short did all the awesome things that made Drupal 8 happen. Now, let’s go make something amazing, for anyone!Front page news: Drupal NewsDrupal version: Drupal 8.x
Drupal 7.41, a maintenance release which contain fixes for security vulnerabilities, is now available for download. See the Drupal 7.41 release notes for further information.Download Drupal 7.41
Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features or non-security-related bug fixes in this release. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 7 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.Bug reports
Drupal 7.41 was released in response to the discovery of critical security vulnerabilities. Details can be found in the official security advisory:
To fix the security problem, please upgrade to Drupal 7.41.Known issues
None.Front page news: Planet DrupalDrupal version: Drupal 7.x