[Qgis-psc] svn write access for GUI translators

[Gary Sherman]

On Dec 7, 2010, at 0:11, Tim Sutton <tim at linfiniti.com> wrote:

> Hi
> 
> On Tue, Dec 7, 2010 at 11:02 AM, Otto Dassau <otto.dassau at gmx.de> wrote:
>> Hi,
>> 
>> Werner indirectly asked, if there is a possibility to provide write access
>> to GUI translators or at least GUI translation coordinators. I don't know, if
>> that makes sense, because we now have about ?30? languages and if they all
>> get write access to the qgis sources, it might be a problem - or not?
>> 
>> Is there any solution to this or should we stick to the procedure we use at
>> the moment, that Werner commits the ts files for the translators.
>> 
> 
> The SAC guys don't seem to like giving granular permissions in SVN and
> I don't think it's a good idea to open write commit access so broadly.
> This is another good use case for GIT - Werner maintains his own clone
> and gives the tr() team push access to it, then periodically pushes
> those changes upstream to SVN. I believe it is possible to work like
> this with GIT-SVN - perhaps Gary or Pirmin could confirm.
> 
This is a perfect use case for git. Simple and ready to go right now. 


-Gary
GeoApt LLC
Chair, Quantum GIS PSC
> Alternatively we could do things a different way and extend the scope
> of our suite of django apps to include a ts() upload portal which
> commits ts() changes as they come in from some kind of system account.
> Possibly open to abuse I guess though I think we could create a system
> osgeo user account and just check out the i18n dir, then when a ts
> update is pushed to the portal, our django view just drops it into the
> checkout dir and commits the change.
> 
> Regards
> 
> Tim
> 
>> What do you think?
>> 
>> regards,
>>  Otto
>> 
>> Am Tue, 07 Dec 2010 08:36:31 +0100
>> schrieb Werner Macho <werner.macho at gmail.com>:
>> 
>>> Hi Giovanni!
>>> 
>>> But as I already told you .. manual translations AND QGIS are in ONE
>>> repository .. So I think I will have to talk to Otto if we can seperate
>>> the translation files to give at least the coordinators access to
>>> translation files.. I already thought about creating an own svn repository
>>> just for translations - disadvantage here is that the translators can
>>> destroy the translations if they don't know howto handle it correctly
>> 
>> _______________________________________________
>> Qgis-psc mailing list
>> Qgis-psc at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-psc
>> 
> 
> 
> 
> -- 
> Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
> ==============================================
> Visit http://linfiniti.com to find out about:
>  * QGIS programming services
>  * Mapserver and PostGIS based hosting plans
>  * FOSS Consulting Services
> Skype: timlinux Irc: timlinux on #qgis at freenode.net
> ==============================================
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc