On Tue, Feb 4, 2014 at 1:44 AM, Vratislav Podzimek <vpodzime@redhat.com> wrote:

...

>
> 3. Once the content is in a shared space, we can do some peer review.
> Your content looks great, and we have some very experienced technical
> writers that can help improve presentation and structure.

What can I do for this? The guide is at:
https://git.fedorahosted.org/cgit/docs/anaconda-addon-development-guide.git/

One more thing I don't understand -- how will it happen that the guide
will appear in the official documentation?

Thanks,

--
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

Now that the repo is in place, we should probably create a Transifex project for it and push POTs for translation. Much of the tx-client usage is covered in the Documentation Guide, and the `create-tx-configuration` package is a big help when creating .tx/config . Ping if you need help, or would like me to save you some time and set it up for you.

The publishing process is covered in the Documentation Guide, and requires Publican 2.x as available from Fedora 18. I still have a box with F18 for this purpose, and can help if needed.

I would like to work on the formatting a little, and jhradilek expressed an interest as well ( at least to check my work :) ). Your call on if you want to publish before or after.

-- Pete