We currently keep docs on d.o and in version control. Since docs are tied to code, I feel that the authoritative source should most naturally our git repositories. The suggestion would be to investigate how we can start deriving some degree of docs from files we commit to VCS, ideally written in a simple markup language like markdown. Obviously this would require other very significant efforts in regards to UI changes ...more »
Allow modules, themes, sandboxes, etc to act more like 'Groups' in which an issue queue is only one aspect of them. Modules could have discussions, wiki pages, events, and could help potentially help tie in the work being done with initiative pages. Functionality like maintainers being able to send out e-mail announcements (i.e. Broadcast) to people 'subscribed' to a module with security releases or major features. This ...more »
http://drupal.org/make-drupalorg-awesome outlines the current community collaboration process on Drupal.org, which is awesome but doesn't cover everything, notably Git, Solr, etc. pieces. We need a full staging environment to allow the community to hack on things in those areas, as well as to ensure Drupal.org deployments go smoothly.
With Drupal 8 due out in a year and a bit, it's high time to get our flagship site onto the latest stable version—Drupal 7!