Translations for the Chef training material


#1

Hi :slight_smile:

First of all, thanks to the Opscode guys for the training material is
really awesome :slight_smile:

I was talking with some spaniards interested on Chef and we are
interested on translate this material.
Is there any plan or prefer way to do that?

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

Thanks :slight_smile:


Juanje


#2

On Feb 24, 2012, at 3:14 AM, Juan Jesús Ojeda Croissier wrote:

I was talking with some spaniards interested on Chef and we are
interested on translate this material.

Awesome! err… ¡Maravilloso!

Is there any plan or prefer way to do that?

There is now!

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

It seems like creating per-langauge branches makes sense. How have other projects successfully managed this?

-Jesse


#3

On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins jesse@opscode.com wrote:

On Feb 24, 2012, at 3:14 AM, Juan Jesús Ojeda Croissier wrote:

Is there any plan or prefer way to do that?

There is now!

:slight_smile:

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

It seems like creating per-langauge branches makes sense. How have other projects successfully managed this?

Another way to do it is crating directories per-language at the same
branch as ProGit Book does:

I’m not sure the better way, both was has their pros and cons.


Juanje


#4

It seems that directories per-language is a more straightforward
approach. Multiple branches for languages would drift quickly, by
keeping the languages in subdirectories it would be readily apparent
what’s available and updating images and the like would get picked up
automatically without having to merge.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

2012/2/28 Juan Jesús Ojeda Croissier juanje.ojeda@gmail.com:

On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins jesse@opscode.com wrote:

On Feb 24, 2012, at 3:14 AM, Juan Jesús Ojeda Croissier wrote:

Is there any plan or prefer way to do that?

There is now!

:slight_smile:

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

It seems like creating per-langauge branches makes sense. How have other projects successfully managed this?

Another way to do it is crating directories per-language at the same
branch as ProGit Book does:
https://github.com/progit/progit

I’m not sure the better way, both was has their pros and cons.


Juanje


#5

You’re right. Totally agree :slight_smile:

On Tue, Feb 28, 2012 at 4:08 PM, Matt Ray matt@opscode.com wrote:

It seems that directories per-language is a more straightforward
approach. Multiple branches for languages would drift quickly, by
keeping the languages in subdirectories it would be readily apparent
what’s available and updating images and the like would get picked up
automatically without having to merge.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

2012/2/28 Juan Jesús Ojeda Croissier juanje.ojeda@gmail.com:

On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins jesse@opscode.com wrote:

On Feb 24, 2012, at 3:14 AM, Juan Jesús Ojeda Croissier wrote:

Is there any plan or prefer way to do that?

There is now!

:slight_smile:

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

It seems like creating per-langauge branches makes sense. How have other projects successfully managed this?

Another way to do it is crating directories per-language at the same
branch as ProGit Book does:
https://github.com/progit/progit

I’m not sure the better way, both was has their pros and cons.


Juanje


Juanje


#6

So… Any decision on this matter?

Branches or directories? what do you like more?
Even if you can’t change the repo yet, if the people know the way choosen,
they can be working in their own repos and then merge the changes you will
need to do.

Thanks for the documentation btw. Good stuff :slight_smile:
El 28/02/2012 16:19, “Juan Jesús Ojeda Croissier” juanje.ojeda@gmail.com
escribió:

You’re right. Totally agree :slight_smile:

On Tue, Feb 28, 2012 at 4:08 PM, Matt Ray matt@opscode.com wrote:

It seems that directories per-language is a more straightforward
approach. Multiple branches for languages would drift quickly, by
keeping the languages in subdirectories it would be readily apparent
what’s available and updating images and the like would get picked up
automatically without having to merge.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

2012/2/28 Juan Jesús Ojeda Croissier juanje.ojeda@gmail.com:

On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins jesse@opscode.com
wrote:

On Feb 24, 2012, at 3:14 AM, Juan Jesús Ojeda Croissier wrote:

Is there any plan or prefer way to do that?

There is now!

:slight_smile:

I mean, we just fork the project and do our translations or are the
Opscode guys planning to make a per-language branches or similar
approach so people can contribute on?

It seems like creating per-langauge branches makes sense. How have
other projects successfully managed this?

Another way to do it is crating directories per-language at the same
branch as ProGit Book does:
https://github.com/progit/progit

I’m not sure the better way, both was has their pros and cons.


Juanje


Juanje