# Translations for the Chef training material

**URL:** <https://discourse.chef.io/t/translations-for-the-chef-training-material/2498>\
**Category:** Chef Infra (archive)\
**Created:** [February 24, 2012, 11:14am UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498 "2012-02-24T11:14:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Juanje\_Ojeda\_Croissi](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/juanje_ojeda_croissi/32/471_2.png) [@Juanje\_Ojeda\_Croissi](https://discourse.chef.io/u/Juanje_Ojeda_Croissi)\
**Post date:** [February 24, 2012, 11:14am UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/1 "2012-02-24T11:14:45Z")

</div>

Hi 🙂

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

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 🙂

–  
Juanje

---

<div class="post-metadata">

**Author:** ![Jesse\_Robbins](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jesse_robbins/32/660_2.png) [@Jesse\_Robbins](https://discourse.chef.io/u/Jesse_Robbins)\
**Post date:** [February 24, 2012, 7:33pm UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/2 "2012-02-24T19:33:39Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Juanje\_Ojeda\_Croissi](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/juanje_ojeda_croissi/32/471_2.png) [@Juanje\_Ojeda\_Croissi](https://discourse.chef.io/u/Juanje_Ojeda_Croissi)\
**Post date:** [February 28, 2012, 4:02pm UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/3 "2012-02-28T16:02:51Z")

</div>

On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins [jesse@opscode.com](mailto: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!

🙂

> > 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:

> **[GitHub - progit/progit: Pro Git Book Content, 1st Edition - This content is...](https://github.com/progit/progit)**
>
> Pro Git Book Content, 1st Edition - This content is deprecated. See 2nd edition at \[progit2\](https://github.com/progit/progit2) - GitHub - progit/progit: Pro Git Book Content, 1st Edition - This co...

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

--  
Juanje

---

<div class="post-metadata">

**Author:** ![Matt\_Ray\_OPSCODE](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/matt_ray_opscode/32/459_2.png) [@Matt\_Ray\_OPSCODE](https://discourse.chef.io/u/Matt_Ray_OPSCODE)\
**Post date:** [February 28, 2012, 4:08pm UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/4 "2012-02-28T16:08:53Z")

</div>

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](mailto:matt@opscode.com) | (512) 731-2218  
Twitter, IRC, GitHub: mattray

2012/2/28 Juan Jesús Ojeda Croissier [juanje.ojeda@gmail.com](mailto:juanje.ojeda@gmail.com):

> On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins [jesse@opscode.com](mailto: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!
> 
> 🙂
> 
> > > 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](https://github.com/progit/progit)
> 
> I'm not sure the better way, both was has their pros and cons.
> 
> --  
> Juanje

---

<div class="post-metadata">

**Author:** ![Juanje\_Ojeda\_Croissi](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/juanje_ojeda_croissi/32/471_2.png) [@Juanje\_Ojeda\_Croissi](https://discourse.chef.io/u/Juanje_Ojeda_Croissi)\
**Post date:** [February 28, 2012, 4:19pm UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/5 "2012-02-28T16:19:37Z")

</div>

You're right. Totally agree 🙂

On Tue, Feb 28, 2012 at 4:08 PM, Matt Ray [matt@opscode.com](mailto: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](mailto:matt@opscode.com) | (512) 731-2218  
> Twitter, IRC, GitHub: mattray
> 
> 2012/2/28 Juan Jesús Ojeda Croissier [juanje.ojeda@gmail.com](mailto:juanje.ojeda@gmail.com):
> 
> > On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins [jesse@opscode.com](mailto: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!
> > 
> > 🙂
> > 
> > > > 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](https://github.com/progit/progit)
> > 
> > I'm not sure the better way, both was has their pros and cons.
> > 
> > --  
> > Juanje

--  
Juanje

---

<div class="post-metadata">

**Author:** ![Juanje\_Ojeda\_Croissi](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/juanje_ojeda_croissi/32/471_2.png) [@Juanje\_Ojeda\_Croissi](https://discourse.chef.io/u/Juanje_Ojeda_Croissi)\
**Post date:** [March 7, 2012, 5:24pm UTC](https://discourse.chef.io/t/translations-for-the-chef-training-material/2498/6 "2012-03-07T17:24:14Z")

</div>

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 🙂  
El 28/02/2012 16:19, "Juan Jesús Ojeda Croissier" [juanje.ojeda@gmail.com](mailto:juanje.ojeda@gmail.com)  
escribió:

> You're right. Totally agree 🙂
> 
> On Tue, Feb 28, 2012 at 4:08 PM, Matt Ray [matt@opscode.com](mailto: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](mailto:matt@opscode.com) | (512) 731-2218  
> > Twitter, IRC, GitHub: mattray
> > 
> > 2012/2/28 Juan Jesús Ojeda Croissier [juanje.ojeda@gmail.com](mailto:juanje.ojeda@gmail.com):
> > 
> > > On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins [jesse@opscode.com](mailto: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!
> > > 
> > > 🙂
> > > 
> > > > > 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](https://github.com/progit/progit)
> > > 
> > > I'm not sure the better way, both was has their pros and cons.
> > > 
> > > --  
> > > Juanje
> 
> --  
> Juanje