unify names of teams on the LD

From Bug #667431

> Ubuntu Florida LoCo Team vs Ubuntu-fl vs ??

Nosir. It should be the URL name -- for instance:

https://launchpad.net/~ubuntu-us-florida

is technically wrong ( same with -us-ohio )

It should be:

https://launchpad.net/~ubuntu-us-fl
https://launchpad.net/~ubuntu-us-oh

The display name can be whatever -- it might even be nice to have some local flair with the name :)

There might also be a related bug that is caused by "ghost" teams -- the LD caching old team data and not picking up that they're gone ( because the manage lpupdate script only checks teams on locoteams, not teams in it's cache )

There is a blocking bug for this ( for the LD ) for sure ( before we can get teams to migrate over )

Cheers!

I've just run a *quick* audit. I'm not doing US state checking or anything. I'll add that in when I have a chance. Here's a short list of the teams currently with non-standard names.

Re: comment #1
https://wiki.ubuntu.com/LoCoTeamHowto says (and I remember California being told in the past) that it's supposed to be ubuntu-statename. If this has changed, that page should be updated too.

Paul, the ability to merge teams exists..

On Oct 27, 2010 3:56 PM, "Paul Tagliamonte" <email address hidden> wrote:

There might also be a related bug that is caused by "ghost" teams -- the
LD caching old team data and not picking up that they're gone ( because
the manage lpupdate script only checks teams on locoteams, not teams in
it's cache )

There is a blocking bug for this ( for the LD ) for sure ( before we can
get teams to migrate over )

Cheers!

--
unify names of teams on the LD
https://bugs.launchpad.net/bugs/667432
You received this bug no...
Status in LoCo Directory: Confirmed

Bug description:
Where do I find a particular team?

Under
- Region LoCo Team
- Region Ubuntu LoCo ...

Re: comment #4

Traditionally, resources with the older style names were considered "grandfathered in" to reduce confusion when resources disappear, although it seems like the current trend is to assume malice behind non-standardized team names.

@Robert Wall: How do you handle:

ubuntu-us-ga
ubuntu-ga

There's a name conflict. It should be ubuntu - isocode - *

@Chris: Yes, but it breaks the LD

@Nathan: Yes, that's true, in the past it was OK. At this point, we've poluted so much outside the ubuntu namespace, it's time to change for new teams ( strict ) and slowly migrate old teams.

@ Comment #4 as well --

From the wiki:

For Almost Everyone

Read LoCoTeamRegions for details on how to pick/name your team.

For the United States

    * IRC: ubuntu-us-SS (ie; ubuntu-us-ut for Utah, ubuntu-us-ny for New York, etc)
    * Launchpad: ubuntu-statename (ie; ubuntu-utah, ubuntu-newyork, etc)
    * Mailing List: ubuntu-us-stateprefix (ie; ubuntu-us-ut, ubuntu-us-ny, ubuntu-us-fl, etc)
    * Ubuntu Forums: state.ubuntuforums.org (ie; utah.ubuntuforums.org, etc)
    *

      Team Wiki: StateTeam (ie; MassachusettsTeam, OhioTeam, FloridaTeam, etc)

Whups, looks like #4 is correct.

I'm wrong, and the wiki is right -- sorry.

The idea should stand, though. Teams are still not in-spec. The LP naming is still screwey and should be fixed up.

Enforcing standards on new team names is an excellent idea and has been done for a couple years as I understood it. :)

The big problem is that renaming legacy resources breaks a lot of things. There's never been a good way to handle this just in general, and probably warrants careful consideration.

The best thing to do is probably to make the LoCo Directory a little smarter and work a little harder for the corner cases.

As per a decision taken at UDS-P a compromise was reached where by the loco council agreed that the LTP developers could alter the main team page that lists all teams shall be renamed consistently having no effect on the loco team page itself