[wp-polyglots] translate.wordpress.org

[Mattias Tengblad]

Hi,

I agree with you Stas.

I also think that we should leave svn repo's as the final production 
location with manual commit by team leaders.

IMO, GlotPress got really good potential but is not yet quite mature as 
a main production location (I rather use poedit<->SVN for now).

*Mvh*
/Mattias Tengblad/
Webbplats: eyesx.com <http://eyesx.com>
E-post/Live Messenger: mst at eyesx.com <mailto:mst at eyesx.com>


Stas Sușcov skrev 2010-02-18 18:52:
> Hi,
> nice work Nikolay, congrats.
>
> Don't get me wrong, but before getting our official local page on
> wordpress.org, we were using a tool like that (called narro, but nvm).
> The problem with web based tools is that they really give you space to
> get more contributions from users, but they still lack some under the
> hood control. After finishing the translations, we were still obliged to
> check the files manually (poedit) to be sure that .mo's were compiled
> correctly and the svn was the only real helpful backup tool (ability to
> get back to another revision and checkout cause of occured errors).
>
> Now it's cool to have it all centralised, but all the issues and
> questions in case of errors, will be addressed you guys (wp.org),
> wouldn't that give you headaches to respond to everyone and fix if
> something goes wrong?
>
> I would leave svn repo's as the final product location with manual
> commit by team drivers.
>
> Also I would like to hear other opinions on that count.
>
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100219/15c4bac6/attachment-0001.htm>