Guidelines and Best Practices for LoCo Teams
In order for a LoCo to work well and work together it is wise for them to follow some basic guidelines. This blueprint is going to work on setting down guidelines and best practices for locos to operate under and also help the LoCo Council monitor teams, and help in the approval and re approval of Teams.
Blueprint information
- Status:
- Complete
- Approver:
- Jono Bacon
- Priority:
- Undefined
- Drafter:
- Laura Czajkowski
- Direction:
- Needs approval
- Assignee:
- Laura Czajkowski
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-10.10
- Started by
- Laura Czajkowski
- Completed by
- Laura Czajkowski
Related branches
Related bugs
Sprints
Whiteboard
[czajkowski] work on the below :DONE
https:/
Best Practices for a LoCo - link to these pages to the main site, but use this as a check list.
*Monthly meeting - publish mins to mailing list and update wiki.
*Update/create a monthly report - assign one person to write it up, anyone can then add to it.
*Meet ups - face to face , publish you had these events
*mentoring set up
*hold workshops on line or face to face if you can
* When wiki page is up to date ask for help with getting it translated :DONE
[czajkowski] produce to pdf and then talk to the documentation team :DONE
