I was also trying to visualize some features users and teams would get. Any mock-ups I’ve included are just indicative of the concept.
Users are part of teams. Teams are a group of Open Source designers/developers who want to achieve a common goal.
A user gets to leave a team whenever he wants to. Leaving a team automatically implies leaving any projects associated with the team. Similarly, if a user takes up a project, but isn’t part of the parent team, then he is automatically added to the team. Users of Glitter Gallery can invite other users to join their team at any time.
Once in a team, users can request to be part of projects. If a user is a project admin, he can approve such requests.
Projects have their own deadlines, and set of issues that contributors can take up. When discussions happen, they generally happen project-wise. Although of course, there will be provisions for teams to discuss together.
These are the organization specific features. Users also get a few user-specific features. I will attempt to cover them in another post.
[Update] -There were slight confusions with the naming conventions, so I decided to call what has been referenced here as teams, as “organizations”.