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. -- unify names of teams on the LD https://bugs.launchpad.net/bugs/667432 You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. Status in LoCo Directory: Confirmed Bug description: Where do I find a particular team? Under - Region LoCo Team - Region Ubuntu LoCo Team - Ubuntu Region LoCo Team - Grupo Ubuntu Region - Region Team - ... At least any order by (English named) Region would be helpful. https://blueprints.launchpad.net/loco-directory/+spec/unify-names-of-teams _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
