LocoTeams

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2006-11-09 01:47:25 →
Size: 159
Editor: 207
Comment:
← Revision 7 as of 2006-11-09 02:00:36 → ⇥
Size: 1710
Editor: 207
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:

== Summary ==

The LoCo team infrastructure needs scaling and expanding in different ways.

== Implementation ==

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

 * Hosting only provided for approved teams - we need to encourage teams to stop spending time building resources and instead spend time building teams. We have a core set of resource requirements - mailing list, IRC etc, and the team should instead build a web presence on the Ubuntu wiki. This encourages contribution and gets people working together.

To improve and scale the LoCo project, we need to follow through with the following action points:

 * Make clearer the position of loco-contacts as a source for best practice.
 * Loco Mentoring (this is a separate spec).
 * Document conflict resolution procedures. Right now conflict resolution largely involves initial assistance from Jono Bacon, and then gu * clarify the conflict resolution process which has been referenced by several other specs, including this one.
idance from Jono as to whether the issue escalated to the community council.
 * Document leadership models and leadership best practices. Importantly, this should be easy to read - we need to make sure that we have a source of leadership best-practice documentation that is concise and easy to implement.

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

 * Continue to revise and improve the documentation. Assigning tasks to interested contributors will help here.

LoCo Teams

Summary

The LoCo team infrastructure needs scaling and expanding in different ways.

Implementation

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

  • Hosting only provided for approved teams - we need to encourage teams to stop spending time building resources and instead spend time building teams. We have a core set of resource requirements - mailing list, IRC etc, and the team should instead build a web presence on the Ubuntu wiki. This encourages contribution and gets people working together.

To improve and scale the LoCo project, we need to follow through with the following action points:

  • Make clearer the position of loco-contacts as a source for best practice.
  • Loco Mentoring (this is a separate spec).
  • Document conflict resolution procedures. Right now conflict resolution largely involves initial assistance from Jono Bacon, and then gu * clarify the conflict resolution process which has been referenced by several other specs, including this one.

idance from Jono as to whether the issue escalated to the community council.

  • Document leadership models and leadership best practices. Importantly, this should be easy to read - we need to make sure that we have a source of leadership best-practice documentation that is concise and easy to implement.

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

  • Continue to revise and improve the documentation. Assigning tasks to interested contributors will help here.

CategorySpec

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