Re: Plone 4.1.4/4.2b2

Hi,

I propose to migrate both plone.app.locales and PloneTranslations to github
collective.
So you will have a package plone.app.locales on github collective and the
actual PloneTranslations/trunk will be in
plone.app.locales/plone/app/locales/locales. No more svn external. The
PloneTranslations/trunk/i18n/kupu will be moved to Products.kupu/i18n on
collective svn where it belongs.
But I think we can't easily keep the history of both package. I suggest to
import PloneTranslations as plone.app.locales on github so we have the
history of translations, then import the structure of plone.app.locales
package. We will lose the previous tags of plone.app.locales. svn tags of
plone.app.locales have svn externals set to a specific collective svn
revision, it will be useless to git anyway.

There is some advantage to github.
You can fix a typo online.
A lambda user can propose a better translation just by adding a comment to
a commit for example,

Vincent

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

_______________________________________________
Plone-i18n mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-i18n