Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Last year Drupal Association staff prepared recommendations for improved content strategy for Drupal.org. Find out what are the first changes implemented.
Drupal.org, the home of the Drupal community, has grown organically for many years. At some point it grew so large that a clear decision making structure became a necessity.
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.
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.
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 want to read the whole thing, so here is a condensed version.
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!).
As our regular quarterly review and update of the Drupal.org Terms of Service and Privacy Policy, we made the following changes to the Privacy policy today:
1. Under 'Sub-sites' we added a paragraph to clarify which data is being sent to updates.drupal.org by Drupal sites.
Drupal.org will be affected by maintenance Monday, October 19th 17:00 PDT (Oct 20th 00:00 UTC )
Upgrade Flag module to version 3 on Drupal.org will cause a short downtime as the database table structure is updated. We plan on a 30 minute window of potential instability.