translation process

[mattetti]

Hi,

We are getting a lot of people excited to translate the book in their
own language, while I'm really happy to see the enthusiasm of
everybody, I'm afraid people will might frustrated if we keep on
updating chapters/pages they thought they were done translating.

To avoid such problems, I will sign off on content once a week and
list what can be translated and add a specific CSS class to the
content. To do the tech review, I will ask experts in each field to
help me out.

The goal is to avoid translations out of sync or frustration from
translators. If this process doesn't suit you, please let me know and
suggest something else.

For the moment, only the TOC and the Ruby page are ready for
translation. Don't forget to update your URLs to point to your
language section.

- Matt

[Mathieu FOSSE]

Hi,

I'm happy that Merb Open Source Book was announced !
I'm agree with you to sign off content once a week.
It will be easier for people to read the documentation and for us to
know which page is ready to translate.
Without this process we should check each "commit" in english
directory and apply the translated version of these changes in our
language directory (not really simple).

A little question :
I just receive a pull-request from "startrader" :
http://github.com/startrader/merb-book/commit/1a44a0408b3af51ee98954bcf40b09947dc133c0
It doesn't concern my language (french) but english.
I must re-send it to you, Matt ?

Mathieu

--
Mathieu FOSSE

Yeasty Mobs : http://www.yeastymobs.com
My blog : http://blog.kawooa.org
étrange mélange : http://www.etrangemelange.com

[Mathieu FOSSE]

Oops, you can forgot my question.
I just understand that this "pull-request" was not for my forked
repository (http://github.com/pointcom/merb-book/) but for the main
repository. So, all committers have received this "pull-request".
Sorry.

[Matt Aimonetti]

Startrader should have only send me the PR, next time, ignore it or ask him to only send me the PR.

Thanks,

- Matt

[mattetti]

Wow, as Dale mentioned few days ago, we only started working on this
project few days ago and we already have 10 active translations going
on. I'm personally really impressed and encouraged by the overall
enthusiasm.

Because we have so many people working together on the same project,
we need to get a bit more organized.

First off, I put the book on a temporary site (no caching, so don't
put the site on dig :p) http://book.merbist.com

Secondly, to avoid conflicts and to easily see what changed in the
English content since last time you worked on your translation, we
will maintain language branches in my repo. Language leaders will push
to the language branch directly. Once a week, the leader will rebase
his/her branch to master and merge the language branch in master. (ask
me if you need help or would prefer me to do that)

Finally, we setup some guidelines to write content, please stick to
them: http://groups.google.com/group/merb-book/web/guidelines

Once again, thank you all!

- Matt

[Arthur Zapparoli]

Matt,

I guess English should have his own branch too.

Separating this, should be easier to track changes in the english content.

As a translator, I need to keep an eye on every english change.

Eg: there's a mardown syntax change in
0-front-matter/1-preface.markdown. I already translated this. Today, I
need to look on every master's commits to catch that change. As master
have all other translation commits, this is hard, since a lot of
commits are for other languages.

Resuming:

- branches for each language (including english).
- translators rebase's mattetti/master on his fork.
- language leaders pushes to the language branch directly (in his fork)
- you pull from each leader (on language branch).
- after all, merge each language branche into master.
- master should not be merged into english branch. this way, we'll
have only english-related commits on english branch
- translators will need to keep an eye only in the english branch

Maybe I'm missing something here, but I guess that should work.

What do you guys think?

[]'s
Arthur Zapparoli
http://merb-br.org
http://arthurgeek.net

[Mathieu FOSSE]

Hi,

Must we always wait for "available-for-translation" CSS class before
translate a content ?

Mathieu

[Arthur Zapparoli]

Matt,

I see various changes in "available-for-translations" files.Tiny
little changes, like markdown syntax, typos, better code examples. But
we have to keep our translation uodated with that, right?

Arthur Zapparoli
http://merb-br.org
http://arthurgeek.net

[Matt Aimonetti]

Let's forget about "available-for-translations" CSS class and just choose whenever it's more appropriate to start translating.

I agree with Arthur that we should probably have an English branch and I'll merge all the English changes in the branch. That should make things easier for translators.

I'm fine with pulling from each translator leader instead of them pushing if that's something everybody wants.

Starting tomorrow I'll use the English branch to merge things in, but mind you, I'll need to rebase it against master once a week to get the app code updates.

- Matt

[Markus Prinz]

On 09.12.2008, at 11:26, Matt Aimonetti wrote:
> Starting tomorrow I'll use the English branch to merge things in,
> but mind
> you, I'll need to rebase it against master once a week to get the
> app code
> updates.

May I ask, why the rebasing? Wouldn't merging do it as well?

g, Markus