Sorry I am joining in a bit late on the discussion. As one of the guys who initially contributed to the code of the LoCo Directory, I thank you for the valuble feedback. We are unfortunate not t have this up and running somewhere for you to test run. I personally can't have it at home since my internet is not that good. But onse it is up we will have a proper testing period for you to give it some serious critical thought.
We tried hard to integrate launchpad with the LoCo Directory and the result was not as flexible as we would have wanted. With this initial release we want to mimic the funtionlity of the big list, this means not making too many changes from that pattern, we are aware of teams that have two or more contacts, but we stuck with the data structure from the wiki. Initially we needed to limit the number of people that could edit the teams entry in the LoCo directory, we narrowed that down to the Lauchpad Owner and the Launchpad Admins and this made sense. We can definetelly make changes to this structure in a maintenance release or something. but for the initial we want to stay as true to the data we have as posible. We have a very diverse LoCo Governance structure but most of them converge on having a liason with the wider ubuntu community, call it LoCo team contact. To request services and resources from the Ubuntu project, this liason is the person (or someone acting on her/his behalf with her/his consent) is the one that should communicate the needs of the team. example (requests CDs, request mailing lists, web hosting, etc). Does it make sense for this person to be the Team owner in Launchpad? The LoCo Directory devs certainly thought so. If you consider this not to be appropiate, I am sure we can work out a diferent way, but it will get added after the 0.1 release. If anyone would like to help out shape LoCo Directory, please head to https://wiki.ubuntu.com/LoCoDirectory and to https://launchpad.net/loco-directory and contribute with blueprints and bugs. This project is being written by volunteers of the Ubuntu comminity and we are trying to be as considerate as we can. Thanks for all the support and all the feedback Efrain Dave Walker escribió: > Martin Owens wrote: > > <SNIP> >> There isn't always a clear leader, we have team contacts (who connect a >> team to the wider loco community) and team leaders OR team councils. >> Those titles though are more internal affairs. >> >> Best to use clear language, so we don't get 5 people from a loco team >> council all claiming to be leader in launchpad. >> >> Martin, >> >> > Hi Martin, > > Well in that instance, you _could_ have a launchpad team: > ~ubuntu-XX-{contact|council|committee|board|etc} > > They *could* be the launchpad admin contact for the ~ubuntu-XX loco > team. This enables easy maintenance, and more important, is easily to > retrieve (and possibly cascade) via the launchpad API. > > I'm not saying i'm in favor of this solution, i'm just suggesting it. > I'm not certain the Launchpad LoCo Team admin *should* have to be the > overall LoCo Team {leader|committee|council|board|etc} . > > Kind Regards, > Dave Walker > > -- Efrain Valles https://launchpad.net/~effie-jayx Ubuntu LoCo Council Member Ubuntu Membership Board of the Americas Member Vento Developer https://launchpad.net/vento -- loco-contacts mailing list loco-contacts@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/loco-contacts
