Tag Archives: locoteams

May21

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

Posted on by
Teams up for re approval Re-approvals for O-Cycle

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!

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!

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:

May18

Re-approvals for O-Cycle rules and overview

Posted on by
Re-approvals for O-Cycle rules and overview

A copy of the mail that just went out to loco teams contacts mailing list for re approval for this cycle:

Good time of day, LoCo Teams!

It’s the time of year again! Re-approval time, so it’s time dust off the team photos and fire out some wiki edits!

We have a *ton* of teams to review this year, so we have some ground  rules that need to be adhered to very closely. We really hate (and we do) to be such a pedantic nit-picker, but it’s to the point where we can’t (as the LoCo Council) slip on reviewing teams. Not good for you, not good for us.

All you team administrators have been subscribed to the LP bug, if you are the contact (and not the admin), please contact your local friendly admin (or one of us on the LoCo Council) to get subscribed.

Here are the rules:

* If the application is submitted before the release of Ubuntu Oneiric, we will consider it. If it fails to come in on time, we *will* have to throw it away. We’re serious about this one.

* We’re looking for a few key things in particular this cycle. We really want to see up-to-date Team Reports. It’s really something that needs to be enforced. We’re also looking (as usual) for outstanding and sustained levels of activity.

* The sooner, the better! We really need to make sure we get to everyone in a sane way, and that means that we’re processing about 2 applications a week. That’s manageable, but not if everyone gets them in the month before release.  ( we have 27 teams to re approve between now and the end of October, please do not leave it till October to submit your application or you’ll make us cry!)

* By the way, we love you guys. We know you guys have done awesome work so far, and we can’t wait to see it! :)

Let’s get those apps in!

Keep rocking!

Paul Tagliamonte

On Behalf of the LoCo Council

P.S.

No extensions. We mean it!