CountryTeams
Country Teams
Improving the contacts and resources that are part of LoCo teams and the countries that house them.
Spec: https://features.launchpad.net/distros/ubuntu/+spec/country-teams
Discussed: 06 Nov 2006
Summary
Right now resources (such as press contacts) and representatives (such as educaton focussed community members) is not generally formally organised, and if it is, it is at a LoCo and not a country level.
To achieve this we need to:
Engage LoCo teams to nominate contacts for particular activities and initiatives such as education and marketing.
Create a centralised list of these resources and representatives of all LoCo teams organised by country and LoCo region.
Encourage LoCo teams to store their resources and contacts in this centralised resource.
- Feed information upstream to groups such as the Marketing and Press teams.
Although there was discussion of create one-rule-to-rule-them-all for LoCo categorisation (which regions LoCo teams are representing), it was decided that flexibility is required and not all LoCo teams are the same (differences in geography, culture, interest etc).
Rationale
Although the LoCo community is well established in many parts of the world, each team largely works at a team level when it comes to certain activities such as education, marketing, translations etc. At this team level, resources and those who are committed to certain action are typically limited to the context of the team, and these resources and contacts are not seen outside the team.
Another issue is that these contacts and resources are often at a LoCo level instead of a country level. So, as an example, a USA based team may have contacts and representatives at a state-wide level, but it would be good if we could access an aggregated list of contacts and representatives at a country wide level.
Use Cases
- ubuntu-moon did a great roll out of Edubuntu to some local schools and wants to ensure that they can get it publicised. The team get their 'marketing contact' in the group to push the news up to the Marketing Team who help roll it out on the fridge, news sites and other resources.
Richard is working on lots of education initiatives and wants to be able to talk to education enthusiasts in the LoCo community. He accesses the central list of LoCo contacts to get their feedback.
Scope
We will build a central list of LoCo contacts and resources and work to get the LoCo community to use the list as part of their teams.
Implementation
Implementing this spec involves two primary tasks:
Creating a central resource where LoCo teams can store details of their resources and representatives.
Get LoCo teams to use this resource as part of their operations. Being an approved LoCo team should involve making use of this centralised resource.
Here is the list of specific actions to achieve these goals:
- Develop a document that outlines what kind of information lives in the central repository - i.e. no private information, the kind of resources etc.
- Create a document about how to push success stories upstream - Rich (Nixternal).
Create a document to clarify exactly what approval means, and how it can benefit a LoCo team - Jono.
Work with key LoCo teams to add their details to the centralised system - Melissa, Mark, Joey, Nik.
- Country-wide coalitions (such as an ubuntu-usa group that encompasses each of the state wide groups) does not make sense right now, until we have lots more teams in a country.