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.
For the information geek, we need a generic filter that sends the text fragment to any pre-defined system command, and sets the rendered HTML output as the output of the command. Graphviz Filter is a special case of such a filter, but we really need a generic system.
I'm thinking: gnuplot, LilyPond, LaTeX, etc. All housed under one roof.
Some design issues arise: Each of these programs produces output in a variety of formats.
The Twitter dataset is an insanely valuable source of useful social networking information. That explains the huge number of Twitter-related sites that spring up, each one performing one specific analysis of Twitter data. The one I was looking at today is TwitterSheep which just creates a tagadelic-type cloud of keywords, from a user's followers' bios. Pretty neat idea, but it was frustrating that the Web application didn't let me actually see who of my followers are in which category - and make a list out of them, and email them, etc.
If you are ready to sponsor the creation of these modules, or want to help with their development, please contact me! And if they exist already, do let me know :-)
An infinite scroll Views 3.x pager plugin. The auto-scroller would refresh the view page with the contents of the next page, as returned by the pager.
Exporters (based on CTools Exportables) for blocks, menus, taxonomies and other core objects.
Single-field editor popups (based on Popups API).