Open Stack

It's just a matter of structure for the guide. I definitely don't want 
to create a blueprint that won't be used just because there isn't one!

I guess the real question is: if there isn't a blueprint, is someone 
already tasked with making the Config Reference structure more coherent 
once all the content has been moved from other guides?

thanks, Summer

Summer Long
OpenStack Documentation
Engineering Content Services

Red Hat Asia Pacific
Brisbane, Australia
slong at redhat.com <mailto:slong at redhat.com>

On 08/30/2013 11:55 PM, Anne Gentle wrote:
>
>
>
> On Thu, Aug 29, 2013 at 6:50 PM, Summer Long <slong at redhat.com 
> <mailto:slong at redhat.com>> wrote:
>
>     Thanks Anne, and looping in the mailing list.
>     I was just wondering if there is a blueprint for the Config Ref
>     guide from which you and others are working (other than the
>     paragraph in the Restructure doc).
>
>     If there is not, would you like me to redo the Etherpad to include
>     the HowTos, and then move that into a visible blueprint? (It
>     doesn't really matter what I thought the intent was, just what is
>     happening going forward. :>)
>
>
> My first instinct is that it's really late in the release for new 
> blueprints, but if it helps you, go ahead. Outlines help me a BUNCH so 
> if that's what you need, do it. You can also just add the outline to 
> the wiki page.
>
> I know I told Nermina to update the admin blueprint, but it already 
> existed. And really she's updating an outline.
>
> If you want to get started on a blueprint for the next release, that's 
> fine too.
>
> Anne
>
>
>     thanks, Summer
>
>
>
>
>
>     Summer Long
>     OpenStack Documentation
>     Engineering Content Services
>
>     Red Hat Asia Pacific
>     Brisbane, Australia
>     slong at redhat.com <mailto:slong at redhat.com>
>
>     On 08/30/2013 02:58 AM, Anne Gentle wrote:
>>     The etherpad you reference does pull in info from the Admin
>>     Guides. The resulting set must be bigger than you had imagined.
>>     :) The original blueprint is
>>     https://wiki.openstack.org/wiki/Blueprint-restructure-documentation#OpenStack_Configuration_Reference,
>>     and it has the Admin Guides as a source of info as well.
>>
>>     When you say "had thought that the use cases and options would be
>>     listed together with the files" what do you mean?
>>
>>     Happy to discuss further on the mailing list as well so others
>>     can benefit.
>>     Anne
>>
>>
>>     On Thu, Aug 29, 2013 at 12:57 AM, Summer Long <slong at redhat.com
>>     <mailto:slong at redhat.com>> wrote:
>>
>>         Hi there,
>>         Can you tell me a bit about the state of the Config Ref
>>         guide, and its direction? I'd not realised all the config was
>>         being moved from individual project guides, and had been
>>         under the impression that the Ref would be initially a
>>         smaller, based-on-files reference (not including all the
>>         project's how-to procedures).
>>
>>         Is there now a blueprint from which you're working? I started
>>         working with Tom to put together a draft
>>         (https://etherpad.openstack.org/Config_Reference-4.0) a while
>>         back, had thought that the use cases and options would be
>>         listed together with the files....but then content started
>>         moving.
>>
>>         Just trying to get my head around it all. :)
>>
>>         thanks, Summer
>>         -- 
>>         Summer Long
>>         OpenStack Documentation
>>         Engineering Content Services
>>
>>         Red Hat Asia Pacific
>>         Brisbane, Australia
>>         slong at redhat.com <mailto:slong at redhat.com>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130902/1a523c38/attachment.html>