[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Notes from the translation BoF at Akademy 2016
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2016-09-28 21:40:10
Message-ID: 1508712.zR0CDEF9Uc () xps
[Download RAW message or body]

El dilluns, 12 de setembre de 2016, a les 20:30:52 CEST, Karl Ove Hufthammer 
va escriure:
> Albert Astals Cid skreiv 08. sep. 2016 00:10:
> >> >BTW, we use the summit workflow (which we are very happy with, and which
> >> >have saved us tons of work). So I guess we don't*really*  need the
> >> >process_orphans scripts for the various branches, only the corresponding
> >> >script for the*summit directory*.
> > 
> > Wouldn't it just be easier for all your translators to work upstream on
> > the
> > summit directory?
> 
> Not for them, but perhaps for me. :)
> (I now use a 458-line bash script + some manual work for all the
> translation management stuff.)
> 
> Are there any problems with giving all the active translators commit
> access? (I seem to remember that originally only the translation
> coordinators could get commit access.)

Anyone that is deemed "responsible enough" can get commit access, the rules 
are losely:
 * We trust he is not going to break stuff (either maliciously or by not 
knowing how to use svn/git)
 * We trust she is not going to disappear tomorrow (not that it matters but 
it's a hassle to grant someone access for then disappear next day).

For people on your team that fit the rules please send them to 
https://community.kde.org/Infrastructure/Get_a_Developer_Account

Cheers,
  Albert

[prev in list] [next in list] [prev in thread] [next in thread]