[Plone-i18n] Plone 4.1.4/4.2b2

[Eric Steele]

Hi all,

I'd like to make releases of 4.1.4 and 4.2b2 on Friday of this week. Could I have a new release of plone.app.locales?

Thanks,

Eric

[Vincent Fretin]

Hi everyone,

You have 2 new messages in plone.app.ldap domain
and 4 new messages in plone domain for Plone 4.2b2

Eric, I did a fix in plone.app.collection.

Argh and I cannot commit on plone.app.locales because the plone svn is now read only.
What do I do?
plone.app.locales uses svn externals to collective. I don't think it's a good idea to move it to github.

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
Plone...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Eric Steele]

Thanks.

I'll check with the AI team to see if we can unlock that. 

plone.app.collection 1.0.2 is released.

Eric

[Vincent Fretin]

Hi,

I couldn't wait, I'm not available today.
So I imported the structure of the plone.app.locales package to svn collective to be able to make the release.
plone.app.locales 4.0.11 released and plone-coredev buildout 4.1 and 4.2 updated.

We can keep the plone.app.locales empty package to svn collective or
in the long-term migrate both plone.app.locales and PloneTranslations to github. The question is github plone or github collective?
What translators think about it?

Vincent

[Mikel Larreategi]

2012/2/10 Vincent Fretin <vincent...@gmail.com>:

> Hi,
>
> I couldn't wait, I'm not available today.
> So I imported the structure of the plone.app.locales package to svn
> collective to be able to make the release.
> plone.app.locales 4.0.11 released and plone-coredev buildout 4.1 and 4.2
> updated.
>
> We can keep the plone.app.locales empty package to svn collective or
> in the long-term migrate both plone.app.locales and PloneTranslations to
> github. The question is github plone or github collective?
> What translators think about it?
>

There two points here:

1. Plone/Collective

Until now translations were not 'Plone core" I continued editing
through collective... I think that the choice should be made by the
Foundation, to consider translations as "plone core" and thus require
a contributor agreement or not.

2. SVN -> Github

Should this package also be migrated to Github? Are the translators
confortable with Github? It's not the same to work on a plone product
and to translate PO files... I don't know... I prefer to use SVN for
this case, but i wouldn't mind moving to github. I'm +-0 on this :)

Mikel

--
Mikel Larreategi
mlarr...@codesyntax.com

CodeSyntax
Azitaingo Industrialdea 3 K
E-20600 Eibar
Tel: (+34) 943 82 17 80

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

[Vincent Fretin]

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

[Giacomo Spettoli]

------------------------------------------------------------------------------
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
Plone...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

+1 for me

I completely agree, I always thought the actual disposition is too much intricate.
Gh can definitely help us in simplifying and in speeding up this part.

Giacomo