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 | locoteams-joining |
6 | locoteams-creating |
7 | locoteams-running |
8 | + locoteams-approval |
9 | |
10 | Spreading The Word |
11 | ------------------ |
12 | |
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 | +================================ |
18 | +Getting your LoCo Team approved. |
19 | +================================ |
20 | + |
21 | +Purpose of this document |
22 | +------------------------- |
23 | + |
24 | +The purpose behind this document is to explain what a team needs to do in order |
25 | +to get approved by the LoCo Council. |
26 | + |
27 | +Types of LoCo Teams |
28 | +------------------- |
29 | + |
30 | +There are two types of LoCo teams in ubuntu basically: |
31 | + |
32 | + * Unapproved Teams - These are teams that have not met all the requirements |
33 | + to apply for Approval. They have either recently formed, or have existed for |
34 | + a while without an established standard team workflow, and have shown a |
35 | + limited amount of sustained team activity. |
36 | + |
37 | + * Approved Teams - An approved team is a team that has demonstrated sustained |
38 | + team activity. They have met all of the requirements, and they |
39 | + have established resources up and running, and there should be a |
40 | + clear evidence that the team is working well. |
41 | + |
42 | +Benifits of getting approved |
43 | +----------------------------- |
44 | + |
45 | +An approved team is eligible for certain benefits such as marketing materials. |
46 | +An approved team is also considered official by the Ubuntu project. |
47 | +The following are the current benefits: |
48 | + |
49 | + * Ubuntu CD Packs `CD packs are given each cycle <https://wiki.ubuntu.com/LoCoGettingCds>`_! |
50 | + |
51 | + * Conference Packs - `Given when there is a conference in your locality and you are representing Ubuntu <https://wiki.ubuntu.com/UbuntuAtConferences>`_! |
52 | + |
53 | +The Process of getting approved |
54 | +-------------------------------- |
55 | + |
56 | +The first question one tends to ask is if the team is ready for approval, If |
57 | +the team leaders and the members answer is 'yes', then they need to know a few |
58 | +things about the application process. |
59 | + |
60 | +Purpose |
61 | +-------- |
62 | + |
63 | +The purpose of the LoCo Team approval process is to ensure that a team is an |
64 | +active resource for Ubuntu enthusiasts in a localized geographical area and |
65 | +that it offers both help and information to those who are interested in |
66 | +contributing to the Ubuntu Community. |
67 | + |
68 | +.. Note:: The real concern of the LoCo Council is whether the loco team remains |
69 | + active over a period of time. |
70 | + |
71 | +Application Crieteria |
72 | +---------------------- |
73 | + |
74 | +The LoCo Council will use the following criteria when evaluating team |
75 | +applications: |
76 | + |
77 | +* Team naming standards followed. |
78 | + |
79 | +* Team Resources. (which may be exempted for countries where there is less |
80 | + developed internet infrastructure) |
81 | + |
82 | +Team resources include the below list in general: |
83 | + * IRC |
84 | + * Launchpad |
85 | + * Team Wiki Page |
86 | + * Team Mailing list |
87 | + * Team Forum on Ubuntu Forums <http://ubuntuforums.org> |
88 | + |
89 | +* Experience - Experience will be evaluated on the below questions typically: |
90 | + |
91 | + * What has the team been doing? |
92 | + |
93 | + * Has the team done any advocacy, exhibitions, support or other activities? |
94 | + The recommendation is that the team has done at least three global |
95 | + activities such as Global Jam Participation, Bug Jam participation, Launch parties, |
96 | + Release parties, etc |
97 | + Eight months of activity prior to applying and detailed team reports are |
98 | + also recommended. However, it is important to understand, that approval |
99 | + depends on activity levels a team |
100 | + |
101 | + * Has the applying team demonstrated the ability to meet future goals and |
102 | + have these goals (essentially a roadmap) been successfully communicated to |
103 | + the LoCo Council? |
104 | + |
105 | + * Has the applying team demonstrated continually growing its member base as |
106 | + to ensure that team leaders and highly active participants aren't setting |
107 | + themselves up for burnout or withdrawal from the community, thus creating |
108 | + an inactive team in a short time after approval? |
109 | + |
110 | + * Has the applying team indicated to the LoCo Council its understanding |
111 | + about what it means to be an Ubuntu LoCo Team and demonstrates |
112 | + how its mission differs from that of a LUG. |
113 | + |
114 | +* Future Planning - Teams which have future events planned gives the |
115 | + LoCo Council confidence that a team is committed to staying active and |
116 | + building their team. These future planned activities should be laid out |
117 | + and included in the roadmap, and added to the LTP (LoCo Team Portal) |
118 | + if at all possible. |
119 | + |
120 | +* Having Ubuntu Members in the team - Are there Ubuntu members on the team? |
121 | + Having an Ubuntu Member in a LoCo is not required; but however, |
122 | + Team Members with Ubuntu Membership shows wider Ubuntu involvement of not |
123 | + only the Ubuntu Member(s) but of the scope and knowledge of the team as a |
124 | + whole. |
125 | + |
126 | +How to write an approval application? |
127 | +------------------------------------- |
128 | + |
129 | +The success of a team’s application to become an approved Ubuntu LoCo team |
130 | +largely rests in ts application wiki page. `An example wiki page is available |
131 | +here <https://wiki.ubuntu.com/LoCoExampleApplication>`_ :-) Showing the page the LoCo |
132 | +team should form when applying for approval with the naming convention |
133 | +*<LoCoTeam>/ApprovalApplication* ex: *UKTeam/ApprovalApplication* |
134 | + |
135 | +Application Tips |
136 | +---------------- |
137 | + |
138 | + * Do not change the structure of the sample page reference given above. |
139 | + * Use as many links and references as possible - this is essential! |
140 | + In the Roadmap and Experience sections and elsewhere on the Approval Application |
141 | + Wiki, you should provide web links to websites, blogs, team reports, |
142 | + mailing list archives etc. that confirm the points you make on the application. |
143 | + * Be Concise and Clear! - while the LoCo Council do not want to see thousands |
144 | + of words, we do want to be able to gain a full understanding of the teams |
145 | + past experience, current activities, and future goals, as well as how those |
146 | + will be achieved. |
147 | + |
148 | +Reapproval |
149 | +---------- |
150 | + |
151 | +Approved Teams are re-assessed every *two* years using the same procedure as |
152 | +described above. The reapproval application wiki page should summarize the LoCo |
153 | +Team’s accomplishments of the past two years and outline plans for the future. |
154 | +The reapproval application follows the naming convention as |
155 | +*<LoCoTeamName>ReApprovalApplicationYEAR* ex: *UKTeam/ReApprovalApplication2012* |
156 | + |
157 | +Each cycle, LoCo contacts from LoCo Teams with approaching review dates will be |
158 | +contacted privately and asked to submit applications. If those LoCo Teams are |
159 | +prepared for re-approval, the team’s contact will add the application to the |
160 | +LoCo Council Meeting Agenda and/or Bug Report. The LoCo Council will vote on |
161 | +the team’s re-approval application. The vote can be done via the Bug Report or |
162 | +at a LoCo Council Meeting. This flexibility is allowed to account for variations |
163 | +in timezones. |
164 | + |
165 | +.. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_! |
166 | |
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 | which members can create regional meeting pages with details of where and |
172 | when people will meet. |
173 | |
174 | +Getting your Team approved |
175 | +-------------------------- |
176 | + |
177 | +Once you have all your meetings and events in place to happen periodically, |
178 | +Over a period of time you can apply for approval from the LoCo Council. |
179 | +The process typically needs the LoCo Council to have confidence that the team |
180 | +is up and running and performing well. This requires some evidence that |
181 | +the team has established various resources and is actively working on different |
182 | +things and working well and is more than one person. To become approved the team |
183 | +needs to create a wiki page that outlines a number of things to do with the |
184 | +group, and has supporting evidence. |
185 | + |
186 | Discover More |
187 | ============= |
188 | |
189 | * :doc:`LoCo Team Activities<./locoteams-activities>` - learn the different |
190 | things you can do in the team. |
191 | - |
192 | + * :doc:`Getting LoCo Team Approved<./locoteams-approval>` - learn how can you |
193 | + drive your team towards approval from the LoCo council and benifits of being |
194 | + an approved LoCo team. |
195 | |
196 | .. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_! |
197 | |
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 | +ubuntu-adk (0.2) raring; urgency=low |
203 | + |
204 | + * Add Locoteams approval reference. |
205 | + |
206 | + -- Bhavani Shankar <bhavi@ubuntu.com> Mon, 17 Dec 2012 13:24:46 +0530 |
207 | + |
208 | ubuntu-adk (0.1) raring; urgency=low |
209 | |
210 | * 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!