Unifying LoCo Team Resources w/Launchpad

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.


This spec discusses expanding Launchpad to centralize and ease the creation and management of LoCo team frequently requested resources.


Right now, LoCo teams need a collection of resources to work. Of course, these vary between different teams, but there is a core of resources that are commonly used by teams. This includes essential resources such as:

But, also includes non-essential, but useful resources such as:

At the moment some of these resources are centralised (mailing lists, IRC, domains), but many are not and the LoCo team need to research, install and run seperate software to get up and running. In addition to this, there is the problem of commonality of resources. As an example, there is no central place for all of the LoCo team planets, they are instead interspersed across the net.

Use cases


This spec covers feature requests for Launchpad. These are primarily data elements for better integration. Launchpad should in no way take over functions (e.g. planet.launchpad.net) but rather be the integration point for those listed in this spec.

This spec assumes that every LoCo team will have a Launchpad group and that members of each LoCo, as per the current process, will have a Launchpad id. Signing of the CoC, while required procedurally, is not currently required for this spec.

This spec does NOT include the unification of the actual planet, CMS and mailing list resources. This spec is ONLY intended to get Launchpad better aware of the data associated with LoCo teams.


We would like to enhance Launchpad by having it contain and maintain additional data fields of interest to LoCos. Data fields will generally be attributed to a LoCo Team record and may or may not be displayed. Each data field may have an associated policy governing it's use.

We would also like to the explore integration with commonly used tools such as mailman and planet.


1) Data to store inside Launchpad

2) Launchpad team will establish a master LoCo team (like the current translation team structure) and each LoCo team, approved or not, will be organized under it.

3) Creation of teams should occur in the same basic manner as it does for other towered teams today.

4) Launchpad will autogenerate a list of teams which can be pasted into the LoCo Team List on the wiki. This will allow the community manager to do a frequent refresh of this information keeping it current as team dynamics change.

5) Lauchpad will link meeting information from the meeting subsystem into each LoCo team page.


n/a at this time

Data preservation and migration

No change from current implementation.


All comments and unresolved issues are on this page.


LoCoTeamsUDSMVSpecs/UnifyingLoCoTeamResources (last edited 2008-08-06 16:17:56 by localhost)