LoCoTeamReApproval

Differences between revisions 1 and 97 (spanning 96 versions)
Revision 1 as of 2009-12-15 15:11:14
Size: 2365
Editor: 13
Comment:
Revision 97 as of 2011-07-22 13:20:28
Size: 2989
Editor: czajkowski
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(LoCoCouncil/SubHeader)>>

||<tablestyle="font-size: 0.85em; border: none; background-color: #f1f1ed; "> [[/ca|català]] || [[/de|deutsch]] || [[/es|español]] || [[/cz|čeština]] || [[/it|italiano]] || [[/kor|한국어(Korean)]] || [[/el|ελληνικά]] || [[/pt_br|Português (Brasil)]] || [[/fr|français]] || Add your language here ||

## TRANSLATORS: in order to create a translated version of this page, please create a subpage with your language code (http://www.loc.gov/standards/iso639-2/php/code_list.php) and add it to the table above. You can check how other folks have translated the page for examples.
Line 4: Line 9:
The LoCo Council has been tasked with identifying Approved LoCo teams which were approved over 2 years ago and thus are due for re-approval.The criteria for reapproval is the same as for approval which is outlined https://wiki.ubuntu.com/LoCoGettingApproved and the LoCo council guidelines can be found at https://wiki.ubuntu.com/LoCoCouncil/TeamApprovalGuidelines . The Lo``Co Council has been tasked with identifying Approved Lo``Co teams which were approved over 2 years ago and thus are due for re-approval. The criteria for re approval is the same as for approval which is outlined on the [[LoCoGettingApproved|getting approved instructions]] and the Lo``Co Council guidelines can be found at [[LoCoCouncil/TeamApprovalGuidelines|the team approval guidelines]].
Line 6: Line 11:
== Reapproval Process == It should be noted that from the day your Lo``Co is approved, you should continue to document all events and history of your LoCo for this re approval process to make it clear and visible to all.
Line 8: Line 13:
The following process is used when identifying and then qualifying a LoCo team for re-approval. == Re approval Process ==
Line 10: Line 15:
 * The LoCo Council identifies teams which have been approved for more than 2 years
 * A member of the LoCo Council is selected to be the point of contact with the LoCo team for re-approval
 * The LoCo Council point of contact will attempt to contact the LoCo team which is up for re-approval
  * The LoCo Council will attempt to contact the LoCo team a reasonable number of times (3) over a reasonable period (1 month)
  * If the LoCo Council receives no response from the LoCo team then the LoCo team will be unapproved
 * The LoCo Council will request that member(s) of the LoCo team attend the next (or another convenient) LoCo Council meeting
 * During the meeting the LoCo Council will go through the same approval process for re-approvals as they do for LoCo team approvals.
The following process is used when identifying and then qualifying a Lo``Co team for re-approval.
Line 18: Line 17:
== Reapproval List ==  * The Lo``Co Council identifies teams which have been approved for more than 2 years, on the LoCo directory
  * The Lo``Co Council will attempt to contact the Lo``Co team a reasonable number of times (3) over a reasonable period (1 month). We do this by creating a bug and emailing the team contact.
  * If the Lo``Co Council receives no response from the Lo``Co team then the Lo``Co team will be unapproved
 * The Lo``Co Council will request that member(s) of the Lo``Co team attend the next (or another convenient) Lo``Co Council meeting
 * During the meeting the Lo``Co Council will go through the same approval process for re-approvals as they do for Lo``Co team approvals.
 * If the time of the meeting does not suit, that is fine, we can conduct the meeting via the bug as all the information will be stored there.
