- From: Matt Ray <
>
- To:
- Subject: [chef] Re: Re: Re: Translations for the Chef training material
- Date: Tue, 28 Feb 2012 10:08:53 -0600
- Authentication-results: mr.google.com; spf=pass (google.com: domain of
designates 10.50.217.132 as permitted sender)
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.
| (512) 731-2218
Twitter, IRC, GitHub: mattray
2012/2/28 Juan Jesús Ojeda Croissier
<
>:
>
On Fri, Feb 24, 2012 at 7:33 PM, Jesse Robbins
>
<
>
>
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
>
>
I'm not sure the better way, both was has their pros and cons.
>
>
--
>
Juanje
Archive powered by MHonArc 2.6.16.