<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 26, 2013 at 3:39 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 11/26/2013 09:07 PM, Anne Gentle wrote:<br>
><br>
><br>
><br>
> On Tue, Nov 26, 2013 at 1:57 PM, Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:aj@suse.com">aj@suse.com</a>>> wrote:<br>
><br>
> On 11/26/2013 08:31 PM, Andreas Jaeger wrote:<br>
> > I read that you discussed at the summit a docutils repo and I'd<br>
> like to<br>
> > work on implementing all the bits for it - if nobody else has<br>
> > volunteered yet for it.<br>
> ><br>
> > Did you discuss any further things on how to use it? Before I write up<br>
> > my own ideas, I'd like to read what you already discussed.<br>
> ><br>
> > Btw. how can I request a new git repo? I would start this while we<br>
> still<br>
> > discuss the specifics...<br>
><br>
><br>
> Referenced in:<br>
> <a href="https://etherpad.openstack.org/p/icehouse-doc-translation" target="_blank">https://etherpad.openstack.org/p/icehouse-doc-translation</a><br>
> starting line 67<br>
><br>
><br>
> Yes, there it is.<br>
><br>
> I think that you just request the repo from the Infrastructure team.<br>
> There's still some research in the options listed there, and some of<br>
> which I'm not informed enough to be opinionated about. The main ideas<br>
> and goals are about translation, autodoc generation, and validation.<br>
<br>
</div>I've asked #openstack-infra for help and got pointers on how to request<br>
a new repo - and since fungi was confused by "docutils" I took the<br>
proposal from the etherpad and proposed "doctools". The patch is at:<br>
<a href="https://review.openstack.org/#/c/58623/" target="_blank">https://review.openstack.org/#/c/58623/</a><br>
<br>
I created an initial repository consisting of all the content from the<br>
tools subdirectory of openstack-manuals and pushed it to<br>
<a href="https://github.com/ajaeger/doctools" target="_blank">https://github.com/ajaeger/doctools</a>. Do you think that's the proper<br>
initial layout and content? Or should I remove some more files?<br>
<br>
<br>
For building documentation (like openstack-manuals) with Jenkins, I see<br>
two options:<br>
Option 1: Have Jenkins checkout the doctools repository every time and<br>
use that for building - similar to the "devstack-checkout"<br>
job<br>
<br>
Option 2: Copy the tools and all support files to each and every<br>
repository. We could automate that.<br>
<br>
I suggest to investigate whether option 1 is feasible and go for that.<br>
It gives us the benefit that any change to doctools will immediately be<br>
reflected in any other repo - and that's a problem as well ;)<br>
<br>
Moving forward, I'd like to have all our repositories (api-site,<br>
compute-api, identity-api, image-api, netconn-api, object-api,<br>
volume-api, operations-guide, openstack-manuals) use proper gates,<br>
thus extend "test.py" so that it can be used in more places.<br>
Right now only operations-guide and openstack-manuals are gated - but<br>
operations-guide uses an old version of the tools.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>One comment about <service>-api repos -- those are going to be deleted in the icehouse release with the content moved to <project>/doc/source repositories. Can you envision gating on those specific directories? </div>
<div><br></div><div>Thanks,</div><div>Anne</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
</div></div></blockquote></div><br></div></div>