Puppet users - Aug 2010 - Documentation contribution opportunity - Please help!

Hi all

One of the big pieces of work we undertook earlier in the year was
migrating the wiki from Trac and establishing the Puppet Docs site at:

http://docs.puppetlabs.com

During this process we began doing a programmatic conversion of the
Restructured Text output from the automatically generated documentation
to Markdown.    The conversion process is less than perfect and some of
the Markdown generated is not overly elegant - making some of our Docs
pages ugly and hard to read.

As a result we''ve decided to rewrite the internal documentation from
Restructured Text to Markdown (see
http://projects.puppetlabs.com/issues/4509).

This is largely:

1. The types and providers documentation (lib/puppet/types/typename.rb &
lib/puppet/providers/provider...)
2. The functions and metaparameter documentation
(lib/puppet/parser/functions/functioname.rb)
3. The configuration reference (lib/puppet/default.rb)
4. And the report, network and indirection references

Updating this documentation doesn''t require any Ruby knowledge!  All
you
need to be able to do is change the existing format into Markdown (both
are fairly simple markup formats).

So if you''ve ever wanted to contribute to Puppet''s core and
get some
commits on the board then this is the perfect opportunity.

All you need to go is clone the Puppet git repo and follow the
development life cycle documentation -
http://projects.puppetlabs.com/projects/puppet/wiki/Development_Lifecycle -
(or feel free to ask for help on #puppet on IRC or either list).

OR email me or anyone else from the team if you''d like to help.  Even a
small number of commits will assist us in migrating this documentation
and making the experience of using Puppet easier!

Cheers

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 10, 2010, at 10:53 PM, James Turnbull wrote:
> During this process we began doing a programmatic conversion of the
> Restructured Text output from the automatically generated documentation
> to Markdown.    The conversion process is less than perfect and some of
> the Markdown generated is not overly elegant - making some of our Docs
> pages ugly and hard to read.
I’ve noticed a couple of things related to in-line fixed-width text (or whatever
you want to call the expected result of using back ticks in Markdown).

1) It looks like text enclosed `like this` is properly converted to
<code>like this</code> on the back-end, but there’s no styling to
set this text apart. (It should show up in a fixed-width font at the very
least).

2) There are places where back ticks are missing and it causes problems. For
instance, the page on templating suggests this command:

    puppet --configprint templatedir

I assume you’re running things through SmartyPants in addition to Markdown
because the above is converted to:

    puppet –configprint templatedir

which will barf if you paste it into a Terminal and try to run it. :)

I suppose the second problem is exactly the type of thing you’re asking for help
with, and if I get time I’ll try, but the first issue I think needs to be fixed
in the CSS file(s) across the board.

Thanks.

-- 
Rob McBroom
<http://www.skurfer.com/>


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> I’ve noticed a couple of things related to in-line fixed-width text
> (or whatever you want to call the expected result of using back ticks
> in Markdown).
> 
> 1) It looks like text enclosed `like this` is properly converted to
> <code>like this</code> on the back-end, but there’s no styling
to set
> this text apart. (It should show up in a fixed-width font at the very
> least).
Okay - I will fix that one.
> 2) There are places where back ticks are missing and it causes
> problems. For instance, the page on templating suggests this
> command:
> 
> puppet --configprint templatedir
> 
Thanks - fixed that one - any others?
> I suppose the second problem is exactly the type of thing you’re
> asking for help with, and if I get time I’ll try, but the first issue
> I think needs to be fixed in the CSS file(s) across the board.
The second problem was actually in a guide - which aren''t
auto-generated
- but still needs to be fixed.

