Open Stack

Bryan - how about adding a chapter for the book into the source repository, and we pull into it acronyms encountered in the various chapters.
If we keep a "feature" patch item like the rest of Openstack we can cross off the chapters we have completed? Anyone who feels like a few fun cycles can see the state
and contribute? Or a blueprint with a patch item for each chapter?
If you say yes, I will do the above.
Regards
Malini

From: bdpayne at gmail.com [mailto:bdpayne at gmail.com] On Behalf Of Bryan D. Payne
Sent: Monday, August 26, 2013 9:24 AM
To: Sriram Subramanian
Cc: Bhandaru, Malini K; openstack-security at lists.openstack.org
Subject: Re: [Openstack-security] OpenStack Security Guide

Agreed that this would be nice.  Anyone want to pick a term to define a put up a PR for the start of a glossary? :-)

-bryan

On Sun, Aug 25, 2013 at 12:18 AM, Sriram Subramanian <sriram at sriramhere.com<mailto:sriram at sriramhere.com>> wrote:
+1.

Thanks,
-Sriram
________________________________
From: Bhandaru, Malini K
Sent: 8/25/2013 12:01 AM
To: openstack-security at lists.openstack.org<mailto:openstack-security at lists.openstack.org>
Subject: [Openstack-security] OpenStack Security Guide
Hello Bryan and Rob,

I think it is beneficial to add a glossary. There are so many acronyms, nice to have for the new comer instead of having to Google each one.
Often times it is already in the text, but grab and add into a glossary section.

Cheers
Malini

_______________________________________________
Openstack-security mailing list
Openstack-security at lists.openstack.org<mailto:Openstack-security at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-security

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-security/attachments/20130826/9626a003/attachment.html>