I brought up this idea at UDS-M and with the help of the rest of the LoCo Council, I am happy to introduce some a guide to best practices we think would be beneficial to all teams. The LoCo Council has drawn up this guide on ”’Best Practices and Guidelines”’ for LoCo Teams to follow while it’s not mandatory we do encourage its use. It could also be viewed as a checklist. It has been created to help new teams set up and delegate tasks within the team and become more involved in the Ubuntu Community. It will also help teams when it is time for their Approval and Re Approval as they can show how they operate and by having continuous reports it is easier for applications.
We have broken the guide into three areas, what we would suggest teams do on a Monthly basis, Cycle based and on a Long Term goal. This will help you plan and set goals to work towards.
By breaking it down this way, it’s easier to follow some of the tasks or goals for a cycle and get used to things. Equally a great way to start to delegate tasks as we have noticed some teams tend not to share out roles within the team, and when this happens, many members are not happy, equally if someone who was in charge of an area leaves nobody knows what to do. Mentoring people is a great way to learn and share tasks with the knowledge there is someone else to help if you get stuck or need a hand.
Monthly meeting – publish mins to mailing list/forums and update wiki.
* Set a chair for 2-3 months and rotate it
* Someone to publish mins to mailing list/forums and mailing list (share out the roles)
*Update/create a monthly report
*One person to create the report and add content to it. Mail the list and ask for input in case folks had organised or participated in events within the OSS/Ubuntu community.
*Meet ups – face to face , publish you had these events, link these to the report
*Blog about them
*For larger events publish a report after the event to the loco contacts mailing list
*Add All of the events to the LoCo Directory!
CYCLE BASED GOALS
LONG TERM GOALS
*Create a a mentoring program on the below areas and train people in those areas
*Help get existing members of the community into positions in the LoCo where they can do the most good
*Help new ( and novice ) members find members to provide some level of help to ensure the new member can contribute in a useful way
*Encourage and mentor for Ubuntu Membership
*Try to create contact with the locos around you, in order to find any potential cross-action
Delegate the roles on the team
*Chair of meetings
*Hold the monthly meeting, set the agenda ( create an agenda page under meetings and let people add to it ) process the agenda with the team.
*Moderate the meeting
*Maintain the LoCo’s website
*Maintain the LoCo’s wiki site
*Mailing list admin
*Clear out the pending queue of messages
*Moderate the mailing list and deal with policy violations over private email exchanges before escalating the issue to the team administrator
*Ensure the CoC is followed in #ubuntu* namespace.
*Regulate bans, voice and ops ( if needed )