TeamVerificationGuidelines
|
Size: 1725
Comment:
|
Size: 8055
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Work in progress == | <<Include(LoCoCouncil/Sandbox/SubHeader)>> == LoCo Team Approval and Re-approval process == ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| === Purpose === The purpose behind this page is to explain what a team needs to do in order to move from the unapproved Teams Category to the approved Teams Category. |
| Line 3: | Line 7: |
| This Wiki entry provides the LoCo Council with a clear set of guidelines that can help determine the fitness of a LoCo Team seeking approval. This guidelines have been suggested by the community manager and for the longest time have ruled the way the Community Council grants the status of "approved" to "new" LoCo Teams. | === Team Categories === In the Ubuntu Lo``Co Teams there are two types of teams: * Unapproved Teams - These are teams that have not met all the requirements to apply for Approval. They have either recently formed, or have existed for a while without an established standard team workflow, and have shown a limited amount of sustained team activity. |
| Line 5: | Line 11: |
| ---- == To be extended == |
* Approved Teams - An approved team is a team that is up and running, and has demonstrated sustained team activity. They have met all of the requirements, and they have established resources up and running, and the team is working well. |
| Line 8: | Line 13: |
| * All teams must provide the Council with a wiki page (in English preferredbly) with details outlined in https://wiki.ubuntu.com/LoCoGettingApproved. | === Benefits of Approval === An approved team is eligible for certain benefits such as marketing materials. An approved team is also considered official by the Ubuntu project. The following are the current benefits: * [[LoCoGettingCds|CDs for each cycle]] * [[UbuntuAtConferences|Special Conference Pack for Approved Teams]] |
| Line 10: | Line 18: |
| * The team should have demonstrated a significant and sustained contribution to the Ubuntu community. (extend a bit in significant and sustained) | === Approval Process === ==== The Process ==== To become an approved Lo``Co, the Lo``Co Council needs to have confidence that the team is up and running and performing well. This requires some evidence that the team has established various resources (website, mailing list, etc) and is actively working on different things and working well and is more than one person. To become approved the team needs to create a wiki page (more on this below) that outlines a number of things to do with the group, and has supporting evidence. ==== Is Your Team Ready? ==== The first question to ask is if the team is ready for approval. When a New Team or its leaders determine the answer to the teams readiness is “yes”, then there are a few things about the Lo``Co Council’s decision making process that the team and its members should know. ==== Purpose and Application Criteria ==== The purpose of the Lo``Co Team approval process is to ensure that a team is an active resource for Ubuntu enthusiasts in a localized geographical area and that it offers both help and information to those who are interested in contributing to the Ubuntu Community. The Lo``Co Council will uses the following criteria when evaluating team applications: * [[LoCoTeamHowto#Team_Naming_Standards|Team naming standards followed]] - many resources in the Ubuntu Community depend on this naming convention, so it is of utmost importance that these naming standards be followed. * Team resources setup (exceptions will be made in countries that have less developed Internet infrastructures). For more details you can see the [[LoCoTeamHowto#Setting_up_your_team_resources| LoCo Team How To]] * IRC * Launchpad * Team Wiki Page * Team Mailing list * Team Forum on Ubuntu Forums (ubuntuforums.org) * Experience - what has the team done so far? * Has the team done any advocacy, exhibitions, support or other activities? * The recommendation is that the team has done at least three global activities (Global Jam Participation, Bug Jam participation, Launch parties, Release parties, etc) * Eight months of activity prior to applying and detailed team reports are also recommended. However, it is important to understand, that depending on activity levels a team may be better advised to wait to apply. * Roadmap - Does the team you have an idea of what goals it wants to achieve and which projects it should work on to achieve those goals? * Future planned activities - Teams which have future events planned gives the Lo``Co Council confidence that a team is committed to staying active and building their team. These future planned activities should be laid out and included in the roadmap, and added to the LTP (Lo``Co Team Portal) if at all possible. * Membership - Are there Ubuntu members on the team? Having an Ubuntu Member in a Lo``Co is not required; but however, Team Members with Ubuntu Membership shows wider Ubuntu involvement of not only the Ubuntu Member(s) but of the scope and knowledge of the team as a whole. '''Note''': The Lo``Co Council will factor in all of the above criteria to make a decision on the applying team’s approval status. There is no magic formula of time or quantity of activities that will guarantee a team approval. The real concern for the Lo``Co Council is that a team will stay active. * Has the applying team demonstrated the ability to meet future goals and have these goals been successfully communicated to the Lo``Co Council? * Has the applying team demonstrated continually growing its member base as to ensure that team leaders and highly active participants aren't setting themselves up for burnout or withdrawal from the community, thus creating an inactive team in a short time after approval? * Has the applying team indicated to the Lo``Co Council its understanding about what it means to be an Ubuntu Lo``Co Team and demonstrates how its mission differs from that of a [[http://en.wikipedia.org/wiki/Linux_user_group|LUG]] === How to Write an Approval or Re-Approval Application === The success of a team’s application to become an approved Ubuntu Lo``Co team largely rests in ts application wiki page. The application wiki page should use the following naming protocol: * <Lo``Co``Team``Name>Approval``Application``2012 * ex: UKTeam/Approval``Application``2012 '''NOTE:''' An example application is available at LoCoExampleApplication. This shows an applying team the kind of structure that the page should form. ==== Applications Tips ==== Here are some important tips * Do not change the structure of that page - use the same section headings and structure of the LoCoExampleApplication page - this makes it easier for the Lo``Co Council to read the page it considers the team’s application. * Use as many links and references as possible - this is essential! In the Roadmap and Experience sections and elsewhere on the Approval Application Wiki, you should provide web links to websites, blogs, team reports, mailing list archives etc. that confirm the points you make on the application. So, Here is an example: A team lists an activity in the Experience section of the its Approval Application wiki, then it should link to a report about the activity in a blog, flickr, wiki page or other resource. Pictures always help! * Be concise, detailed and clear - while we the Lo``Co Council do not want to see thousands of words, we do want to be able to gain a full understanding of the teams past experience, current activities, and future goals, as well as how those will be achieved. === Re-Approval === '''Note:''' Approved teams will be re-assessed every two years to maintain their approved status. Bug Reports will be opened for teams requiring re-approval. If a team is applying for reapproval you the wiki page should use the following naming protocol: * <Lo``Co``Team``Name>Re``Approval``Application``YEAR * ex: UKTeam/Re``Approval``Application``2012 The re-approval application is similar to the approval application detailed above. The re-approval application wiki page should summarize the Lo``Co Team’s accomplishments of the past two years and outline plans for the future. Each cycle, Lo``Co contacts from Lo``Co Teams with approaching review dates will be contacted privately and asked to submit applications. If those Lo``Co Teams are prepared for re-approval, the team’s contact will add the application to the LoCoCouncilAgenda and or Bug Report. The Lo``Co Council will vote on the team’s re-approval application. The vote can be done via the Bug Report or at a Lo``Co Council Meeting. This flexibility is allowed to account for variations in timezones. |
| Line 13: | Line 71: |
| * The team should have public wiki pages and an open public mailing list set up. * The team should have an entry in https://wiki.ubuntu.com/LoCoTeamList * The team should have been running for at least 4 months and have had a consistent set of interactions with each other (council members should look at mailing list activity to assess how much activity there is) - you should also assess IRC activity where applicable. * The team should have a good roadmap and a good set of goals that they want to achieve, The Approved status is only a confirmation of their effort and it is also a commitment for further community activity. * Is the leadership fair and open - has the leader being picked fairly and representing the team efficiently and effectively? * Has there been much conflict in the team, and if so, has it been resolved? * Do the council feel this team could be trusted with additional resources such as additional CDs and being sent equipment for use? * Is this team setting a good example to the community? |
|
Council Resources to help Teams |
|
Contact |
|
LoCo Council Team Activities |
LoCo Team Approval and Re-approval process
Purpose
The purpose behind this page is to explain what a team needs to do in order to move from the unapproved Teams Category to the approved Teams Category.
Team Categories
In the Ubuntu LoCo Teams there are two types of teams:
- Unapproved Teams - These are teams that have not met all the requirements to apply for Approval. They have either recently formed, or have existed for a while without an established standard team workflow, and have shown a limited amount of sustained team activity.
- Approved Teams - An approved team is a team that is up and running, and has demonstrated sustained team activity. They have met all of the requirements, and they have established resources up and running, and the team is working well.
Benefits of Approval
An approved team is eligible for certain benefits such as marketing materials. An approved team is also considered official by the Ubuntu project. The following are the current benefits:
Approval Process
The Process
To become an approved LoCo, the LoCo Council needs to have confidence that the team is up and running and performing well. This requires some evidence that the team has established various resources (website, mailing list, etc) and is actively working on different things and working well and is more than one person. To become approved the team needs to create a wiki page (more on this below) that outlines a number of things to do with the group, and has supporting evidence.
Is Your Team Ready?
The first question to ask is if the team is ready for approval. When a New Team or its leaders determine the answer to the teams readiness is “yes”, then there are a few things about the LoCo Council’s decision making process that the team and its members should know.
Purpose and Application Criteria
The purpose of the LoCo Team approval process is to ensure that a team is an active resource for Ubuntu enthusiasts in a localized geographical area and that it offers both help and information to those who are interested in contributing to the Ubuntu Community. The LoCo Council will uses the following criteria when evaluating team applications:
Team naming standards followed - many resources in the Ubuntu Community depend on this naming convention, so it is of utmost importance that these naming standards be followed.
Team resources setup (exceptions will be made in countries that have less developed Internet infrastructures). For more details you can see the LoCo Team How To
- IRC
- Launchpad
- Team Wiki Page
- Team Mailing list
- Team Forum on Ubuntu Forums (ubuntuforums.org)
- Experience - what has the team done so far?
- Has the team done any advocacy, exhibitions, support or other activities?
- The recommendation is that the team has done at least three global activities (Global Jam Participation, Bug Jam participation, Launch parties, Release parties, etc)
- Eight months of activity prior to applying and detailed team reports are also recommended. However, it is important to understand, that depending on activity levels a team may be better advised to wait to apply.
- Roadmap - Does the team you have an idea of what goals it wants to achieve and which projects it should work on to achieve those goals?
Future planned activities - Teams which have future events planned gives the LoCo Council confidence that a team is committed to staying active and building their team. These future planned activities should be laid out and included in the roadmap, and added to the LTP (LoCo Team Portal) if at all possible.
Membership - Are there Ubuntu members on the team? Having an Ubuntu Member in a LoCo is not required; but however, Team Members with Ubuntu Membership shows wider Ubuntu involvement of not only the Ubuntu Member(s) but of the scope and knowledge of the team as a whole.
Note: The LoCo Council will factor in all of the above criteria to make a decision on the applying team’s approval status. There is no magic formula of time or quantity of activities that will guarantee a team approval. The real concern for the LoCo Council is that a team will stay active.
Has the applying team demonstrated the ability to meet future goals and have these goals been successfully communicated to the LoCo Council?
- Has the applying team demonstrated continually growing its member base as to ensure that team leaders and highly active participants aren't setting themselves up for burnout or withdrawal from the community, thus creating an inactive team in a short time after approval?
Has the applying team indicated to the LoCo Council its understanding about what it means to be an Ubuntu LoCo Team and demonstrates how its mission differs from that of a LUG
How to Write an Approval or Re-Approval Application
The success of a team’s application to become an approved Ubuntu LoCo team largely rests in ts application wiki page. The application wiki page should use the following naming protocol:
<LoCoTeamName>ApprovalApplication2012
ex: UKTeam/ApprovalApplication2012
NOTE: An example application is available at LoCoExampleApplication. This shows an applying team the kind of structure that the page should form.
Applications Tips
Here are some important tips
Do not change the structure of that page - use the same section headings and structure of the LoCoExampleApplication page - this makes it easier for the LoCo Council to read the page it considers the team’s application.
- Use as many links and references as possible - this is essential! In the Roadmap and Experience sections and elsewhere on the Approval Application Wiki, you should provide web links to websites, blogs, team reports, mailing list archives etc. that confirm the points you make on the application. So, Here is an example: A team lists an activity in the Experience section of the its Approval Application wiki, then it should link to a report about the activity in a blog, flickr, wiki page or other resource. Pictures always help!
Be concise, detailed and clear - while we the LoCo Council do not want to see thousands of words, we do want to be able to gain a full understanding of the teams past experience, current activities, and future goals, as well as how those will be achieved.
Re-Approval
Note: Approved teams will be re-assessed every two years to maintain their approved status. Bug Reports will be opened for teams requiring re-approval.
If a team is applying for reapproval you the wiki page should use the following naming protocol:
<LoCoTeamName>ReApprovalApplicationYEAR
ex: UKTeam/ReApprovalApplication2012
The re-approval application is similar to the approval application detailed above. The re-approval application wiki page should summarize the LoCo Team’s accomplishments of the past two years and outline plans for the future.
Each cycle, LoCo contacts from LoCo Teams with approaching review dates will be contacted privately and asked to submit applications. If those LoCo Teams are prepared for re-approval, the team’s contact will add the application to the LoCoCouncilAgenda and or Bug Report. The LoCo Council will vote on the team’s re-approval application. The vote can be done via the Bug Report or at a LoCo Council Meeting. This flexibility is allowed to account for variations in timezones.