Line 20: Line 24:
This is a _provisional_ list. It is not final. == LoCoCouncil Team ==
Line 22: Line 26:
 * Re-approve the teams
   * Belgian Local Community Team (TBD)
   * Colorado Ubuntu Local Team (TBD)
   * DCTeam LoCo (TBD)
   * Equip oficial d'ubuntaires (TBD)
   * Florida LoCo Team (TBD)
   * Georgia LoCo (TBD)
   * German Ubuntu LoCo Team (TBD)
   * Grupo Ubuntu Nicaragua (TBD)
   * Indiana LoCo Team (TBD)
   * Kurdish Kurmanji Team (TBD)
   * Lithuanian LoCo Team (TBD)
   * Pennsylvania - US LoCo Team (TBD)
   * Russian Team (TBD)
   * Thai Loco Team (TBD)
   * Ubuntu Australian Team (TBD)
   * Ubuntu Austria LoCo team (TBD)
   * Ubuntu Bangladesh (TBD)
   * Ubuntu Brazilian Users (TBD)
   * Ubuntu Canada Team (TBD)
   * Ubuntu Chicago LoCo Team (TBD)
   * Ubuntu Chile (TBD)
   * Ubuntu China LoCo Team (TBD)
   * Ubuntu Colombia (TBD)
   * Ubuntu Croatian Advocates (TBD)
   * Ubuntu Czech Republic (TBD)
   * Ubuntu DK (TBD)
   * Ubuntu Ecuador Team (TBD)
   * Ubuntu El Salvador Team (TBD)
   * Ubuntu Finland Team (TBD)
The members of the current Lo``Co Council you will hear from are regarding this re approval process are
 
 * Laura Czajkowski (czajkowski)
 * Alan Pope (popey)
 * Paul Tagliamonte (paultag)
 * Christophe Sauthier (huats)
 * Chris Crisafulli (itnet7)
 * Leandro Gómez (leogg)

## TRANSLATORS: there is no need to translate this page after this point.
##
## If you nevertheless want to include the (untranslated) list of re-approvals, you can do it by including this at the end of your translated page (removing the backticks (``) first):
##
## <<Include(LoCoCouncil/LoCoTeamReApproval, , from="Start``ReapprovalList", to="End``ReapprovalList")>>

## EDITORS: do not remove the tags starting with ## below when editing.
##
##

http://wiki.ubuntu.com/LoCoCouncil

Council Resources to help Teams
LoCoCouncil
LoCo Team Approval
LoCo Team Re Approval
Best Practices and Guidelines for Teams
LoCo Council Standards

irc-small.png

Contact
LoCo Council Meetings IRC
LoCo Council ML <loco-council AT lists DOT ubuntu DOT com>

contacts.png

LoCo Council Team Activities
LoCo Council Meeting Agenda
LoCo Council Meeting Minutes
LoCo Council Team Reports

Summary

The LoCo Council has been tasked with identifying Approved LoCo teams which were approved over 2 years ago and thus are due for re-approval. The criteria for re approval is the same as for approval which is outlined on the getting approved instructions and the LoCo Council guidelines can be found at the team approval guidelines.

It should be noted that from the day your LoCo is approved, you should continue to document all events and history of your LoCo for this re approval process to make it clear and visible to all.

Re approval Process

The following process is used when identifying and then qualifying a LoCo team for re-approval.

  • The LoCo Council identifies teams which have been approved for more than 2 years, on the LoCo directory

    • The LoCo Council will attempt to contact the LoCo team a reasonable number of times (3) over a reasonable period (1 month). We do this by creating a bug and emailing the team contact.

    • If the LoCo Council receives no response from the LoCo team then the LoCo team will be unapproved

  • The LoCo Council will request that member(s) of the LoCo team attend the next (or another convenient) LoCo Council meeting

  • During the meeting the LoCo Council will go through the same approval process for re-approvals as they do for LoCo team approvals.

  • If the time of the meeting does not suit, that is fine, we can conduct the meeting via the bug as all the information will be stored there.

LoCoCouncil Team

The members of the current LoCo Council you will hear from are regarding this re approval process are

  • Laura Czajkowski (czajkowski)
  • Alan Pope (popey)
  • Paul Tagliamonte (paultag)
  • Christophe Sauthier (huats)
  • Chris Crisafulli (itnet7)
  • Leandro Gómez (leogg)

LoCoCouncil/LoCoTeamReApproval (last edited 2013-10-09 21:21:36 by jose)