OK, this is a proposal for drupal.org's overall structure, drafted out of an irc discussion which lasted at least 2-3 hours.
In total, drupal.org +
4, 5, 6, 7, 8 subdomains
- Primarily for people visiting the site for the first time, or for the first time in a month or more. Big download link, not a lot else. this has to be ultra-fast, major news posted to it, site showcase content type, block aggregating front page news from subdomains, it has download links for core, it takes people off to where they need to go. Not much else. This could be built from scratch almost.
- Similar to the front page of drupal.org, this would consist of Drupal-related articles, announcements, events, and show-case pieces that people would post. Then folks could rate them, and editors could "promote" them (or rate them with higher weights), and each month the top X teasers from each section would be consolidated into a newsletter to be automatically generated and e-mailed to subscribers (after a chance for last minute editing). (Optionally as a PDF? That would be great for promotional materials.)
- Using panels, the sub-site would stand as a showcase for news-oriented sites. Featured articles, listings of articles in various sub-categories.
- Alternatively, or additionally, it could be an aggregator from the other sub-sites, and even Planet Drupal. Having content aggregation be automatic, so it grabs promoted and highly user-rated pieces from the other relevant sections, would help to solve the issue of editor burn-out.
- This could be the front page of drupal.org, but having it be a separate subdomain allows for user ratings to change the weights of featured articles, which helps for community-moderated content to be later e-mailed. Once e-mailed, the articles would be marked with the Flag module (or some other implementation) and archived for that month. Then the next batch has its turn to be featured on the n.d.o front page.
- The handbook, maybe api.drupal.org (docs.drupal.org/api?). Essentially we start with a dump of drupal.org and rip out everything that's not in the book hierarchy. Then we bolt api.drupal.org on somehow (even if it's a prominent link and unified search).
- Downloads + issue queues, including support. This includes module and themes. This starts as a database dump of drupal.org, with everything ripped out that's not a project or issue. I don't think there's a clean way to separate out releases from support from bugs from development between subdomains - and it's an unhealthy split anyway.
either way - projects.drupal.org/ - aggregates new and popular modules and themes and stuff
projects.drupal.org/modules - probably not the full list, that's a level down for performance
projects.drupal.org/profiles (but ideally this is /distributions or something)
projects.drupal.org/issues - the issue queue.
projects.drupal.org/support - maybe goes to a support landing page, including support issue queue (cleverly disguised as a forum), links to docs etc.
- Much the same as it is now, with some enhancements. At the moment the docs team is discussing removing large numbers of the forums. Possibly all forum type stuff should be in groups, except support (which is in project.g.o). For example paid services goes here and becomes more like a classifieds section.
g.d.o possibly takes on mailing list functionality as well.
- Hosts the DROP site. Very much as it is being hosted externally.
- No change
mitigates the subdomain split, and provides a way to avoid splitting into any more.
It runs panels 2, views 2, feedapi. rips off netvibes.
my.drupal.org/ - customisable personalised home page
my.drupal.org/planet - souped up planet + internal .d.o news aggregation
my.drupal.org/developer - cool developer stuff (see webchick's original mockup for developer.drupal.org)
my.drupal.org/designer - ditto for designers.
my.drupal.org/video - aggregates video stuff
my.drupal.org/foo- if 4-5 people are willing to maintain one, they get something similar to og panels collections to work with.
Phase 2 of my.drupal.org might do this:
By using feedapi and feed element mapper, we make sure we get the uid of every node and comment into my.drupal.org. That way, rather than parsing 200,000 x4 tracker rss feeds (+ my issues), it can take four and process those. Then my.drupal.org knows about my issues, my tracker etc. fairly intelligently.
Once it knows this, if we install user relationships, and I make friends with cwgordon07, webchick and chx, then it also knows what patches they've got that need reviewing, which modules they just released, which cvs commits they just made etc. etc. This is one possible way to deal with the potential of a million or more posts a year across *.d.o within the next year or so. It'll also allow my.drupal.org to pull that information in and spit it back out as feeds - so on projects.drupal.org it could show me a block with 'recently downloaded by your friends' or something. But my.drupal.org does the donkey work for users who are logged in a lot, so higher traffic hit and run sites like drupal.org docs.drupal.org and projects.drupal.org don't have to (as much, anyway). We'd have to make sure that my.drupal.org/[nid] is masked some to avoid link rot since there's no need for it to accumulate information for years - it'll need to periodically clean out. We also want all activity to happen on the primary subdomains, with this just for convenience.
Additionally - my.drupal.org could potentially host my.drupal.org/your-user-profile - a configurable public profile for all *.d.o users - so this is centralised in one place (and probably takes advantage of panels/advprofile as well)
There's no obvious place for the forums to live, unless they can be folded into groups and issue queues (which I'd +1)
Single sign-on - actually this doesn't add that much to the number of places to log into, but we'd need open id becuase some people will need to.
Unified search - something like solr
Unified tracker - I don't want one tracker, I want 3-4 which I can view on one page, my.drupal.org handles this.
No cross posts anywhere - instead anything posted to the front page of a subdomain appears in a block on all subdomains to avoid unnecessary duplication and "wtf I just read this" moments. - my.drupal.org can be used to aggregate content and spit it back out again between the different subdomains