Em Sáb, 2008-12-20 às 11:29 -0800, Karsten Wade escreveu: Having at least one sponsor from each team would be nice, but I am wondering how this could be organized. I have been a sponsor for a short time, but I already see a lack of information at FAS. Sometimes I can't tell for sure from which country the person is. I am giving priority for those ones who are in the queue for a longer time or for the ones from my team or languages. I think it is important to know who is the person before become his sponsor, but FAS don't give us enough information. Is there a language maintainer list in L10n infrastructure we can use to grant them sponsor status or we need to build one? Regards, Igor Pires Soares

Karsten Wade さんは書きました: "At least one sponsor from each team" would be simpler and easier. To organize, can we add the entry of "sponsor" under the Details section of each team? http://translate.fedoraproject.org/teams/ja It says in TQSG 2.9.2 'Introducing your self'; "Post a short self introduction http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/ to the fedora-trans-list mailing list and to the list of your local team." However current 2.6.4 'Joining the cvsl10n Group' is not clear enough. "An administrator is notified of your application, and offers to sponsor you. This may take between an hour and a few days. The membership notification will be emailed to you once sponsored." So shall we amend to?; "All administrators are notified of your application. Introduce yourself by following the section 2.9.2. Then your language administrator offers to sponsor you. This may take between an hour and a few days. The membership notification will be emailed to you once sponsored. Is anyway that we can send the message to those people, asking to follow the process which they might accidentally skip? Then for those who still do not respond, we can safely deny them. noriko

Igor Pires Soares さんは書きました: It makes sense to me too. Then that coordinator can upgrade anyone of his/her team as 'sponsor' if needed. You are right, wiki page would be faster. The page can be added here? http://fedoraproject.org/wiki/L10N noriko

2008/12/23 Noriko Mizumoto <noriko(a)redhat.com&gt;: Domingo Becker Spanish Team Coordinator (es) fas: beckerde irc: dbecker regards Domingo Becker (es)

On Mon, Dec 29, 2008 at 06:27:42PM +1000, Noriko Mizumoto wrote: I saw this request in my IRC buffer, happy to oblige. I promoted a bunch of the current L10n steering committee members to Administrator status, you can add anyone I missed and promote people to Sponsor with ease. - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41

Noriko Mizumoto pisze: Piotr Drąg, irc:Raven46 (Polish) piotrdrag(a)gmail.com fas: raven -- Piotr Drąg http://raven.pmail.pl

Em Ter, 2008-12-23 às 17:15 +1000, Noriko Mizumoto escreveu: I just created a new page [1] for this list, since it will get bigger. I also changed the title because I was not sure about the term "administrators", since FAS distinguish sponsors from administrators. Noriko, If you agree with these changes we can use this new page from now on. You can add some information there if necessary. I think we should keep it as simple as possible because it can be hard to maintain. I am just waiting for someone to upgrade Domingo and Piotr in order to add them to the list, because I'm not an administrator at FAS. [1] https://fedoraproject.org/wiki/L10N/GroupSponsors Regards, Igor Pires Soares

2008/12/23 Noriko Mizumoto <noriko(a)redhat.com&gt;: +1 * Yuan Yijun, FAS: bbbush, IRC: hers, Language Team: Simplified Chinese. Some new translators happened to pop up in #fedora-cn recently. If I could sponsor them into l10n commit group that will be the best. -- bbbush ^_^

Karsten Wade wrote: Most other mails on the same thread suggest, "one sponsor from each team (e.g. coordinator)". Although this sounds like an easier method, imho it is not scalable given the current size of the FLP. With >~80 sponsors for the cvsl10n group, it would become a necessity, putting in place guidelines for sponsorship and ensuring that they are adhered to. Especially, since the following needs to be tracked: 1. Coordinators/Sponsors for a team are active and respond 2. Coordinators/Sponsors for a team do not sponsor members from other teams without authorization Additionally, in case of disputes or dormant teams, some guidelines have to be in place to over-ride the language team coordinator's authority (if we are assuming that only a coordinator or authorized member of a language team can sponsor new entrants to that team). Secondly, it does not eradicate the current problem of: 1. Determining the identity/affiliations of the new entrant (unless the entrant chooses to disclose). Reason being: The "Self:Introduction" mail is listed in the TQSG, but is not a hindrance to reach the queue. Unless the new entrant is "forcibly" made to mention the language team she/he would like to join, they can be waiting in the queue for eternity (or sponsored by someone clearing the queue). Reiterating from an earlier suggestion about this[1], imho the introduction of an automatic additional step - "approval from the language coordinator" somewhere on the sponsorship page would help map the new entrant to a language and ensure that the coordinator can approve/disapprove of her/his membership either directly or indirectly. 'l10n' works, however we need to make sure that all references are very carefully replaced. :-) hth Thanks Runa [1] https://www.redhat.com/archives/fedora-trans-list/2008-November/msg00031.... -- blog: http://runab.livejournal.com irc: mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix

Igor Pires Soares wrote: [...] Language groups sounds a viable option, however I am afraid that it might lead to unrelated segregation amongst groups as a long-term side effect. Perhaps the FLSCo members can be considered as a neutral level of sponsors, who can take decisions about sponsoring members for: 1. new teams without coordinators 2. old teams without designated coordinators (i just spotted a few on translate.fp.o) 3. teams with disputed/MIA leadership +1 Also, I already saw a mail[1] about the sequence of to-do's listed in the TQSG listed as: 1. Approval into cvsl10n 2. Self-introduction mail to the list. We might need to change that. Secondly, I am not sure if we have any automated method currently for: 1. notifying people waiting in the cvsl10n queue to send self-introduction mails, 2. notifying the team coordinators (who are not yet listed as sponsors) about people from their language waiting to be sponsored As far as my understanding, yes. However, imho it might not be a bad idea to explore the option of a possible patch to the system that might help us plug this bit, which is a nagging worry for FLP. Thoughts? regards Runa [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00093.... -- blog: http://runab.livejournal.com irc: mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix

On Fri, Dec 26, 2008 at 8:56 AM, Runa Bhattacharjee <runab(a)redhat.com&gt; wrote: There is no option currently in FAS for language groups, only for choosing the country the user lives in. Good point, although I believe anyone can be considered a neutral sponsor in this case. Here's what I do: "If person has sent self-introduction and language team does not have a coordinator, then sponsor him and urge to step up as a coordinator". Upon cleanup, I usually send a standard email to un-introduced folks urging them to follow the instructions and get-going asap with translations. There is no automated way. Folks with programming skills, however, could write a plugin for FAS that does exactly that. -δ PS: I've been a bit inactive lately due to heavy work. More on this on a separate email though. =) -- Dimitris Glezos Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) --