Merge lp:~bhavi/uak/add-locoteam-approval into lp:uak
- add-locoteam-approval
- Merge into trunk
Status: | Merged |
---|---|
Merged at revision: | 63 |
Proposed branch: | lp:~bhavi/uak/add-locoteam-approval |
Merge into: | lp:uak |
Diff against target: |
210 lines (+171/-1) 4 files modified
adk/documentation.rst (+1/-0) adk/locoteams-approval.rst (+149/-0) adk/locoteams-running.rst (+15/-1) debian/changelog (+6/-0) |
To merge this branch: | bzr merge lp:~bhavi/uak/add-locoteam-approval |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jono Bacon (community) | Approve | ||
Review via email: mp+140086@code.launchpad.net |
Commit message
Description of the change
Added a note on getting a loco team approved in /adk/locoteams-
Regards
Bhavani
Javier López (javier-lopez) wrote : | # |
It has a typo:
"Over a period of time you can you can apply for approval from the LoCo Council." -> you can
I agree with the comment Jono made, I'd be glad to help you Bhavani, my english isn't very good, but I think I understand at least basically the process.
Bhavani Shankar (bhavi) wrote : | # |
> Thanks for the contribution, Bhavani!
>
> I think this is a great start, but I think we should create a new page that
> outlines the approval process. This way you can explain:
>
> * the difference between Approved and non-Approved teams.
> * why teams should strive to be approved.
> * how the approval process works.
> * some tips and tricks for ensuring teams are successful.
>
> Could you create locoteams-
> re-submit? Thanks!
Thanks Jono! and Javier for pointing out the typo, I'll work on the same and resubmit this evening.
Regards
Bhavani
- 61. By Bhavani Shankar
-
Added adk/locoteams-
approval. rst containing lococouncil processes on approval - 62. By Bhavani Shankar
-
Update the d/changelog
Bhavani Shankar (bhavi) wrote : | # |
Dear Jono,
Updated the branch
Regards
Bhavani
- 63. By Bhavani Shankar
-
Few more markup changes
- 64. By Bhavani Shankar
-
fix typos
Bhavani Shankar (bhavi) wrote : | # |
Dear Jono,
Please review latest commit 64 as I have done few more markup changes and fixed typos
Regards
Bhavani
- 65. By Bhavani Shankar
-
make reference to locoteams-approval in /adk/documentat
ion.rst
Bhavani Shankar (bhavi) wrote : | # |
Referenced locoteams-
Regards
Bhavani
- 66. By Bhavani Shankar
-
Bit more rewording :-) Thanks to Chris and Sergio
Jono Bacon (jonobacon) wrote : | # |
Thanks for the update, guys! Great work, and thanks for the contribution!
I made some edits that you can see in trunk now that I would like to ask you to bear in mind for future contributions:
* There were some spelling mistakes - please run a spellcheck before you submit.
* I used different heading levels to add sections within other sections.
* Try not to talk about the document itself (e.g. purpose of the document) and just present the information.
* I made some of the content a little more concise - people won't read huge chunks of text.
* There were some bits where the writing didn't make sense (I suspect this is because English is not your first language) - it might be wise to ask a native English speaker to proof read your content to help with this.
Thanks again for the contribution and I hope this feedback helps and you continue to contribute! :-)
Bhavani Shankar (bhavi) wrote : | # |
Thanks Jono for going through the review. We will get the help of a native speaker at the time of submission.
Regards
Bhavani
Preview Diff
1 | === modified file 'adk/documentation.rst' | |||
2 | --- adk/documentation.rst 2012-12-14 01:39:31 +0000 | |||
3 | +++ adk/documentation.rst 2012-12-17 15:58:22 +0000 | |||
4 | @@ -12,6 +12,7 @@ | |||
5 | 12 | locoteams-joining | 12 | locoteams-joining |
6 | 13 | locoteams-creating | 13 | locoteams-creating |
7 | 14 | locoteams-running | 14 | locoteams-running |
8 | 15 | locoteams-approval | ||
9 | 15 | 16 | ||
10 | 16 | Spreading The Word | 17 | Spreading The Word |
11 | 17 | ------------------ | 18 | ------------------ |
12 | 18 | 19 | ||
13 | === added file 'adk/locoteams-approval.rst' | |||
14 | --- adk/locoteams-approval.rst 1970-01-01 00:00:00 +0000 | |||
15 | +++ adk/locoteams-approval.rst 2012-12-17 15:58:22 +0000 | |||
16 | @@ -0,0 +1,149 @@ | |||
17 | 1 | ================================ | ||
18 | 2 | Getting your LoCo Team approved. | ||
19 | 3 | ================================ | ||
20 | 4 | |||
21 | 5 | Purpose of this document | ||
22 | 6 | ------------------------- | ||
23 | 7 | |||
24 | 8 | The purpose behind this document is to explain what a team needs to do in order | ||
25 | 9 | to get approved by the LoCo Council. | ||
26 | 10 | |||
27 | 11 | Types of LoCo Teams | ||
28 | 12 | ------------------- | ||
29 | 13 | |||
30 | 14 | There are two types of LoCo teams in ubuntu basically: | ||
31 | 15 | |||
32 | 16 | * Unapproved Teams - These are teams that have not met all the requirements | ||
33 | 17 | to apply for Approval. They have either recently formed, or have existed for | ||
34 | 18 | a while without an established standard team workflow, and have shown a | ||
35 | 19 | limited amount of sustained team activity. | ||
36 | 20 | |||
37 | 21 | * Approved Teams - An approved team is a team that has demonstrated sustained | ||
38 | 22 | team activity. They have met all of the requirements, and they | ||
39 | 23 | have established resources up and running, and there should be a | ||
40 | 24 | clear evidence that the team is working well. | ||
41 | 25 | |||
42 | 26 | Benifits of getting approved | ||
43 | 27 | ----------------------------- | ||
44 | 28 | |||
45 | 29 | An approved team is eligible for certain benefits such as marketing materials. | ||
46 | 30 | An approved team is also considered official by the Ubuntu project. | ||
47 | 31 | The following are the current benefits: | ||
48 | 32 | |||
49 | 33 | * Ubuntu CD Packs `CD packs are given each cycle <https://wiki.ubuntu.com/LoCoGettingCds>`_! | ||
50 | 34 | |||
51 | 35 | * Conference Packs - `Given when there is a conference in your locality and you are representing Ubuntu <https://wiki.ubuntu.com/UbuntuAtConferences>`_! | ||
52 | 36 | |||
53 | 37 | The Process of getting approved | ||
54 | 38 | -------------------------------- | ||
55 | 39 | |||
56 | 40 | The first question one tends to ask is if the team is ready for approval, If | ||
57 | 41 | the team leaders and the members answer is 'yes', then they need to know a few | ||
58 | 42 | things about the application process. | ||
59 | 43 | |||
60 | 44 | Purpose | ||
61 | 45 | -------- | ||
62 | 46 | |||
63 | 47 | The purpose of the LoCo Team approval process is to ensure that a team is an | ||
64 | 48 | active resource for Ubuntu enthusiasts in a localized geographical area and | ||
65 | 49 | that it offers both help and information to those who are interested in | ||
66 | 50 | contributing to the Ubuntu Community. | ||
67 | 51 | |||
68 | 52 | .. Note:: The real concern of the LoCo Council is whether the loco team remains | ||
69 | 53 | active over a period of time. | ||
70 | 54 | |||
71 | 55 | Application Crieteria | ||
72 | 56 | ---------------------- | ||
73 | 57 | |||
74 | 58 | The LoCo Council will use the following criteria when evaluating team | ||
75 | 59 | applications: | ||
76 | 60 | |||
77 | 61 | * Team naming standards followed. | ||
78 | 62 | |||
79 | 63 | * Team Resources. (which may be exempted for countries where there is less | ||
80 | 64 | developed internet infrastructure) | ||
81 | 65 | |||
82 | 66 | Team resources include the below list in general: | ||
83 | 67 | * IRC | ||
84 | 68 | * Launchpad | ||
85 | 69 | * Team Wiki Page | ||
86 | 70 | * Team Mailing list | ||
87 | 71 | * Team Forum on Ubuntu Forums <http://ubuntuforums.org> | ||
88 | 72 | |||
89 | 73 | * Experience - Experience will be evaluated on the below questions typically: | ||
90 | 74 | |||
91 | 75 | * What has the team been doing? | ||
92 | 76 | |||
93 | 77 | * Has the team done any advocacy, exhibitions, support or other activities? | ||
94 | 78 | The recommendation is that the team has done at least three global | ||
95 | 79 | activities such as Global Jam Participation, Bug Jam participation, Launch parties, | ||
96 | 80 | Release parties, etc | ||
97 | 81 | Eight months of activity prior to applying and detailed team reports are | ||
98 | 82 | also recommended. However, it is important to understand, that approval | ||
99 | 83 | depends on activity levels a team | ||
100 | 84 | |||
101 | 85 | * Has the applying team demonstrated the ability to meet future goals and | ||
102 | 86 | have these goals (essentially a roadmap) been successfully communicated to | ||
103 | 87 | the LoCo Council? | ||
104 | 88 | |||
105 | 89 | * Has the applying team demonstrated continually growing its member base as | ||
106 | 90 | to ensure that team leaders and highly active participants aren't setting | ||
107 | 91 | themselves up for burnout or withdrawal from the community, thus creating | ||
108 | 92 | an inactive team in a short time after approval? | ||
109 | 93 | |||
110 | 94 | * Has the applying team indicated to the LoCo Council its understanding | ||
111 | 95 | about what it means to be an Ubuntu LoCo Team and demonstrates | ||
112 | 96 | how its mission differs from that of a LUG. | ||
113 | 97 | |||
114 | 98 | * Future Planning - Teams which have future events planned gives the | ||
115 | 99 | LoCo Council confidence that a team is committed to staying active and | ||
116 | 100 | building their team. These future planned activities should be laid out | ||
117 | 101 | and included in the roadmap, and added to the LTP (LoCo Team Portal) | ||
118 | 102 | if at all possible. | ||
119 | 103 | |||
120 | 104 | * Having Ubuntu Members in the team - Are there Ubuntu members on the team? | ||
121 | 105 | Having an Ubuntu Member in a LoCo is not required; but however, | ||
122 | 106 | Team Members with Ubuntu Membership shows wider Ubuntu involvement of not | ||
123 | 107 | only the Ubuntu Member(s) but of the scope and knowledge of the team as a | ||
124 | 108 | whole. | ||
125 | 109 | |||
126 | 110 | How to write an approval application? | ||
127 | 111 | ------------------------------------- | ||
128 | 112 | |||
129 | 113 | The success of a team’s application to become an approved Ubuntu LoCo team | ||
130 | 114 | largely rests in ts application wiki page. `An example wiki page is available | ||
131 | 115 | here <https://wiki.ubuntu.com/LoCoExampleApplication>`_ :-) Showing the page the LoCo | ||
132 | 116 | team should form when applying for approval with the naming convention | ||
133 | 117 | *<LoCoTeam>/ApprovalApplication* ex: *UKTeam/ApprovalApplication* | ||
134 | 118 | |||
135 | 119 | Application Tips | ||
136 | 120 | ---------------- | ||
137 | 121 | |||
138 | 122 | * Do not change the structure of the sample page reference given above. | ||
139 | 123 | * Use as many links and references as possible - this is essential! | ||
140 | 124 | In the Roadmap and Experience sections and elsewhere on the Approval Application | ||
141 | 125 | Wiki, you should provide web links to websites, blogs, team reports, | ||
142 | 126 | mailing list archives etc. that confirm the points you make on the application. | ||
143 | 127 | * Be Concise and Clear! - while the LoCo Council do not want to see thousands | ||
144 | 128 | of words, we do want to be able to gain a full understanding of the teams | ||
145 | 129 | past experience, current activities, and future goals, as well as how those | ||
146 | 130 | will be achieved. | ||
147 | 131 | |||
148 | 132 | Reapproval | ||
149 | 133 | ---------- | ||
150 | 134 | |||
151 | 135 | Approved Teams are re-assessed every *two* years using the same procedure as | ||
152 | 136 | described above. The reapproval application wiki page should summarize the LoCo | ||
153 | 137 | Team’s accomplishments of the past two years and outline plans for the future. | ||
154 | 138 | The reapproval application follows the naming convention as | ||
155 | 139 | *<LoCoTeamName>ReApprovalApplicationYEAR* ex: *UKTeam/ReApprovalApplication2012* | ||
156 | 140 | |||
157 | 141 | Each cycle, LoCo contacts from LoCo Teams with approaching review dates will be | ||
158 | 142 | contacted privately and asked to submit applications. If those LoCo Teams are | ||
159 | 143 | prepared for re-approval, the team’s contact will add the application to the | ||
160 | 144 | LoCo Council Meeting Agenda and/or Bug Report. The LoCo Council will vote on | ||
161 | 145 | the team’s re-approval application. The vote can be done via the Bug Report or | ||
162 | 146 | at a LoCo Council Meeting. This flexibility is allowed to account for variations | ||
163 | 147 | in timezones. | ||
164 | 148 | |||
165 | 149 | .. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_! | ||
166 | 0 | 150 | ||
167 | === modified file 'adk/locoteams-running.rst' | |||
168 | --- adk/locoteams-running.rst 2012-12-12 14:22:03 +0000 | |||
169 | +++ adk/locoteams-running.rst 2012-12-17 15:58:22 +0000 | |||
170 | @@ -68,11 +68,25 @@ | |||
171 | 68 | which members can create regional meeting pages with details of where and | 68 | which members can create regional meeting pages with details of where and |
172 | 69 | when people will meet. | 69 | when people will meet. |
173 | 70 | 70 | ||
174 | 71 | Getting your Team approved | ||
175 | 72 | -------------------------- | ||
176 | 73 | |||
177 | 74 | Once you have all your meetings and events in place to happen periodically, | ||
178 | 75 | Over a period of time you can apply for approval from the LoCo Council. | ||
179 | 76 | The process typically needs the LoCo Council to have confidence that the team | ||
180 | 77 | is up and running and performing well. This requires some evidence that | ||
181 | 78 | the team has established various resources and is actively working on different | ||
182 | 79 | things and working well and is more than one person. To become approved the team | ||
183 | 80 | needs to create a wiki page that outlines a number of things to do with the | ||
184 | 81 | group, and has supporting evidence. | ||
185 | 82 | |||
186 | 71 | Discover More | 83 | Discover More |
187 | 72 | ============= | 84 | ============= |
188 | 73 | 85 | ||
189 | 74 | * :doc:`LoCo Team Activities<./locoteams-activities>` - learn the different | 86 | * :doc:`LoCo Team Activities<./locoteams-activities>` - learn the different |
190 | 75 | things you can do in the team. | 87 | things you can do in the team. |
192 | 76 | 88 | * :doc:`Getting LoCo Team Approved<./locoteams-approval>` - learn how can you | |
193 | 89 | drive your team towards approval from the LoCo council and benifits of being | ||
194 | 90 | an approved LoCo team. | ||
195 | 77 | 91 | ||
196 | 78 | .. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_! | 92 | .. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_! |
197 | 79 | 93 | ||
198 | === modified file 'debian/changelog' | |||
199 | --- debian/changelog 2012-12-13 14:55:24 +0000 | |||
200 | +++ debian/changelog 2012-12-17 15:58:22 +0000 | |||
201 | @@ -1,3 +1,9 @@ | |||
202 | 1 | ubuntu-adk (0.2) raring; urgency=low | ||
203 | 2 | |||
204 | 3 | * Add Locoteams approval reference. | ||
205 | 4 | |||
206 | 5 | -- Bhavani Shankar <bhavi@ubuntu.com> Mon, 17 Dec 2012 13:24:46 +0530 | ||
207 | 6 | |||
208 | 1 | ubuntu-adk (0.1) raring; urgency=low | 7 | ubuntu-adk (0.1) raring; urgency=low |
209 | 2 | 8 | ||
210 | 3 | * Initial release. | 9 | * Initial release. |
Thanks for the contribution, Bhavani!
I think this is a great start, but I think we should create a new page that outlines the approval process. This way you can explain:
* the difference between Approved and non-Approved teams.
* why teams should strive to be approved.
* how the approval process works.
* some tips and tricks for ensuring teams are successful.
Could you create locoteams- approvalprocess .rst and add this content and then re-submit? Thanks!