Creating Team Pages

Current Status - High Priority - Active

This is currently a top priority for this initiative and we are actively defining the design of a new issue page in preparation for implementation discussions.

Current thinking:

We create a series of 'teams' that people can join. To begin with (while we're working things out) we should limit the number of teams as much as possible, ideally to less than 20 teams.

Purpose

The purpose of the 'teams' is multiple including:
- a way for people to identify their expertise
- a way to aggregate content of interest to that team from across Drupal.org (the greater family)
- 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.
- //insert other good reasons here//

Current Wireframe

• team pages are wiki like in that their titles and descriptions can be edited by any member of the team (with a revision history kept)
• the bulk of the page is devoted to aggregation. The top tab shows all the latest activity in reverse chronological order (latest to top) along the lines of an activity page on Facebook for example. The other tabs act as filters, showing particular content types eg. issues, topics, groups activity and - a new feature - messages. (need to work out exactly how these would work - do you have to be a member to send a message to the team? perhaps? perhaps we just leave it open and see if we need to constrain it or not based on behaviour?)
• what other types of content might we want to aggregate here? I was tempted to add in a documentation tab as well?
  the RHS column allows you to
• join the team (equivalent of 'following'),
• see the number of team members and link to a page showing a full list of members
• share/invite: this might be a share link on Twitter/Facebook and also a form to invite other people on D.O and the rest of the world to come join the team?
• view FAQ/About the Group link or links where we can get newcomers across the history, background, whatever is relevant to get them up to speed quickly.
• see most active team members (based on their activity across all the aggregated content on the site?)
• related teams - links to other teams that members of this team are most likely to also have an interest in. This is human editable.
• manage subtopics/tags - possibly one for the future but if we need to have sub topics in the future we could manage it along the lines that Quora does it. Also, it may be useful to relate tags to teams?

Dependencies:
- deciding on the list of teams
- working out how to tag issues/groups/other d.o content with particular teams
- a much nicer graphic design
- someone to code it :)

this one strikes me as being significantly less complex than say, the issue page and there by perhaps something we could achieve relatively quickly?

Teams

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.

• Development
• Design & UX
• Documentation
• Translation
• Marketing
• Learning Drupal
• Accessibility
• Security
• Support

• Performance

• Community Management ?

• E-commerce ?
• Drupal.org (webmasters on d.o, g.d.o, infrastructure team) ?
• Git ?

Reference

Attached is a spreadsheet with an inventory of different topic-like listings already in use on drupal.org which were used to come up with our own high-level topic/team list.

Earlier Prairie discussions

• a topic page, initial ideas - http://groups.drupal.org/node/138439