Open Stack

Based on the discussion, sounds like it should become a chapter in the
larger admin guide.

Anne

On Fri, May 22, 2015 at 7:29 PM, Bernd Bausch <berndbausch at gmail.com> wrote:

> The term "virtual machine images" has the advantage of being quite
> specific,
> and, as Adrien points out, the disadvantage of simply being wrong. The term
> "cloud images guide" sounds a bit vague and unspecific. "cloud ready images
> guide" is better.
> Does the word "guide" has to come at the end, or do we need this word at
> all?
>
> Here is my mouthful: "Creating and managing images for your OpenStack
> cloud"
>
>
> ----------------------------------------------------------------------------
> ------------
>
> From: Lana Brindley [mailto:openstack at lanabrindley.com]
> Sent: Saturday, May 23, 2015 3:51 AM
> To: openstack-docs
> Subject: [OpenStack-docs] Renaming Virtual Machine Image Guide
>
> Hi team,
>
> Adrien has approached me at Summit to discuss renaming the Virtual Machine
> Image Guide to something more appropriate, probably something like the
> Cloud
> Image Guide. He originally proposed this
> in https://bugs.launchpad.net/openstack-manuals/+bug/1438597 and I said I
> wanted to have more discussion about it before we made a decision.
>
> Can you please reply to this email and let me know if you approve of
> changing the name of the guide and, if so, what you think it should be
> called? The main argument I can see is that the word ‘cloud’ is a broader
> definition than the word ‘virtual machine’ and we need to be a little more
> generic.
>
> Looking forward to hearing your thoughts.
>
> Lana
>
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
>
>
>
>
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
annegentle at justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150523/03c6dc98/attachment.html>