<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Sep 1, 2013 at 8:20 PM, Summer Long <span dir="ltr"><<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Of course! I just don't want to step on toes, and I know that others
have already been doing work. And I'm not sure where the book is, in
that 'move stuff' process.</div></blockquote><div><br></div><div>Yay, please do! With git I'm not too worried about toe-stepping but it's good of you to let your intentions be known. </div><div><br></div>
<div>Today's a holiday in the US so I'll be less responsive than usual, but I do want to dig into the Object Storage config tables this week again. But I'm happy to have you organize and do whatever you see fit all along. </div>
<div><br></div><div>Anne</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div class="im">
<br>
<br>
<br>
<div>
<div><font color="#666666">Summer Long<br>
OpenStack Documentation<br>
Engineering Content Services<br>
<br>
Red Hat Asia Pacific<br>
Brisbane, Australia</font><br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a></div>
</div>
<br>
</div><div><div class="h5"><span style>
<div>On 09/02/2013 11:00 AM, Tom Fifield
wrote:<br>
</div>
</span>
<blockquote type="cite">Can
we sign you up? :D
<br>
<br>
<br>
On 02/09/13 10:59, Summer Long wrote:
<br>
<blockquote type="cite">It's just a matter of structure for the
guide. I definitely don't want
<br>
to create a blueprint that won't be used just because there
isn't one!
<br>
<br>
I guess the real question is: if there isn't a blueprint, is
someone
<br>
already tasked with making the Config Reference structure more
coherent
<br>
once all the content has been moved from other guides?
<br>
<br>
thanks, Summer
<br>
<br>
Summer Long
<br>
OpenStack Documentation
<br>
Engineering Content Services
<br>
<br>
Red Hat Asia Pacific
<br>
Brisbane, Australia
<br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a> <a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>
<br>
<br>
On 08/30/2013 11:55 PM, Anne Gentle wrote:
<br>
<blockquote type="cite">
<br>
<br>
<br>
On Thu, Aug 29, 2013 at 6:50 PM, Summer Long
<<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a>
<br>
<a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>> wrote:
<br>
<br>
Thanks Anne, and looping in the mailing list.
<br>
I was just wondering if there is a blueprint for the
Config Ref
<br>
guide from which you and others are working (other than
the
<br>
paragraph in the Restructure doc).
<br>
<br>
If there is not, would you like me to redo the Etherpad to
include
<br>
the HowTos, and then move that into a visible blueprint?
(It
<br>
doesn't really matter what I thought the intent was, just
what is
<br>
happening going forward. :>)
<br>
<br>
<br>
My first instinct is that it's really late in the release for
new
<br>
blueprints, but if it helps you, go ahead. Outlines help me a
BUNCH so
<br>
if that's what you need, do it. You can also just add the
outline to
<br>
the wiki page.
<br>
<br>
I know I told Nermina to update the admin blueprint, but it
already
<br>
existed. And really she's updating an outline.
<br>
<br>
If you want to get started on a blueprint for the next
release, that's
<br>
fine too.
<br>
<br>
Anne
<br>
<br>
<br>
thanks, Summer
<br>
<br>
<br>
<br>
<br>
<br>
Summer Long
<br>
OpenStack Documentation
<br>
Engineering Content Services
<br>
<br>
Red Hat Asia Pacific
<br>
Brisbane, Australia
<br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a> <a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>
<br>
<br>
On 08/30/2013 02:58 AM, Anne Gentle wrote:
<br>
<blockquote type="cite"> The etherpad you reference does
pull in info from the Admin
<br>
Guides. The resulting set must be bigger than you had
imagined.
<br>
:) The original blueprint is
<br>
<a href="https://wiki.openstack.org/wiki/Blueprint-restructure-documentation#OpenStack_Configuration_Reference" target="_blank">https://wiki.openstack.org/wiki/Blueprint-restructure-documentation#OpenStack_Configuration_Reference</a>,<br>
and it has the Admin Guides as a source of info as well.
<br>
<br>
When you say "had thought that the use cases and options
would be
<br>
listed together with the files" what do you mean?
<br>
<br>
Happy to discuss further on the mailing list as well so
others
<br>
can benefit.
<br>
Anne
<br>
<br>
<br>
On Thu, Aug 29, 2013 at 12:57 AM, Summer Long
<<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a>
<br>
<a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>> wrote:
<br>
<br>
Hi there,
<br>
Can you tell me a bit about the state of the Config
Ref
<br>
guide, and its direction? I'd not realised all the
config was
<br>
being moved from individual project guides, and had
been
<br>
under the impression that the Ref would be initially
a
<br>
smaller, based-on-files reference (not including all
the
<br>
project's how-to procedures).
<br>
<br>
Is there now a blueprint from which you're working?
I started
<br>
working with Tom to put together a draft
<br>
(<a href="https://etherpad.openstack.org/Config_Reference-4.0" target="_blank">https://etherpad.openstack.org/Config_Reference-4.0</a>) a
while
<br>
back, had thought that the use cases and options
would be
<br>
listed together with the files....but then content
started
<br>
moving.
<br>
<br>
Just trying to get my head around it all. :)
<br>
<br>
thanks, Summer
<br>
--
<br>
Summer Long
<br>
OpenStack Documentation
<br>
Engineering Content Services
<br>
<br>
Red Hat Asia Pacific
<br>
Brisbane, Australia
<br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a> <a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div>