Czajkowski

Following on from my post  last week regarding the up to date conference packs and the new banners for APPROVED teams, we have created a new wiki page we need the team contact to fill in. Again, a big thank you goes to Canonical for making this possible!

There is an enormous amount of useful information on wiki.ubuntu.com however there is also a lot of duplicate triplicate and redundant material on there also.  This weekend why not get your loco reviewing a section of the wiki and help to clear up some of the pages.  I’ve noticed sometimes that a page was created in lower  case and then never used as someone else created the wiki in upper case, well then the one not used should be removed.

The LoCo Council are going to be looking over the sections of the pages LoCo Teams and if you want to help that would be great.  A lof of that information is on the LoCo Directory – I’d hope by now folks know about the directory………………

If you go through the wiki and find all the pages that are out of date, unused or the information is over on the LD already  add the Category “CategoryLoCoObsoleteâ€? to it.   We the LC will review the pages and decide their fate.  So don’t be worried.

FYI — to add a Category, just append:

----
CategoryLoCoObsolete

to the bottom of a page. If there’s already a Category, do this:

----
CategoryAwesomeTag CategoryLoCoObsolete

I’ll be in #ubuntu-locoteams on Satuday from 9am UTC – 4pm UTC and on Sunday from 10am UTC – 7pm UTC

I am very pleased to announce the new Conference packs for LoCo Teams, this came from a session at UDS-M in Brussels of this year but also was something we’ve been looking at for a while.  So it’s great to see an action item marked DONE (which makes bacon happy) but also has a positive effect for a lot of people.  We wanted to encourage teams to become and stay an approved LoCo Team and how we could possibly help. With that in mind we looked what was currently available, we talked to many people on what they thought might be helpful to them. When you attend an event you are representing your team and Ubuntu, so to present yourself in a professional manner we looked at things like a banner for teams.

The LoCo Council would like to thank Jane Silber for this as she was one of the people in the session who encouraged us to bring this action item to light and also we’ve had great help from Cezzaine Haugh and also Canonical for making this happen for all LoCo Teams, thank you very much!

The following has been approved for conference packs, and the wiki has been updated to reflect this

Once off gift to approved loco teams
When a LoCo Team is approved, part of what they need to do is nominate someone to receive and manage their LoCo Welcome Pack, which Canonical will provide.

• x1 PVC banner – (one design only)
• x1 Table cloth – (one design only)

Pack A – Approved loco teams

• x55 Lanyards
• x2 caps
• x25 mixed sticker sheets
• x25 pin-badges – (These have yet to be produced)
• x2 t-shirts (release t-shirt) for give-away/booth staff
• x1 Official Ubuntu Book (prize/give-away) – (Only while stocks last, we will not produce anymore than the amount received after each release)
• CDs (250 Desktop, 25 Server, 25 Kubuntu) – (To be requested via shipit as per usual process)
  
• Name badges (Loco to produce their own)
• Ubuntu leaflets (Loco to create a project to produce their own ideas)
• Ubuntu video (Canonical to provide – will be available for d/l on wiki once completed)
  

Pack B – UnApproved loco teams

• x25 mixed sticker sheets
• x55 Lanyards
• CDs (75 Desktop) – (To be requested via shipit as per usual process)
• Name badges (Loco to produce their own)
• Ubuntu leaflets (Loco to create a project to produce their own ideas)
• Ubuntu video (Canonical to provide – will be available for d/l on wiki once completed)

Also discussed and decided last week on was:

• Ubuntu leaflets – not relevant in most countries due to various languages. Loco council will introduce a community driven project for loco teams to design their own Ubuntu leaflets based on brand guidelines and access to assets. Assets for these can be found at: http://design.canonical.com/the-toolkit/ubuntu-brand-guidelines/
• Name-badge designs - this is mainly when hosting their own events. Again Loco’s to create their own using assets and brand guidelines.
• Ubuntu video to run on machines at events – Canonical is currently working on a generic Ubuntu video in English and a few other languages – this will be added to the wiki page once completed.

We now have this fantastic all in one place information on teams, global and local events.  It makes finding information for everyone a lot easier.  It’s come on a long way and looks rather pretty also and is still being worked on there are bugs logged for some issues so with every week there are new improvements coming.

What I have noticed however is the amount of teams there on the LD with not up to date information, no wiki page listed, no mailing list, no website, no IRC channel listed or any information about themselves and in many cases most of the teams are providing this help.  We need you to update your information, that’s either through your team leader, point of contact or you have admins set up on launchpad who can edit the loco directory,  if you see your team has other resources that are not listed there PLEASE ASK OF YOUR TEAM TO ADD IT!

