<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 6, 2012, at 11:50 AM, Doug Hellmann <<a href="mailto:doug.hellmann@gmail.com">doug.hellmann@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 5, 2012, at 3:20 PM, Anne Gentle wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hey all, sorry for top posting but I'm not sure how to insert comments without sounding weird. :) <div><br></div><div>I'm completely fine with starting it in DocBook, (I <3 markup, hee hee) but I had two concerns really, one about the markup authors want, and another about the license for the Operations manual chapters. <div>
<br></div><div>I've been talking to Debra at Pearson, on the To: line (Hi Debra!) and we are looking for authors for some of the operations chapters to be part of a larger book about running and deploying OpenStack. So I would love for you to start as author but want to be sure it's okay that the license is such that we're sharing those chapters with Pearson for a larger book. The outline is <a href="http://etherpad.openstack.org/EssexOperationsGuide" target="_blank">http://etherpad.openstack.org/EssexOperationsGuide</a> for the operations part, and Doug Hellman and I have worked on an outline for the "Developing" part at <a href="http://etherpad.openstack.org/PythonDevBookOutline">http://etherpad.openstack.org/PythonDevBookOutline</a>. The two together comprise a book proposal for Pearson. </div>
<div><br></div><div>Debra, if you have any pointers for the "source" files that would help us decide amongst DocBook or markdown or asciidoc, let us know. </div></div></blockquote><div><br></div><div>I have a bit of experience with DocBook, and IIRC it was an option with Pearson. My book was done with Sphinx and LaTeX with only moderate pain during the compositing phase.</div><br><blockquote type="cite"><div><br></div><div>I'm trying to be transparent about the re-uses that operations manual can be used for and make sure we're all good with it. I know I am - sharing content with a 3rd party publisher sounds like the best of two worlds to me. But I welcome discussion - thanks Jon for bringing it to the mailing list, sorry I didn't do so sooner. Please discuss. :) </div>
<div><br></div><div>I think one good path is:</div><div>1. Un-abandon review 10487. </div><div>2. In the book file make sure CC licensing is set. </div><div>3. Start writing based on the outline.</div><div>4. Rock out.</div>
<div>5. Do maintenance going forward in a common authoring environment. </div></blockquote><div><br></div><div>Anything that makes merging and collaborating easy works for me. What tools are the group used to working with?</div><div><br></div><div>Doug</div><br></div></div></blockquote><div><br></div><div>The docs maintained by the doc team are pretty much all in docbook format, with maven scripts used to generate the output. I believe Anne has been using pandoc to convert from other formats when people contribute in other formats, but that hasn't happened too much. The dev teams use Sphinx.</div><div><br></div><div>At this point, I have no problem with DocBook, as I've been working with it for a while now, and Oxygen makes it much easier to edit DocBook files since they give us free licenses (see <a href="http://wiki.openstack.org/Documentation/HowTo">http://wiki.openstack.org/Documentation/HowTo</a>). I do think it takes a bit of time to ramp up with the tools.</div><div><br></div><div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div><div><br></div></div></span><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"></div></div></div></body></html>