Re: [Openstack-doc-core] inviting Ying Chun Guo to join openstack-doc-core

2012-07-28 Thread Ying Chun Guo
Thank you for your invitation, Anne. I'd love to !

 I will try my best to work for openstack documents.
My English may be not as good as Chinese. But I have good experience in
programming.
Besides translation and bug fixing, I also can contribute to doc tools
development.
For example, I plan to work with CI team to automate document publishing
process and translation process
as much as possible.

Regards
Ying Chun Guo (Daisy)

annegen...@justwriteclick.com wrote on 07/28/2012 03:08:38 AM:

> Anne Gentle 
> Sent by: annegen...@justwriteclick.com
>
> 07/28/2012 03:08 AM
>
> To
>
> openstack-doc-core@lists.launchpad.net, Ying Chun Guo/China/IBM@IBMCN,
>
> cc
>
> Subject
>
> inviting Ying Chun Guo to join openstack-doc-core
>
> Hi all -
> I'd like to invite Ying Chun Guo (Daisy) to join our team, she has
> worked both on doc bugs and on a process for translating
> documentation.
>
> Hi Daisy -
> I hope you'll accept the invitation to join openstack-doc-core. Your
> contributions have been extremely helpful.
>
> Thanks,
> Anne
>-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack-doc-core] Client documentation

2012-07-28 Thread Lorin Hochstein
On Jul 27, 2012, at 3:04 PM, Anne Gentle  wrote:

> Hi all -
> The various client projects are getting a consistency boost and I'm
> pretty excited about it. I'd like to know if anyone on the doc-core
> team is interested in working on client docs specifically. Here at
> Rackspace, Karin Levenstein is interested, but working on another
> project for a little while. I know that Dean Troyer was working on the
> consistency pieces for all the clients, and I've reached out to him as
> well.
> 
> So, my question is - on this team does anyone have a special interest
> in improving the client documentation? I'm talking about the
> command-line nova, glance, keystone, and swift commands and their
> parameters. How should we document those? Just on the command line
> itself? Is there a separate guide we should write for each? Would love
> your thoughts and if this is a special interest area for anyone,
> please let us all know your ideas.
> 

Anne:

I have some interest here, although not many cycles to work on it. :(

My own command-line documentation search workflow is:

1. Use the built-in "--help" or "help" command of the tool
2. Look at the man page
3. Go to the internet


If other people work like I do, then that's how I propose we prioritize the doc 
generation. I think we should also have a google'able web page for each tool. I 
suggest generating that content by writing the man page documentation in a 
format that can be easily transformed into HTML (we're already doing this, 
aren't we?) and just post the HTML-ized versions of the client man pages 
somewhere on docs.openstack.org. I don't think we need a separate guide for 
each.

Do we know if the python-openstackclient will be ready in time for the Folsom 
release (I guess this is a good question for Dean)?


Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp