Teams up for re approval Re-approvals for O-Cycle

Laura Czajkowski laura at lczajkowski.com
Sat May 21 13:49:16 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To explain this a little more as there seems to be some confusion.  Paul
sent a mail to locoteams as well as sending a BUG to each of the team
owners which are up for renewal this cycle.

If your team owner received a bug  what that means is your team needs to
submit a re approval Application to the LoCo Council either one of two
ways 1) add it to the bug or 2) add your application to our council
meetings which we have monthly.

The reason we're doing it this way as it?s taken some time to get into
the swing of these re approvals, it started off via a wiki page and
emails, and now to creating a bug.  Now I do understand there is some
issues surrounding the bug being created so I?d like to explain that.

The bug is created namely for the loco council, it is a way for us to
track which teams need doing so, paultag block sent 27 bugs to us the
last day! thanks Paul!! Those bugs go to the teams, and we know during
this cycle we should receive some form of communication from them, if
the team owner/contact/leader  which have been added to the bug leaves a
comment on the bug, we all get it, if they chose to mail us we copy the
mail into the bug, this means all the information is in on place.

The bug also acts as a way to keep the loco council up to date for
ourselves, as you can imagine 27 teams is a lot to get through!
Processing these via the meetings may not be possible as we only have 1
hour and we do sometimes go over, we also appreciate not every team can
make the meeting, and if it's done over mail it gets drawn out, trust
me, we've tried it that way also.

The bug also acts as a way for us to poke one another and go OI GO VOTE
AND READ THE APPLICATION. The bug is made open at the end of the voting
system, or if the vote has happened via the IRC meeting the bug is
updated with the information, comments and logs from it to the bug.

There have been comments as to why the bug isn't open from the start and
I'd like to address that, it's really rather simple we don't want the
bug taken over with people going have you voted yet, are you ready yet,
we love our team, we know you love your team, our team is awesome, yes
we know this also.  The bug is just a way we've found useful to help us
help teams.

In order to to get ready for a re approval, I suggest creating a new
wiki page called re approval application this will help you keep track
of your team, and also give past and future team members an insight into
how your team has progressed.  If you want at any stage poke one of the
council members to have a look over it and give you some pointers, we
don?t want to un approve you, we are here to help you. Tell us how you
do things in your team, share the work load, how you get the word out
there about Ubuntu, show us you are a community! PHOTOS MAKE US VERY
HAPPY!!

As for a time frame, when you are ready, either add it to the bug, or
add to the meetings we have each month, please pretty please do not
leave all of this till October!!!! Or we shall cry!

https://wiki.ubuntu.com/LoCoCouncil/LoCoTeamReApproval

The following teams are selected for this cycles re approval and should
have been contacted:

Thai Loco Team:

Ubuntu Venezuela Team:

Ubuntu DK:

Ubuntu UK:

Ubuntu Team Philippines:

Pennsylvania ? US LoCo Team:

Ubuntu-Michigan:

Ubuntu Maryland LoCo Team:

Ubuntu Malaysia LoCo Team:

Ubuntu Japanese Team:

Ubuntu Ireland:

Ubuntu El Salvador Team:

Ubuntu Swiss Team:

Ubuntu Portugal:

Ubuntu Polish LoCo Team:

Ubuntu Perú:

Ubuntu Norge:

Ubuntu Croatian Advocates:

Thai Loco Team:

Ubuntu Tamil Team:

Ubuntu Israel:

Arizona LoCo Team:

Ubuntu New York State:

Ubuntu California:

Georgia LoCo:

Ubuntu Brazilian Users:

Argentina LoCo:

Ubuntu China LoCo Team

Laura on behalf of the Ubuntu LoCo CouncilT

- -- 

https://wiki.ubuntu.com/czajkowski
http://www.lczajkowski.com
Skype: lauraczajkowski


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN18LaAAoJECUQy5EY50eFIc0H/34kxieN/ZJJ0ChRwWSokcLZ
MxYwvLNPoN6HVI9EejU00bWOar6cvho6b7hMarAQEKJnFLcoDiuuJWh2GIBYjkjA
59tGX72IosBJu/3P82E01vEWVkuw749/JWrx2j+4Ikw22gVrawEXlr4NJt33N7qn
GQkPrsjetbPp9ZdjbyCezj9s6PyS2PpHcTcA+6Sx15/zC+hPaple+8bhdMLrcr7L
jaejarGq0BnWq+ucR34OXT4b7l2G1saC4zIzVXX7QPSEjYJ4lStZTgTVFDWWwMbo
79n1MvYQ4tGbrB6Fx2hrZ5V0+o7+wzhjkP3B3j/y++eLo0/dqSg3lqyrzAu4Rsk=
=sEyo
-----END PGP SIGNATURE-----



More information about the loco-contacts mailing list