Thanks

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 11, 2010, at 11:00 AM, James Turnbull wrote:
> Okay - I will fix that one.
Thanks.
>> puppet --configprint templatedir
>> 
> 
> Thanks - fixed that one - any others?
None that I’ve personally run across, but cloning `puppet-docs` and searching
for the regex ''--\w'' shows a few. There are also some
occurrences of ''\`'' which I''ve never seen, but
Markdown seems to convert it to a plain back tick. (Particularly in the
[Configuration guide][1].) I imagine this was done to set that text apart, but
once you''ve added some style to <code> it should stand out (plus
the occurrences of ''--'' aren''t getting protected from
SmartyPants where ''\`'' is used).
> The second problem was actually in a guide - which aren''t
auto-generated
> - but still needs to be fixed.
Like I said, no time at the moment, but if I were to fork that repo, I could
just send a pull request, right?

[1]: http://docs.puppetlabs.com/references/latest/configuration.html

-- 
Rob McBroom
<http://www.skurfer.com/>


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> 
> Like I said, no time at the moment, but if I were to fork that repo, I
could just send a pull request, right?
> 
> [1]: http://docs.puppetlabs.com/references/latest/configuration.html
Correct.

Thanks

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> 1) It looks like text enclosed `like this` is properly converted to
<code>like this</code> on the back-end, but there’s no styling to
set this text apart. (It should show up in a fixed-width font at the very
least).
I''ve updated the style and pushed an update.
> 2) There are places where back ticks are missing and it causes problems.
For instance, the page on templating suggests this command:
> 
>     puppet --configprint templatedir
> 
> I assume you’re running things through SmartyPants in addition to Markdown
because the above is converted to:
I''ve fixed the ones I could find - would welcome having any further
highlighted.

Thanks

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 11, 2010, at 4:48 PM, James Turnbull wrote:
> Rob McBroom wrote:
>> 1) It looks like text enclosed `like this` is properly converted to
<code>like this</code> on the back-end, but there’s no styling to
set this text apart. (It should show up in a fixed-width font at the very
least).
> 
> I''ve updated the style and pushed an update.
Looks good. Will the wiki be getting the same treatment at some point?
>> 2) There are places where back ticks are missing and it causes
problems. For instance, the page on templating suggests this command:
>> 
>>    puppet --configprint templatedir
>> 
>> I assume you’re running things through SmartyPants in addition to
Markdown because the above is converted to:
> 
> I''ve fixed the ones I could find - would welcome having any
further
> highlighted.
Thanks. Looks much better. I''ll clone the repo and fix what I can at
some point.

-- 
Rob McBroom
<http://www.skurfer.com/>

The magnitude of a problem does not affect its ownership.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> On Aug 11, 2010, at 4:48 PM, James Turnbull wrote:
> 
>> Rob McBroom wrote:
>>> 1) It looks like text enclosed `like this` is properly converted to
<code>like this</code> on the back-end, but there’s no styling to
set this text apart. (It should show up in a fixed-width font at the very
least).
>> I''ve updated the style and pushed an update.
> 
> Looks good. Will the wiki be getting the same treatment at some point?
Can you provide an example of that in the wiki so I can have a look?
> 
> Thanks. Looks much better. I''ll clone the repo and fix what I can
at some point.
> 
Thanks!  That''d be awesome.

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 12, 2010, at 3:29 PM, James Turnbull wrote:
>>>> 1) It looks like text enclosed `like this` is properly
converted to <code>like this</code> on the back-end, but there’s no
styling to set this text apart. (It should show up in a fixed-width font at the
very least).
>>> I''ve updated the style and pushed an update.
>> 
>> Looks good. Will the wiki be getting the same treatment at some point?
> 
> Can you provide an example of that in the wiki so I can have a look?
I used back ticks in a number of places in my Augeas examples:

http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Augeas#Simple+Examples

Again, the <code> tags are where they should be, but it shows as normal
text. Thanks.

(I''ll probably be practically rewriting that page. I''m finding
much easier, more reliable ways to use Augeas than what we have traditionally
done.)

-- 
Rob McBroom
<http://www.skurfer.com/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 10, 2010, at 10:53 PM, James Turnbull wrote:
> 1. The types and providers documentation (lib/puppet/types/typename.rb
&
> lib/puppet/providers/provider...)
> 2. The functions and metaparameter documentation
> (lib/puppet/parser/functions/functioname.rb)
> 3. The configuration reference (lib/puppet/default.rb)
> 4. And the report, network and indirection references
> 
> …
> 
> All you need to go is clone the Puppet git repo and follow the
> development life cycle documentation -
> http://projects.puppetlabs.com/projects/puppet/wiki/Development_Lifecycle -
> (or feel free to ask for help on #puppet on IRC or either list).
So I cloned the repo today to see if I could help out and I''m not
finding any of the paths referenced above. You were referring to the main Puppet
source, right? Should I be cloning a specific branch or something? Also, should
I fork it on GitHub and work from that, or just clone the real deal?

Maybe this is all answered on the Wiki, but it seems to be down right now.

-- 
Rob McBroom
<http://www.skurfer.com/>


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Fri, 2010-08-27 at 10:29 -0400, Rob McBroom wrote:
> On Aug 10, 2010, at 10:53 PM, James Turnbull wrote:
> 
> > 1. The types and providers documentation (lib/puppet/types/typename.rb
&
> > lib/puppet/providers/provider...)
> > 2. The functions and metaparameter documentation
> > (lib/puppet/parser/functions/functioname.rb)
> > 3. The configuration reference (lib/puppet/default.rb)
> > 4. And the report, network and indirection references
> > 
> > …
> > 
> > All you need to go is clone the Puppet git repo and follow the
> > development life cycle documentation -
> >
http://projects.puppetlabs.com/projects/puppet/wiki/Development_Lifecycle -
> > (or feel free to ask for help on #puppet on IRC or either list).
> 
> So I cloned the repo today to see if I could help out and I''m not
> finding any of the paths referenced above. You were referring to the
> main Puppet source, right? 
Yes, the documentation is embedded in the source code.
You need to patch this part of the code.
> Should I be cloning a specific branch or something? 
I think you can safely base on the 2.6.x branch (and if I''m wrong it
should be easy to rebase on master).
> Also, should I fork it on GitHub and work from that, or just clone the
> real deal?
The usual workflow is:
* fork on github
* clone your own repository
* create a branch in which you want to work
* do the changes
* commit
* push as a remote branch
* ask for a merge giving your remote branch

-- 
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 27, 2010, at 12:03 PM, Brice Figureau wrote:
> Yes, the documentation is embedded in the source code.
> You need to patch this part of the code.
That''s what I thought, but where are the files James mentions? I
don''t see `lib/puppet/types`, `lib/puppet/providers`, `functioname.rb`,
etc. in master or 2.6.x.

-- 
Rob McBroom
<http://www.skurfer.com/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 27/08/10 19:16, Rob McBroom wrote:
> On Aug 27, 2010, at 12:03 PM, Brice Figureau wrote:
> 
>> Yes, the documentation is embedded in the source code.
>> You need to patch this part of the code.
> 
> That''s what I thought, but where are the files James mentions? I
don''t see `lib/puppet/types`, `lib/puppet/providers`, `functioname.rb`,
etc. in master or 2.6.x.
They''re not real filenames just pointers to where the files are.
That means all files in:
lib/puppet/types/*.rb
lib/puppet/providers/*.rb
lib/puppet/parser/functions/*.rb

-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 27, 2010, at 2:11 PM, Brice Figureau wrote:
> They''re not real filenames just pointers to where the files are.
> That means all files in:
> lib/puppet/types/*.rb
> lib/puppet/providers/*.rb
I don''t think you understand (or I don''t).

    % ls lib/puppet/types/*.rb
    ls: No match.
    % ls lib/puppet/providers/*.rb
    ls: No match.

Those directories aren''t there. And in case you think something is
screwed up on my system, take a look at
http://github.com/reductivelabs/puppet/tree/master/lib/puppet/

There are no directories named `types` or `providers`.

There are no files anywhere in the entire repo named `typename.rb` or
`functioname.rb`.

-- 
Rob McBroom
<http://www.skurfer.com/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

>There are no directories named `types` or `providers`.
>
>There are no files anywhere in the entire repo named 
>`typename.rb` or `functioname.rb`.
>
Perhaps he means types as in these: lib/puppet/type/*.rb? Same goes for
providers.

This email communication and any files transmitted with it may contain
confidential and or proprietary information and is provided for the use of the
intended recipient only.  Any review, retransmission or dissemination of this
information by anyone other than the intended recipient is prohibited.  If you
receive this email in error, please contact the sender and delete this
communication and any copies immediately.  Thank you.
http://www.encana.com


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> On Aug 27, 2010, at 2:11 PM, Brice Figureau wrote:
> 
>> They''re not real filenames just pointers to where the files
are.
>> That means all files in:
>> lib/puppet/types/*.rb
>> lib/puppet/providers/*.rb
That''s my typo - mea culpa:

lib/puppet/type/*.rb
lib/puppet/provider/*.rb
> There are no files anywhere in the entire repo named `typename.rb` or
`functioname.rb`.
Those are examples - the actual files are named after the types and
providers - host.rb, template.rb etc.

Although thanks to some people in the community and a sprint from me
we''ve updated all this code now to Markdown!

Thanks to everyone contributed!

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 27/08/10 20:44, Rob McBroom wrote:
> On Aug 27, 2010, at 2:11 PM, Brice Figureau wrote:
> 
>> They''re not real filenames just pointers to where the files
are.
>> That means all files in:
>> lib/puppet/types/*.rb
>> lib/puppet/providers/*.rb
> 
> I don''t think you understand (or I don''t).
> 
>     % ls lib/puppet/types/*.rb
>     ls: No match.
>     % ls lib/puppet/providers/*.rb
>     ls: No match.
> 
> Those directories aren''t there. And in case you think something is
screwed up on my system, take a look at
http://github.com/reductivelabs/puppet/tree/master/lib/puppet/
> 
> There are no directories named `types` or `providers`.
My bad there are no ''s'', try:

lib/puppet/type/*.rb
lib/puppet/provider/*.rb
> There are no files anywhere in the entire repo named `typename.rb` or
`functioname.rb`.
Yes, you''re supposed to replace typename by a name of a type (ie for
File, see file.rb, etc). Same for functions: functioname.rb would be
include.rb, generate.rb, etc...
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 27, 2010, at 2:53 PM, James Turnbull wrote:
> Rob McBroom wrote:
>> On Aug 27, 2010, at 2:11 PM, Brice Figureau wrote:
>> 
>>> They''re not real filenames just pointers to where the
files are.
>>> That means all files in:
>>> lib/puppet/types/*.rb
>>> lib/puppet/providers/*.rb
> 
> That''s my typo - mea culpa:
> 
> lib/puppet/type/*.rb
> lib/puppet/provider/*.rb
> 
>> There are no files anywhere in the entire repo named `typename.rb` or
`functioname.rb`.
> 
> Those are examples - the actual files are named after the types and
> providers - host.rb, template.rb etc.
OK, I see now. Sorry.
> Although thanks to some people in the community and a sprint from me
> we''ve updated all this code now to Markdown!
Sounds like it''s mostly taken care of. Is there any need for someone to
go through http://github.com/reductivelabs/puppet-docs ?

-- 
Rob McBroom
<http://www.skurfer.com/>


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Rob McBroom wrote:
> 
> Sounds like it''s mostly taken care of. Is there any need for
someone to go through http://github.com/reductivelabs/puppet-docs ?
> 
Totally!  Any improvements or additions to that would be gratefully
received.  We''d also welcome people updating the existing Markdown
references - source/references/* to more viable Markdown (fixing the
tables for example).

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Is there any way to contribute translating the current docs into different
languages?

Thanks.

On Fri, Aug 27, 2010 at 3:16 PM, James Turnbull
<james@puppetlabs.com>wrote:
> Rob McBroom wrote:
> >
> > Sounds like it''s mostly taken care of. Is there any need for
someone to
> go through http://github.com/reductivelabs/puppet-docs ?
> >
>
> Totally!  Any improvements or additions to that would be gratefully
> received.  We''d also welcome people updating the existing Markdown
> references - source/references/* to more viable Markdown (fixing the
> tables for example).
>
> Regards
>
> James Turnbull
>
> --
> Puppet Labs - http://www.puppetlabs.com
> C: 503-734-8571
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
Tony
http://blog.tonyskapunk.net

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Tony G. wrote:
> Is there any way to contribute translating the current docs into
> different languages?
> 
We''d love to see this.  What languages did you have in mind?

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I recall someone started a translation to Chinese, I''ll be happy to
help
with Spanish, and I''ve seen some French speakers into the list that
might be
interested.

Thanks.

On Fri, Aug 27, 2010 at 5:39 PM, James Turnbull
<james@puppetlabs.com>wrote:
> Tony G. wrote:
> > Is there any way to contribute translating the current docs into
> > different languages?
> >
>
> We''d love to see this.  What languages did you have in mind?
>
> Regards
>
> James Turnbull
>
> --
> Puppet Labs - http://www.puppetlabs.com
> C: 503-734-8571
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
Tony
http://blog.tonyskapunk.net

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

If an effort to translate the docs to Spanish get under way, I can help.
-- 
------------------------------

Jesús Couto F.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I can also chip in when this translation project starts.

Best regards,
--
Daniel Bahena
Twitter: @informatux



On Tue, Aug 31, 2010 at 12:47 AM, Jesús Couto <jesus.couto@gmail.com>
wrote:
> If an effort to translate the docs to Spanish get under way, I can help.
> --
> ------------------------------
>
> Jesús Couto F.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Daniel Bahena wrote:
> I can also chip in when this translation project starts.
> 
> Best regards,
So how would people like to contribute documentation in other languages?
 I can create a structure in the current docs directory tree like:

http://github.com/reductivelabs/puppet-docs

source/eng/...
source/esp/...
source/fr/...

And then people can translate the index.markdown and the guides and I
can update.

I can then update the docs site to allow people to select an appropriate
language.

Do people have thoughts on how we might translate the internally-help
and auto-generated reference documentation?

Regards

James Turnbull

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.