Current Status - Ready for implementation
The design phase is over for this sub-project and it is ready to be implemented.
Discussion on technical implementation started here: http://groups.drupal.org/node/179394
'Topic' page aggregates all activity across d.o, which was tagged with this specific topic.
We've explored and ditched the idea of these things being 'team' spaces.
Earlier Prairie discussions
- a topic page, initial ideas - http://groups.drupal.org/node/138439
The purpose of the 'topics' is multiple including:
- a way for people to identify their expertise
- a way to aggregate content of interest to that topic from across Drupal.org
- a way to see what is happening around specific topic right now, where and who is active
- a way to aggregate people who have interest/expertise into one place so that they are contactable en masse (when their assistance is required)
- a way for people to find mentors/people with common interest more easily when they join our community.
More images and detailed description can be found here: http://groups.drupal.org/node/144584#comment-592174
There will be 2 types of topic pages.
1st there will be short list of "top level topics" - most general ones. They will have path aliases drupal.org/usability etc. Only webmasters or some other users with special permissions will be able to create these topics.
Then there will be "usual" topic pages - subtopics, more specific than top level ones. This pages will be "childs" to top level topic pages. All drupal.org users can create subtopics of any depth.
When creating new topic - user can choose any existing topic(s) as parent(s) and as subtopic(s). Topic can have no sub-topics but should have at least 1 parent.
Topic pages are wiki-like in that their titles and descriptions can be edited by any follower of the topic (with a revision history kept).
Topic pages will have links to show a view of issues, groups, documents, discussions, initiatives that have been associated with this topic.
Main part of topic page - aggregated 'latest activity' across a range of content types on the site with ability to filter for a particular type of content (eg. issues, groups etc.)
RHS column allows you to:
- follow topic
- change notification settings
- see the number of topic followers as a link to a page showing followers list
- share/invite: this might be a share link on Twitter/Facebook or a form to invite other people on D.O and the rest of the world to come join the topic
- view FAQ/summary or links where we can get newcomers across the history, background, whatever is relevant to get them up to speed quickly.
- see most active topic members (based on their activity across all the aggregated content on the site - more scalable/friendly than 'maintainer' links but would presumably still show the maintainers here because they're most likely to be v active)
- see important links - links to key groups/documents etc. where people in this topic are active.
- see parent and sub-topics of the current one
- related topics - links to other teams that members of this topic are most likely to also have an interest in. This is human editable.
Proposed list for "top level" topic pages
We need to define a list of (ideally) less than 20 teams to begin with.
Here's a starting point for discussion/building out. The fewer of these we have to begin with the better. Probably.
- Design & UX
- Learning Drupal
- Drupal.org (webmasters on d.o, g.d.o, infrastructure team)