This morning there were 69 teams listed on the LD with no fix abode they had no country listed against them.  I’ve gone in and added them all, bar 5 which I need help on.  In the LD Language is a mandatory field, I’ve added the one language against each team, you can select more, PLEASE SELECT MORE if you have more than one language in your team.

Think of the directory from a new persons point of view a yellow pages of information they can access.  If someone was in your area and wanted to learn more about your team, that information should be visible.  They shouldn’t have to join a mailing list or an IRC channel just to find out where your wiki page is located.

Also a really handy tool for people who are travelling is they can view the LD and see if there are any events going on in the area so they can drop by and say hi.

After spending some time on wikpedia and learning a lot about other countries and their languages I was able to reduce the list to following 5

*edit: All teams are now listed under a country! including the 5 homeless ones above!  See I won’t be beaten!

I’ve had some time recently to review a lot of wiki applications for LoCos.  It is truly amazing the amount of work some teams do and is a great source of ideas to try for other teams.

With that said, I’ve also seen some wiki pages which are less than clear on what the team is doing which makes it very hard to judge. So I thought I’d put down some best practices to make it clearer what is expected.

So firstly let’s recap:

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.

Now it is safe to say some teams do not continue documenting their work so when it comes to re approval time it’s panic stations, all hands on deck!  Things you can do to help elevate this are the following

• Use the LoCo Directory to log all of your events it will make it easier to write up about them and possibly in the future link to past events
• MONTHLY Reports folks, only a handful of teams use them and there are more teams there that SHOULD be writing monthly reports, list your IRC meeting, any real life meet up, projects people are working on in relation to Ubuntu.
• Take photos of your events it’ll help in the long run, assign someone at each event to take photos and even create a gallery in one place to link to them

When it comes to the creation of the Application be it for Approval or ReApproval it’s the same thing just NAMED DIFFERENTLY.  You just need to document it. LOTS OF DETAILS PLEASE! We’d rather have too much then not enough details as the meeting is short and we have a lot of teams to get through.

What is expected of a LoCo Team

• All teams must provide the Council with a wiki page (in English preferably) with details outlined in https://wiki.ubuntu.com/LoCoGettingApproved.
• The team should have demonstrated a significant and sustained contribution to the Ubuntu community, from participating in a ubuntu-related project, documentation, localization, development (bug reports and packaging, marketing, participating in FOSS events, release parties. All of these abiding the Code of Conduct and following the LoCo team project’s policies.
• The team should have public wiki pages and an open public mailing list set up, these initial resources indicate open participation and they provide the Council with a log of the Team’s activity.
• The team should have an entry in https://wiki.ubuntu.com/LoCoTeamList.
• The team should have been running for at least 4 months and have had a consistent set of interactions with each other (council members should look at mailing list activity to assess how much activity there is) – you should also assess IRC activity where applicable.
• The team should have a good roadmap and a good set of goals that they want to achieve, The Approved status is only a confirmation of their effort and it is also a commitment for further community activity.
• Leadership within the team must be build upon fairness and openess. The team must be in agreement with the fair apointment of a leader. This leader must represent the team in different situations in an efficient and effective manner, so the leader’s commitment towards the team is paramount.
• Has there been much conflict in the team, and if so, has it been resolved?: This is a very important sign of a team that is mature enough to face further situations in the future. Resolving issues is definetely a learning experience for LoCo Teams.
• Do the council feel this team could be trusted with additional resources such as additional CDs and being sent equipment for use?, Extra resources encourage more participation therefore, Being able to administer their resources is paramount, making sure that the team has what they need to promote ubuntu locally .
• Is this team setting a good example to the community? The Team must serve as role for new teams. The teams participation in LoCo team communication channels (Mailing list and IRC) is also encouraged, this way the team can be sure of that the great work done by this team gets shared with the whole LoCo Team community.

We also know that from time to time things don’t run smoothly, but how you cope  resolve and work things out is what we would like to know about.  It’s not a bad thing unless you hide it.  On the wiki page tell us how many is in your TEAM, IRC Channel, Mailing list, Forums and link to them.  We need the details, please don’t expect us to go looking for them, your team is one of a number of teams being reviewed.

When it comes to the IRC meeting if you are called for one, don’t come alone.  You are not in the team alone.  You don’t run the team alone.  BRING PEOPLE  TO CHEER THEIR TEAM ALONG!  It’s a team effort remember this when doing the application ASK FOR HELP, ASK  FOR CONTENT, you may miss something when someone else has blogged or taken photos of something.

Remember the LoCo Council idles in #ubuntu-locoteams if you want us to look over your application to give you some pointers just ask.  Remember being called for reapproval is a normal procedure and do not panic

Finally some really good applications just to give you an idea of what we’re looking for are the following

1. Colombian LoCo
2. Italian LoCo
3. French LoCo