Merge lp:~bhavi/uak/add-locoteam-approval into lp:uak

[Bhavani Shankar]

Added a note on getting a loco team approved in /adk/locoteams-running.rst

Regards
Bhavani

[Jono Bacon (jonobacon)]

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!

review: Needs Fixing

[Javier López (javier-lopez)]

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)]

> 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!

Thanks Jono! and Javier for pointing out the typo, I'll work on the same and resubmit this evening.

Regards
Bhavani

[lp:~bhavi/uak/add-locoteam-approval]

61. By Bhavani Shankar on 2012-12-17

Added adk/locoteams-approval.rst containing lococouncil processes on approval

62. By Bhavani Shankar on 2012-12-17

Update the d/changelog

[Bhavani Shankar (bhavi)]

Dear Jono,

Updated the branch

Regards
Bhavani

[lp:~bhavi/uak/add-locoteam-approval]

63. By Bhavani Shankar on 2012-12-17

Few more markup changes

64. By Bhavani Shankar on 2012-12-17

fix typos

[Bhavani Shankar (bhavi)]

Dear Jono,

Please review latest commit 64 as I have done few more markup changes and fixed typos

Regards
Bhavani

[lp:~bhavi/uak/add-locoteam-approval]

65. By Bhavani Shankar on 2012-12-17

make reference to locoteams-approval in /adk/documentation.rst

[Bhavani Shankar (bhavi)]

Referenced locoteams-approval.rst in /adk/documentation.rst too (Commit 65)

Regards
Bhavani

[lp:~bhavi/uak/add-locoteam-approval]

66. By Bhavani Shankar on 2012-12-17

Bit more rewording :-) Thanks to Chris and Sergio

[Jono Bacon (jonobacon)]

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! :-)

review: Approve

[Bhavani Shankar (bhavi)]

Thanks Jono for going through the review. We will get the help of a native speaker at the time of submission.

Regards
Bhavani

=== modified file 'adk/documentation.rst'
--- adk/documentation.rst	2012-12-14 01:39:31 +0000
+++ adk/documentation.rst	2012-12-17 15:58:22 +0000
@@ -12,6 +12,7 @@
    locoteams-joining
    locoteams-creating
    locoteams-running
+   locoteams-approval
 
 Spreading The Word
 ------------------

=== added file 'adk/locoteams-approval.rst'
--- adk/locoteams-approval.rst	1970-01-01 00:00:00 +0000
+++ adk/locoteams-approval.rst	2012-12-17 15:58:22 +0000
@@ -0,0 +1,149 @@
+================================
+Getting your LoCo Team approved.
+================================
+
+Purpose of this document
+-------------------------
+
+The purpose behind this document is to explain what a team needs to do in order 
+to get approved by the LoCo Council.
+
+Types of LoCo Teams
+-------------------
+
+There are two types of LoCo teams in ubuntu basically:
+
+ * 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 has demonstrated sustained 
+   team activity. They have met all of  the requirements, and they 
+   have established resources up and running, and there should be a 
+   clear evidence that the team is working well. 
+
+Benifits of getting approved
+-----------------------------
+
+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: 
+
+ * Ubuntu CD Packs `CD packs are given each cycle <https://wiki.ubuntu.com/LoCoGettingCds>`_!
+
+ * Conference Packs - `Given when there is a conference in your locality and you are representing Ubuntu <https://wiki.ubuntu.com/UbuntuAtConferences>`_!
+
+The Process of getting approved
+--------------------------------
+
+The first question one tends to ask is if the team is ready for approval, If
+the team leaders and the members answer is 'yes', then they need to know a few
+things about the application process.
+
+Purpose
+--------
+
+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. 
+
+.. Note:: The real concern of the LoCo Council is whether the loco team remains 
+   active over a period of time.
+
+Application Crieteria
+----------------------
+
+The LoCo Council will use the following criteria when evaluating team 
+applications:
+
+* Team naming standards followed.
+
+* Team Resources. (which may be exempted for countries where there is less 
+   developed internet infrastructure)
+
+Team resources include the below list in general:
+   * IRC
+   * Launchpad
+   * Team Wiki Page
+   * Team Mailing list
+   * Team Forum on Ubuntu Forums <http://ubuntuforums.org>
+
+* Experience - Experience will be evaluated on the below questions typically:
+
+   * What has the team been doing?
+
+   * Has the team done any advocacy, exhibitions, support or other activities? 
+     The recommendation is that the team has done at least three global 
+     activities such as 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 approval 
+     depends on activity levels a team
+
+   * Has the applying team demonstrated the ability to meet future goals and 
+     have these goals (essentially a roadmap) 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.
+
+* Future Planning - 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.
+ 
+* Having Ubuntu Members in the team - 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.
+
+How to write an approval application?
+-------------------------------------
+
+The success of a team’s application to become an approved Ubuntu LoCo team 
+largely rests in ts application wiki page. `An example wiki page is available
+here <https://wiki.ubuntu.com/LoCoExampleApplication>`_ :-) Showing the page the LoCo
+team should form when applying for approval with the naming convention 
+*<LoCoTeam>/ApprovalApplication* ex: *UKTeam/ApprovalApplication*
+
+Application Tips
+----------------
+
+ * Do not change the structure of the sample page reference given above.
+ * 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.
+ * Be Concise and Clear! - while 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. 
+
+Reapproval
+---------- 
+
+Approved Teams are re-assessed every *two* years using the same procedure as
+described above. The reapproval application wiki page should summarize the LoCo 
+Team’s accomplishments of the past two years and outline plans for the future.  
+The reapproval application follows the naming convention as
+*<LoCoTeamName>ReApprovalApplicationYEAR* ex: *UKTeam/ReApprovalApplication2012*
+
+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 
+LoCo Council Meeting Agenda 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.  
+
+.. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_!

=== modified file 'adk/locoteams-running.rst'
--- adk/locoteams-running.rst	2012-12-12 14:22:03 +0000
+++ adk/locoteams-running.rst	2012-12-17 15:58:22 +0000
@@ -68,11 +68,25 @@
 which members can create regional meeting pages with details of where and
 when people will meet.
 
+Getting your Team approved
+--------------------------
+
+Once you have all your meetings and events in place to happen periodically, 
+Over a period of time you can  apply for approval from the LoCo Council. 
+The process typically needs the LoCo Council to have confidence that the team 
+is up and running and performing well. This requires some evidence that 
+the team has established various resources 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 that outlines a number of things to do with the 
+group, and has supporting evidence. 
+
 Discover More
 =============
 
  * :doc:`LoCo Team Activities<./locoteams-activities>` - learn the different
    things you can do in the team.
-
+ * :doc:`Getting LoCo Team Approved<./locoteams-approval>` - learn how can you
+   drive your team towards approval from the LoCo council and benifits of being
+   an approved LoCo team.
 
 .. Note:: Have more more questions? Be sure to `ask them on Ask Ubuntu <http://www.askubuntu.com//questions/ask?tags=locoteams>`_!

=== modified file 'debian/changelog'
--- debian/changelog	2012-12-13 14:55:24 +0000
+++ debian/changelog	2012-12-17 15:58:22 +0000
@@ -1,3 +1,9 @@
+ubuntu-adk (0.2) raring; urgency=low
+
+  * Add Locoteams approval reference.
+
+ -- Bhavani Shankar <[e-mail]>  Mon, 17 Dec 2012 13:24:46 +0530
+
 ubuntu-adk (0.1) raring; urgency=low
 
   * Initial release.