The Drupal.org D7 upgrade launch is confirmed. Today is Monday, 28th of October, we have 0 launch blocking issues and performance tests are looking fine. Therefore, we are going to launch on Thursday, October 31st, 2013.
What will the launch process be like?
Drupal.org will be down for approximately 24 hours during deployment. It will be replaced by a static page with a download link for the latest Drupal release available. Sub-sites will stay online, but with user logins disabled. Both updates.drupal.org and ftp.drupal.org will stay online. drush make / dl will work fine, update status module as well.
We will start deployment around 15:00 UTC on October 31st. We expect the site to be back up by 15:00 UTC on November 1st.
We realize this will be a significant inconvenience for users who rely on Drupal.org, and will try to minimize downtime as much as possible.
What if there are problems? Do you have a backup plan?
Yes, we do. If we encounter significant problems during migration, we will roll back to the Drupal 6 version of Drupal.org and restore with a backup made right before migration started.
How can I find out what’s going on during deployment?
What changes will I experience when the site comes back online?
You can find information about the changes in functionality or UI in the Drupal.org D7 F.A.Q. Most pages on the site won’t change as far as layout or functionality. Our goal for this project was a straight port from Drupal 6 to Drupal 7. The only place where you will see significant UI changes is the issue page. This blog post explains what is changing on the issue page and why in detail. In general Drupal 7 gives us more flexibility to implement new features and there will be a boost in performance for some of the pages.
Why aren’t we waiting and upgrading to Drupal 8 once it releases?
The Drupal 7 upgrade began in March 2012. The upgrade took longer than we anticipated due to a variety of reasons that include the scale and complexity of Drupal.org and resource contstraints. We decided to push ahead and complete the Drupal 7 upgrade so Drupal.org can be on the latest release of Drupal, and so we can use the learnings in future upgrades.
UPDATE: We’ve finished running studies for this initial period. Analysis and findings now published.
Usability studies are one of the best ways to keep improving Drupal 8. We want to speak with people who create or edit content on the web to take part in a UX research study to help improve Drupal 8.
This study will help us learn how content creators move between admin and non-admin interfaces. Editing content is a key part of working with Drupal, so understanding this interaction is essential.
There are a few ways you can help:
And, with a pool of willing participants, we’ll have people we can reach out to for future studies.
If you’re interested in helping out on other Drupal User Experience issues, join us in IRC in #drupal-usability (particularly Mondays at 4:00PM Eastern Time) or follow along with issues posted in https://groups.drupal.org/usability.
Front page news:
After a month-long Community QA, we are getting ready to deploy Drupal.org D7 upgrade. During the last couple of weeks we were limiting the number of ‘to-do before launch’ issues to those that are absolutely essential. Currently our launch blocker list consists of the 12 open issues.
We took a look at the upcoming Drupal events to find a quiet week, which won’t interfere with major camps and sprints, and..
If by Monday, 28 of October, launch blocker issue is down to 0, we plan to deploy the Drupal.org D7 upgrade on Thursday, 31 of October.
If by Monday, 28 of October, the launch blocker issue count is higher than 0, we will have to postpone deployment for a few weeks.
What will the launch look like?
Drupal.org will be down for approximately 24 hours during deployment. It will be replaced by a static page with a download link for the latest Drupal release available. Sub-sites will stay online, but with user logins disabled. We realize this will be a significant inconvenience for users who rely on Drupal.org, and will try to bring it up as soon as possible.
We will start deployment around 15:00 UTC on October 31st. We expect the site to be back up by 15:00 UTC on November 1st.
Update: both updates.drupal.org and ftp.drupal.org will stay online. drush make / dl will work fine, update status module as well.
What if there are problems? Do you have a back up plan?
Yes, we do. If we encounter significant problems during migration, we will roll back to the Drupal 6 version of Drupal.org and restore backup made right before migration started.
How can I find out what’s going on during deployment?
What changes will I see when the site comes back online?
Most pages on the site won’t change. Our goal for this project was straight port from Drupal 6 to Drupal 7. The only place where you will see significant UI changes is the issue page. Some time ago we wrote up this blog post, which explains what is changing and why in detail. We will also publish an F.A.Q. right before launch, which will list all changes you might encounter on the website.
How can I help?
To ensure we are able to launch on time, you can help us by bringing launch blockers count to 0.
Here are the issues:
If you have been on Drupal.org today, you may have noticed something interesting near the bottom of the page. At some point during the past 24 hours, the millionth user joined Drupal.org!
It is tempting to overlook those statistics at the bottom of the page because our eyes tend to skip over what they see repeatedly. But it’s worth taking a moment to think about it. 228 countries. 181 languages. And counting.
As Dries pointed out in his keynote at Prague, more than 1,600 people have contributed to Drupal 8. That’s nearly double the number of contributors for Drupal 7!
The Drupal community is truly global and it’s always growing, always moving forward, 24 hours a day, 365 days a year.
Here’s to the next 1 million!
Congratulations to Mortendk and Matthew Saunders, our newly elected Directors at Large, representing the community on the board of the Drupal Association. Please join me in thanking all the candidates who put themselves forward to stand for election.
This was our third community election for the rebooted Drupal Association. We’ve learned a lot along the way and made some minor adjustments as we went, but it´s always good to reflect in the process, and perhaps reassess how we go about this in the future. We’re excited to welcome Matthew to the board and have Morten continue on for another year.
This year we’ve heard and share the community´s disappointment about the lack of diversity amongst the candidates and welcome everyone’s ideas on how to ensure we reach out wider next time. If you know great people who would be willing to serve on the board, please help us and encourage them to nominate themselves next year.
We also need to encourage more people to vote. This year 668 people cast their vote. That is 0.36% of eligible voters, which compares with last year when 0.55% of eligible voters cast a vote. Voting was open for 6 days, as opposed to 2 weeks last year. So that may well be a factor in the lower turn-out. Nonetheless we should explore the reasons, and find ways to engage more of our community in this process in the future. We´ll be opening discussion on the elections on groups.drupal.org and invite all those interested to share their thoughts.
Finally, I’d really like to thank Tatiana, Neil and Holly for taking on the work of running the elections, and outgoing community board member Pedro Cambra not only for wrangling the election software, but for being so great to work with over the past year.
Voting is now open for the 2013 At-Large Board positions for the Drupal Association! If you haven’t yet, check out the candidate profiles and review the Meet the Candidate sessions (first and second) that we held. Get to know your candidates, and then get ready vote.
How does voting work? Voting is open to all individuals who have a Drupal.org account by the time nominations open and who have logged in at least once in the past year. These individuals’ accounts will be added to the voters list on association.drupal.org and they will have access to the voting.
To vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). The results will be calculated using an “instant runoff” method. For an accessible explanation of how instant runoff vote tabulation works, see videos linked in this discussion.
Elections will be held from September 15, 2013 through September 19, 2013. During this period, you can review and comment on candidate profiles on association.drupal.org and engage all candidates through posting to the Drupal Association group.
Have questions? Contact Drupal Association Executive Director Holly Ross.
It’s time! After almost a year and a half of work we are at the finish line. D7 Drupal.org is open for community QA. We invite you all to login to the site, look around, do some of the things you usually do on Drupal.org and report any bugs or problems you encounter. Community QA will last for at least 3 weeks. The launch date will be sometime after DrupalCon Prague and will depend on how many bugs you find.
Before You Start
For this upgrade project our goal was a straight port to Drupal 7. No major regressions, no major new features. And indeed nearly all sections and pages on D7 Drupal.org will look the same as they do now on Drupal 6. There is only one page which will change significantly – the issue page. Awhile ago we wrote a detailed explanation of the changes and why they had to happen. Please be sure to review the post before going to the QA site.
Note that patch testing on the QA site may be somewhat delayed relative to production, but with patience, should be fully functional.
Ready to Do Some QA?
Great! We’ve set up a dedicated issue queue for the process. You’ll find instructions on the project page: https://drupal.org/project/d7qa.
We’ve also set up an #drupal-d7qa IRC channel on Freenode, a place for QA participants to talk to each other and the development team.
Any Video Tutorial Available?
Good question. In preparation for the community QA Melissa Anderson and Neil Drumm held a QA orientation session, where they talked about our QA server, and where and how to report issues. They also briefly showed the new Drupal.org issue pages. The recording is available below:
Now go and check out D7 Drupal.org! We do hope you’ll like it.
UPDATE: Voting is Now Open!
Voting closes on Thursday 19 Sep 2013
Now is the time! As we announced on August 16, we are looking to fill the two At-Large Director positions that are opening. 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 take part in the process.
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.
Directors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required). You can learn more about what’s expected of board members by reviewing the board member agreement.
The self-nomination form that will allow you to throw your hat in the ring is open for just a few more days:
To nominate yourself, you should be prepared to answer a few questions:
We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 2 sessions:
The nomination form will be open September 1, 2013 through September 6, 2013 at midnight UTC. For a thorough review of the process, please see our announcement blog post.
Update: Pushes to contributed modules and sandboxes are once again possible, thanks to the work of Sam Boyer and Damien Tournoud. Go forth and contribute!
Last packaged version: 7.x-2.0-alpha1+23-devLast updated: October 5, 2013 – 01:03View usage statistics for this release
Cross-post from https://association.drupal.org/node/18358
Greetings from the Drupal.org Software Working Group! We are a governance group that has been chartered in order to define the overall strategy and roadmap for *.Drupal.org’s features and functionality.
The Drupal Association Board is having their quarterly retreat at DrupalCon Prague in just a few short weeks, at which point they’ll be reviewing draft 2014 budget for the year, which will include an amount set aside for Drupal.org improvements. We want to ensure that the community has input on what this budget is spent on, but unfortunately the previous data we have on what the community wants is almost two years old. And, because of the tight timeline, we need to do this quickly.
Therefore, the Drupal.org Software Working Group is seeking input from the community to help us determine two to three significant improvements for Drupal.org to be started on by Drupal Association staff at the beginning of 2014 (yes, Drupal.org D7 upgrade will be finished this year!). If you’d like to provide your input on the Drupal.org roadmap for the first part of 2014, please visit the 2014 Drupal.org feature brainstorming group. You can review and “vote up” other peoples’ proposals, or propose your own ideas. We’ll be leaving the call for ideas open until 00:00 GMT on September 2, 2013.
We will then look at the results gathered, consider our constraints (budget, development, other necessary maintenance work, volunteer momentum) and make the best possible choice we can for the next projects. At this time, we are likely to avoid any projects that would block the forward movement of others. That doesn’t mean you shouldn’t include them. Please do. Just know that we have some work to do before the next epic undertaking. Also note that these votes will almost certainly not correspond directly to the initial priorities that we publish. There will be very practical reasons why some of the top-ranked ideas won’t be a part of this batch. We will explain the reasoning behind our choices, but we probably won’t be able to explain the reasoning for every choice we do NOT make.
We acknowledge this interim process to be severely sub-optimal. The timeline is too short, the tools are awkward, we won’t get enough feedback from a broad enough representation of the community, and we acknowledge that different stakeholders will have equally important, competing, or even conflicting priorities. One of our highest priorities as a Working Group is to develop efficient and inclusive process for collecting, prioritizing, and implementing Drupal.org improvements, a process which will allow us to get the widest community feedback possible and make informed decisions. That takes time, however, and we cannot afford to put improvements on hold until it’s worked out.
We will be re-engaging the community in 2014 with more robust process to gather more ideas about how Drupal.org can better serve its varied audiences. We’d love to have you think hard about small-scope ideas with wide-ranging impact in this go-round, but we also want to know the truth about where it hurts.
Express the needs, risks, and benefits of your ideas as clearly as you can, we’ll look at the entire picture to figure the best way we can move forward, and we’ll share the results with you in a few weeks.
Thank you for your participation in making Drupal.org awesome!
Drupal.org Software Working Group
Update: Drupal 7.24 is now available.
Download Drupal 7.23
The Drupal.org Security Team and Infrastructure Team has discovered unauthorized access to account information on Drupal.org and groups.drupal.org.
Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, etc) will be going down for 30 minutes Thursday, May 9, 17:00 PDT (May 10, 0:00 UTC). This maintenance window will be used to remove a core hack. Please follow the @drupal_infra twitter a…
Scott Reynen has done some fun things in the Drupal community. Some notable examples:
How did you get involved with Drupal?
About 4 years ago, I took a job as a developer with Aten Design Group, where we do mostly Drupal projects. At the time, I was pretty skeptical of content management systems, after frustrating experiences with both WordPress and Joomla. But I quickly grew to appreciate Drupal’s modular architecture.
What do you do with Drupal these days?
Most of my Drupal time is spent building websites for clients. I’m fortunate to be able to work on projects I really care about, like the International Center for Transitional Justice, the National Center for Women & Information Technology, and the United Nations Development Programme. Apart from client work, I use Drupal as a platform to explore new ideas. With a wide variety of code and a huge active community, Drupal serves as a great incubator.
You’re involved with the Drupal community locally and internationally – can you describe some of the things you do and why you like them?
I co-maintain Drupal Groups (groups.drupal.org), deal with abandoned projects on Drupal.org, do some work on project review applications, help organize the local Denver Drupal meetup, actively mentor a few people, and contribute some modules. I think I like all of this because I feel like I’m actively building the future, either through directly improving the web, or by enabling other people to improve the web.
What got you started in the project application review process?
I didn’t go through the application review process to get my own Git (previously CVS) access, and didn’t realize the process existed for a long time. So I think some feeling of debt played a part in my getting involved. But I also believe the future of Drupal depends on people who aren’t yet involved, and the application process, if not handled well, can very easily be a point where we turn away this next generation of contributors.
What are some of your favorite moments from that process?
It’s always nice to get thanks from new contributors for my feedback, or to discover a cool new module before it even has a release. But I think my favorite moment was when klausi arrived. Before that, I felt like I had to stay actively involved or the whole process might fall apart. When klausi started doing a superhuman number of reviews, I could comfortably step away from the queue for a short (or even long) period of time and avoid both catastrophe and burnout.
Read a previous Community Spotlight about Klaus Purer (klausi).
Are there any cool projects you’ve learned about through that process?
Commerce Registration is, I think, a great example of why the review process is important to the wider community. After some quick minor bug fixes in the review process, that project was approved and is now part of the Conference Organizing Distribution, used in every DrupalCon site. And the maintainer has gone on to contribute several other modules, a few to Drupal Commons that will be part of the next version of the Drupal Groups site. A more frustrating project review could have easily meant the Drupal community losing all of this.
What changes do you hope will come in the project review process?
Mostly I think we just need more people with the right mindset. Right now, the “needs review” backlog is gradually disappearing, largely thanks to a lot of new reviewers. I think we just need to keep more of these reviewers involved and make sure they know, as jthorson recently wrote, “the role of reviewers in this process is that of a ‘mentor’, not ‘traffic cop’”.
What is your favorite part about the Drupal community?
It’s rare to hear someone say “I don’t care” in the Drupal community. There’s plenty of work that goes off the rails on passionate debate over what color to paint the bike shed, and that can grow tedious. But our bike sheds are the best-painted on the web (12 coats!), because people really care. I like that.
Tell us a little about your background or things that interest you outside Drupal?
When I was young, I hit myself in the forehead with a boomerang. I wasn’t entirely unfamiliar with the concept, but I’d never had one actually come back. This one did, just as I was turning to see where it had landed. Stitches weren’t great back then, so I still have a scar. I still have problems with tools doing what I say rather than what I expect.
Drupal 7.22, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.22 release notes for a full listing.
Download Drupal 7.22
Update: Drupal 7.22 is now available.
Update: Drupal 7.21 is now available.
Download Drupal 7.20
Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, etc) will be going down for 30 minutes Tuesday, February 12, 5:00 PST (February 13, 01:00 UTC). This maintenance window will be used to upgrade our single sign on system. Please follow th…
Update: Drupal 7.20 is now available.