[Openstack-docs] [Docs] Documentation PTL Candidacy

Emilien Macchi emilien.macchi at enovance.com
Mon Sep 23 14:08:56 UTC 2013


+1

Anne is doing without any doubt an amazing job on OpenStack manuals.

Thank you Anne,

Emilien Macchi
----------------------------------------------------
# OpenStack Engineer
// eNovance Inc.              http://enovance.com
// ? emilien at enovance.com     ? +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris

On 09/22/2013 08:19 PM, Anne Gentle wrote:
> Hi all, 
> I'm writing to declare my intention to run for OpenStack documentation
> program technical lead. [1]
>
> I've been working on OpenStack docs since September 2010, and it has
> been an honor and a privilege to serve in this position informally
> prior to having documentation declared a program. I've been serving as
> the interim PTL as encouraged by my doc peers. 
>
> In Havana we've been hard at work (and continue to do so), refactoring
> the openstack-manuals repo to ensure installation, configuration, and
> administration info is as complete and accurate as we can, including
> the addition of automation tools for gathering configuration options
> into one location.
>
> We've added an End User Guide, an Admin User Guide, and a Cloud
> Administration Guide to document OpenStack as a whole, including all
> the clients and the things you can do with your OpenStack clouds
> through command-line calls. 
>
> We also work on API documentation to bring you a compete reference
> listing of all OpenStack APIs including example requests and responses.
>
> In the last year we've held two successful book sprints in the past
> year resulting in the OpenStack Operations Guide and the OpenStack
> Security Guide. We're actively recruiting writers for a book sprint to
> write an OpenStack Architecture Design Guide. The Operations Guide has
> been translated to Chinese and Japanese.
>
> I believe the documentation PTL role is one of coordination, coaching,
> and providing platforms for documentation. This doesn't happen in
> isolation and requires constant attention and coordination. I do know
> our shortcomings and continue to work through the difficulties we face
> trying to document a fast-moving integrated set of projects. In the
> future I'd like to recruit more upstream OpenStack writers and have
> designated project doc leads. 
>
> I continue to be the top committer to the openstack-manuals repo [2]
> and I am an active reviewer of all docs repos. [3]
>
> I'm proud of the work we've done so far and would be privileged to
> continue this most challenging work. 
> Thanks,
> Anne
>
> 1. Wow, that sounds too formal, but that's what this email is. 
> 2. https://github.com/openstack/openstack-manuals/graphs/contributors
> 3. https://review.openstack.org/#/q/reviewer:anne%2540openstack.org,n,z
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130923/096b2686/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130923/096b2686/attachment.pgp>


More information about the Openstack-docs mailing list