[Systems] Pootle project reorganization for Etoys
cjlhomeaddress at gmail.com
Tue Jun 22 15:47:51 EDT 2010
Unfortunately, I am really only able to do the front-end Pootle
administrative tasks through the user interface (add languages, change
privs. etc.). And, in fact, I barely have time to do that with my new job
and living situation. I've had to cut way back on my volunteer efforts for
OLPC and Sugar Labs.
I'm very sorry, but I am not sure I can help you with this sort of back-end
work. Sayamindu is really the master of the back-end of Pootle project
set-up. He is stillo around (somewhere), but I iagine he is prtty busy with
his grad school plans.
If he can't help, we will try to identify someone from the SugarLabs
Sysadmin Group that can lend a hand with this major re-organization.
On Tue, Jun 22, 2010 at 11:34 AM, Korakurider <korakurider at gmail.com> wrote:
> Dear Chris,
> I am one of Etoys developers managing translation work.
> We are planning major reorganization of Etoys pootle project
> and would ask pootle admins for help.
> 1. What we would like to change:
> + Only one big PO: etoys.po
> + Pootle project integrated to git
> Developers manually copy updated POs to our master SVN repository.
> + Now we have smaller, splitted POs.
> We expect problem by too big PO will be fixed.
> + We want Pootle project integrated SVN directly.
> You could review structure of our new SVN repo and POTs/POs under:
> 2. Migration story *** This is just our thought ***
> step1: create pootle project "etoys-new" that integrated to SVN for
> test purpose.
> step2.1: Rename Pootle project "etoys" to "etoys-old"; keeping git
> integration as-is.
> (I filled http://bugs.sugarlabs.org/ticket/2037 for this
> step2.2: Rename Pootle project "etoys-new" to "etoys" and open for
> public use.
> 3. Detailed migration plan:
> * commit split po's to our svn (
> * ask localization list to commit any outstanding edits in pootle
> within a week, explain our plan below
> * create a new pootle project "etoys-new" hooking into our svn, test it
> * wait a week for translators to commit
> * then announce on localization list to not edit anything anymore,
> all further changes would be lost
> * pull latest pootle translations from git
> * generate new split po's from those latest
> * update split po's in svn
> * on pootle, move "etoys" (git-based) to "etoys-old", and
> "etoys-new" to "etoys" (svn-based)
> * announce an "all clear" on localization list, ask them to look
> if we indeed did not lose anything
> * from then on, pootle commits would go directly into our svn repo
> 4. Request and Questions
> + We would ask pootle admins for help of changes to pootle.
> + Can Pootle really be integrated to SVN? (At least pootle document says
> + Could you check the migration story/plan above; is this possible
> and reasonable?
> + Do we need to fill ticket for this request other than #2037?
> Your help will be greatly appreciated.
> /Korakurider (behalf of etoys team)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Systems