Re: Missing language teams from Mango

[Runa Bhattacharjee <runabh gmail com>]

Olav Vitters wrote:
> On Tue, Jul 08, 2008 at 11:12:57AM +0530, Runa Bhattacharjee wrote:
>   
> > Hi,
> >
> > Christian Rose wrote:
> >     
> > > On 7/4/08, Ankit Patel <ankit644 yahoo com> wrote:
> > >   
> > >       
> > > > Runa Bhattacharjee wrote:
> > > > Ankit Patel wrote:
> > > >
> > > >
> > > >     
> > > >         
> > [snip]
> >     
> > > I added http://bugzilla.gnome.org/show_bug.cgi?id=541665 as a request
> > > for solving this catch-22 in Mango. Needs some Mango love; I hope that
> > > Olav will have time to look at it...
> > >       
> > Thanks Christian for filing the bug. The conversation in there however, 
> > still does not clarify what are the steps a team has to take to ensure that 
> > they eventually get commit rights. There is no mention of documentation (or 
> > any impending ones) about the LDAP account process, and whether existing 
> >     
>
> Mango doesn't do that yet. So without being able to do stuff, it is
> pointless to have documentation.
>
>   
> > teams listed in Mango would be reviewed to ensure that they conform to the 
> > requirements. Often, teams go through changes in leadership and may have to 
> >     
>
> What requirements?
>
>   
> > go through the entire process, irrespective of the maturity/trust of the 
> > existing account holders from the language team. How would such a situation 
> > be handled?
> >     
>
> Mango doesn't handle that at the moment.
>
>   
> > The solution plan as described in:
> >
> > http://bugzilla.gnome.org/show_bug.cgi?id=541505
> >
> > does not have any time line about the change in process and does not talk 
> > about how the *existing* languages  would be re-instated into Mango 
> > (assuming, the current mandatory rule of 
> >     
>
> I don't get 'reinstated'. Nobody's account has been revoked.
>   
The discussion here is not about "account revocation". But about  
languages missing from the Mango list. And that definitely is a bug. 
Either on Mango or due to a flaw in the GTP account system or due to 
some missing bits on the part of the language team. And that bit needs 
to be documented. There are some specific scenarios here which would 
require separate handlers. :

1. New Team just starting off, without any kind of accounts (coordinator 
or team member) - Where is the account request for the first account to 
be sent and what are the checklist items that need to be completed to 
get the account? e.g. Pashto

2. Existing Team with translations, without co-ordinator account due to 
a change in co-ordinator - Where is the account request for the first 
account to be sent and what are the checklist items that need to be 
completed to get the account? e.g. Marathi

3. Existing Team with translations, with co-ordinator account, not 
listed in Mango - Where does a team member send the request for an 
account? e.g. Gujarati, Bengali-India


None of these above cases can be handled by the only documentation 
available to the GTP volunteers at present, which are:

http://live.gnome.org/TranslationProject/RequestingAnAccount
http://live.gnome.org/TranslationProject/AccountFAQ


Languages teams are right now hitting a blind alley at the New Accounts 
interface on Mango if any of the above 3 conditions exist.
>   
> > "team-gets-listed-if-svn-account-exists-for-coordinators"  is still in 
> >     
>
> Timeline? I don't get paid to work on GNOME. So I can't give a timeline.
> Especially as I still have to learn Django, LDAP schema stuff, etc.
>
> If more people help, it will go faster. Of course, ideally I'd like it
> to be finished in a few months. But that is not a promise plus it might
> be fixed faster (no idea).
>
>   
> > place). Some of these language teams have been around for nearly 5-6 years, 
> > highly active, have a larger group of volunteers and have also gone through 
> > changes in coordinatorship. Most of the individual language team bugs have 
> > been closed with an outright NOTABUG resolution, without any clarification 
> > of what we are doing wrong and/or what is to be done next.
> >     
>
> I think I explained everything. The Mango component is for bugs in
> Mango. Not about getting people an account.
>
> If you want to help, ask me what is needed and submit patches.
> Discussion won't speed anything up.
>
> If someone is at GUADEC, just talk to me. That'll be much easier and
> faster.
>
>
> In short: Mango is a tool to make the accounts gnome org queue handling
> automated. If Mango doesn't do something, there always is the email
> address (which currently is even handled every weekend or so).
>
> Currently people will be pretty much lost if they're forgot their Mango
> password etc, I have ideas about solving that. But don't have time, I
> work on more stuff on GNOME than Mango, etc.
>   
Irrespective of what happens beyond the abstracted layer for the 
accounts queue handling/admininstration, the translation teams can only 
meet specific instructions as per whatever is the current process as 
determined and documented by the GTP to get an account.

regards
Runa


--
blog: http://runab.livejournal.com
irc: mishti or runa_b on Freenode