Some random observations on the usability of Drupal.org after 5 years of using it daily. I hope to expand on these in the future.
Documentation on Drupal.org is hard to navigate. Handbook pages are mostly disconnected from module pages, which doesn't encourage module maintainers to produce consistent documentation. The module project page (which is the center of operations for the maintainer) should contain blocks pertaining to the documentation, like:
In addition, issues related to documentation (Component = "Documentation") should provide ability to link to document pages, or to create new pages that are related to this issue.
A project roadmap is a luxury if the module maintainer doesn't benefit from it - because she has other things more pressing to tend to. On the other hand, being able to manage one's own future releases is greatly beneficial, as it clearly sets up the expectations for module users, and helps the maintainer allot her time and energy to focus on important issues.
The use case is simple: Alice sifts through her issue queue, scheduling specific bugs and feature requests to be fixed in some future release (typically the next one). She can also create new feature requests for the features she plans to implement for the next release. This was one of the advices of Greg Dunlap (heyrocker)'s great talk at the Pacific Northwest Drupal Summit 2010.
Comments
I agree with your observations about the amount of disorganization in documentation. I think the latest iteration is an improvement, but needs tweaking. I also felt that someone missed the boat when I had to go to a separate tab for my groups, I would prefer that to be front and center with the first tab of my dashboard. Have you sent these ideas in as a request?
I haven't sent requests (yet) because I haven't been involved with the drupal.org redesign. I haven't even read the docs associated with it... So before engaging in public conversation, I think I should be at least aware of what's been said and of the rationales for what's been done!