Diff for "FeatureHighlights/TeamManagement"

Not logged in - Log In / Register

Differences between revisions 5 and 6
Revision 5 as of 2007-03-26 16:13:27
Size: 3488
Editor: 81
Comment:
Revision 6 as of 2007-03-27 09:58:26
Size: 3455
Editor: 217
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 14: Line 13:
== Subscription Policies == == Subscription policies ==
Line 16: Line 15:
As you can see, this team has a list of folks who have just recently joined, and also a list of people who have recently applied to join but not yet been approved for membership. This highlights a useful feature of Launchpad team management - membership subscription policies. You can create a team which is entirely open - anybody can join just by adding themselves to the team. You can also have a team which is moderated, as Launchpad Beta Testers is, which means that anybody can apply to join but the team administrators have to approve your membership. And finally, you can have a team which is restricted - the only way to become a member is to have a team administrator add you to the team. As you can see, this has two lists of people: folks whose membership has been recently approved and people who have recently applied but have not yet been approved. This highlights a useful feature of Launchpad team management: membership subscription policies.
Line 18: Line 17:
These subscription policies are similar to those used for mailing lists. They allow you, as the creator or administrator of a team, to decide how flexible you want to be, and to maintain good control of the growth of your community if you want that. Launchpad allows you to choose from three types of membership subscription policy:
Line 20: Line 19:
== Team Hierarchies ==  * '''Entirely open:''' any Launchpad user can join simply by adding themselves.
 * '''Moderated:''' any Launchpad user can apply to join, but the team administrators must approve their membership. This is how the Launchpad Beta Testers team runs.
 * '''Restricted:''' the only way to join a team is to be added by one of its administrators.
Line 22: Line 23:
Notice that Launchpad Beta Testers is not a subteam of any other teams? Launchpad allows you to make a team a member of another team, which means of course that all the members of Team A are now also effectively members of Team B (they get all the same permissions and access to all the same goodies). Technically they are "indirect" members of Team B, but that makes no difference, they are treated exactly the same as people who signed up directly to Team B. These subscription policies are similar to those used for mailing lists. They allow you, as the creator or administrator of a team, to decide how flexible you want to be, and to maintain good control of the growth of your community, if you choose.

== Team hierarchies ==

Notice that Launchpad Beta Testers is not a sub-team of any other teams? Launchpad allows you to make a team a member of another team.

For example: if Team A becomes a member of Team B, all the members of Team A effectively become members of Team B; that is, they get all the same permissions and access to all the same goodies. Technically they are "indirect" members of Team B, but that makes no difference, they are treated exactly the same as people who joined Team B directly.
Line 28: Line 35:
Here is the relevant bit of screen: Here is the relevant part of the screen:
Line 32: Line 39:
The MOTU ("Masters of the Universe") is a very important team in Ubuntu because it's the team which looks after the largest collection of packages and is also the team where most developers first get recognized as full contributors to Ubuntu. As a result, the MOTU team is a member of several other teams - because structuring things that way means that "all new Ubuntu developers" become members of those other teams too. The MOTU ("Masters of the Universe") is a very important team in Ubuntu because it's the team which looks after the largest collection of packages. It is also the team where most developers first get recognized as full contributors to Ubuntu.
Line 34: Line 41:
There is no practical limit to the depth of team nesting that you can arrange. For example, we have some community teams which are organised in regions of a country, and they then also have a national team which consists of only the regional team members. This way, everyone who is a member of a regional team is also a member of the national team, but they don't have to do any administration of individual memberships in the national team because it's all handled by the regions. As a result, the MOTU team is a member of several other teams. Structuring things that way means that "all new Ubuntu developers" become members of those other teams too.
Line 36: Line 43:
== Using Teams == There is no practical limit to the depth of team nesting that you can arrange. For example, we have some community teams that are organised by regions of a country. That country then also has a national team, consisting only of the regional teams. This way, everyone who is a member of a regional team is also a member of the national team but administration of individual memberships is handled by the regions.
Line 38: Line 45:
First, it is trivial to create a team. You can add people and teams as members of your team. And you can use teams just about anywhere that you might use an individual person - for example, you can make a team the assignee of a bug, or the driver of a project, or the translator of a piece of software. == Using teams ==

Creating a team is trivial. Once you have created it, you can add people and teams as members of your team. You can then use your team just about anywhere that you might use an individual person. For example, you can make a team the assignee of a bug, or the driver of a project, or the translator of a piece of software.

Team management

Strong communities are built on teams. Launchpad has a very rich infrastructure to support the creation of teams, which allows communities to develop in a sophisticated fashion around projects or initiatives.

Let's look at a team:

Here's a snapshot of part of the page at the time of writing:

attachment:teamoverview.png

Subscription policies

As you can see, this has two lists of people: folks whose membership has been recently approved and people who have recently applied but have not yet been approved. This highlights a useful feature of Launchpad team management: membership subscription policies.

Launchpad allows you to choose from three types of membership subscription policy:

  • Entirely open: any Launchpad user can join simply by adding themselves.

  • Moderated: any Launchpad user can apply to join, but the team administrators must approve their membership. This is how the Launchpad Beta Testers team runs.

  • Restricted: the only way to join a team is to be added by one of its administrators.

These subscription policies are similar to those used for mailing lists. They allow you, as the creator or administrator of a team, to decide how flexible you want to be, and to maintain good control of the growth of your community, if you choose.

Team hierarchies

Notice that Launchpad Beta Testers is not a sub-team of any other teams? Launchpad allows you to make a team a member of another team.

For example: if Team A becomes a member of Team B, all the members of Team A effectively become members of Team B; that is, they get all the same permissions and access to all the same goodies. Technically they are "indirect" members of Team B, but that makes no difference, they are treated exactly the same as people who joined Team B directly.

Let's look at another team:

Here is the relevant part of the screen:

  • attachment:motuteams.png

The MOTU ("Masters of the Universe") is a very important team in Ubuntu because it's the team which looks after the largest collection of packages. It is also the team where most developers first get recognized as full contributors to Ubuntu.

As a result, the MOTU team is a member of several other teams. Structuring things that way means that "all new Ubuntu developers" become members of those other teams too.

There is no practical limit to the depth of team nesting that you can arrange. For example, we have some community teams that are organised by regions of a country. That country then also has a national team, consisting only of the regional teams. This way, everyone who is a member of a regional team is also a member of the national team but administration of individual memberships is handled by the regions.

Using teams

Creating a team is trivial. Once you have created it, you can add people and teams as members of your team. You can then use your team just about anywhere that you might use an individual person. For example, you can make a team the assignee of a bug, or the driver of a project, or the translator of a piece of software.

One of the nicest uses of teams, however, is to determine who gets "commit access" to a particular branch of code. That leads us to the next stop on our tour- [:ReviewersGuide/BazaarHosting:hosting branches of code in Launchpad].

FeatureHighlights/TeamManagement (last edited 2008-06-17 14:21:20 by localhost)