LoCo Teams

Summary

Ever since the beginning of the Ubuntu project, LoCo teams have played a key role, but the huge growth of the project and the LoCo community has caused some scalability issues. This has resulted in the following issues:

Use Cases

Mike eager to participate in advocating Ubuntu joins his states LoCo. He posts messages on the LoCo's Forum and sends out an Email on the mailing list. The only responses he gets are from other "confused" LoCo members who hear from the teams senior members very rarely. Most of them say the team has been in a lull and no one has taken any initiative to get the LoCo active again in quite some time. A couple of members express to Mike their interest in wanting to participate in some Ubuntu advocacy. Mike decides he wants to start providing some direction for the Team. He is having trouble accessing the LoCo's tools (Wiki, Mailing List, Launchpad, Forum) because the current stewards of the passwords are very frequently unavailable and do not readily offer to relinquish the passwords to just anyone who asks for them. Without any ByLaws he is uncertain what actions to take in order to get the LoCo reorganized. He wants to insure a level of professionalism and prevent any kind of action that might create a schism. A certain amount of accountability not being part of the status quo makes it difficult for everyone involved to know exactly what to expect and what is expected.

Implementation

Firstly, there have been some policy decisions with the LoCo project:

To improve and scale the LoCo project, we need to follow through with the following action points, much of which involves the documentation of common processes:

Aside from these specific action points, the following general aims will also be pursued:


CategoryLoCoObsolete CategorySpec

LocoTeams (last edited 2010-08-29 14:33:29 by czajkowski)