4877. That is where the tradition within the Drupal community of making predictions for the year ahead with regards to our software, our community and broader, the web, started. Node 4877, written at the end of the year 2003. We have come a long way si…
Drupal.org will be going down for up to 1 hour Monday, Jan 13, 17:00 PDT (Jan 14, 1:00 UTC). This maintenance window will be used for routine Drupal updates, which need to alter large tables. Single sign on for sub-sites (api.drupal.org, groups.drupal….
Drupal.org will be going down for up to 2 hours Wednesday, Jan 8, 17:00 PDT (Jan 9, 1:00 UTC). This maintenance window will be used to improve the speed of issue queues. Single sign on for sub-sites (api.drupal.org, groups.drupal.org, etc) will be down…
Update: Drupal 7.26 is now available.
Download Drupal 7.25
The Drupal Association, with the help of a Search Committee comprised of Board and Advisory Board members, is beginning a search for a Chief Technical Officer (CTO) for Drupal.org (not the Drupal software project). The CTO will fill a critical role for the both the Association and the community, working at the strategic level with the Drupal.org Working Groups to build a roadmap for Drupal.org, create and manage processes critical to the success of the site (including security and disaster recovery), and ensure that Drupal.org roadmaps are met. A CTO role ensures that Drupal.org has the technical and strategic oversight needed to drive improvements and innovations. Specifically we want to ensure that we have the best platform for developers, community involvement, and critical revenue-generating opportunities.
The CTO is the first of several hires we will make over the course of the next few months to significantly increase our ability to improve the experience of Drupal.org for our many constituents. These hires will include more development and devops bandwidth, among other things. In short, this is a really exciting time to work on Drupal.org!
We’re asking for your help to find the right person for this role. We’re looking for someone with strong product management skills, a community player who can work with our broad base of remarkable volunteers, and the experience to guide and manage our development, infrastructure and operations teams. Please review and share the Drupal Association CTO Job Description.
We’ve also included a little more context below if you want to learn more. And, if you have any questions, please feel free to contact Holly Ross.
Why a CTO? Isn’t that a bit much for our needs?
Our focus at the Association in 2013 has been re-aligning Association resources to bring more support and funding to our community’s most important asset: Drupal.org. During the last 9 months, we’ve begun diversifying our revenue streams so that we can scale our income and provide more funding for Drupal.org projects. We launched Working Groups to manage the strategic direction and policy setting we need to make good decisions for the site. Most recently, we hired a Technology Manager for the Association so that our limited technical staff can focus more fully on Drupal.org.
In 2014, we are planning for an even more dramatic shift, bringing on engineering and infrastructure staff to pay off years of technical debt and begin to move the site forward with new developer tools, better site performance, and strong security practices. We’re incredibly excited to help the community move Drupal.org forward and really meet community needs. We see the CTO role as essential to making this happen. It sets us up to proactively address Drupal.org needs at a strategic level – forecasting necessary changes before they become critical problems.
Isn’t this the role of the Working Groups?
Yes – the Working Group charters put them in charge of direction-setting and strategy for the sites. We anticipate that the CTO will work closely with the Working Groups to coordinate their work and ensure that those decisions are translated into a cohesive roadmap. Additionally, the Working Groups are not designed to implement the roadmap. The CTO will oversee the team that does that – either in-house, using 3rd party tools, through contractors, with volunteers, or a combination of these options.
Are you going to hire from within the community?
We are certainly going to look within the community. We will also look outside the Drupal community. The committee seeks a candidate who brings a breadth of experience and knowledge regarding open source community sites.
Is this a technical role or a business role?
We expect that the right candidate will have equal parts technical chops and business savvy. We are not expecting the CTO to write production code, but the CTO will have to know how to do that so that they can manage it well. Additionally, the CTO will need to understand business problems and how technology can be strategically deployed to meet those needs.
Where will the position be based?
Ideally, in Portland, OR, at the Drupal Association headquarters. We know however, that this is likely unrealistic as a hard and fast constraint, and will encourage applicants from around the globe.
Drupal 6.0 was released almost 6 years ago in February 2008. The Drupal community is committed to release Drupal 6 bugfixes until Drupal 8.0 is released and with recent changes provide security fixes much longer.
Back in November of 2011, I appointed Greg Knaddison to lead the Drupal Security Team, for a term of two years. In that time, Greg has done a tremendous job helping the Security Team scale. November 2013 ends the term that Greg and I agreed to, Greg is…
Update: Drupal 7.25 and Drupal 6.30 are now available.
If you are reading this announcement right now, then we did it! Drupal.org runs on Drupal 7! This was a big and complicated project, which took longer than we expected. But we are finally done!
Our goal was a straight port to Drupal 7 without major changes to functionality or layout, but with greatly improved code under the hood. However some things did change, please see Drupal.org D7 F.A.Q. for details. Overall Drupal 7 gives us more flexibility to implement new features and there will be a boost in performance for some of the pages.
NOTE: issues are still being indexed, listings and searches will show incomplete results till the indexing is done.
There probably will be some bugs. If you encounter something unusual, please check the Drupal.org D7 F.A.Q. first. It may be that the change was intentional. If you are sure that you found a bug, please use the D7 upgrade QA queue to report them.
* * *
The only thing we really want to say now is..
Thank you to all of you for being patient with us during this long project. We know it took longer than anticipated and there were some bumps along the way. Our only goal throughout the project was to make Drupal.org better for all of you.
Thank you to all our fantastic contributors. There are so many of them, we even have a special page. Thank you:
Andrei Mateescu / amateescu
Thank you to the Drupal Association Supporting Partners, who gave us the funding required to make the upgrade happen.
We couldn’t have done this without you!
Front page news:
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