<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><div id="bloop_customfont" style="margin: 0px;">Hi Doug,</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">first of all sorry for the late response. I am the current PTL of the openstack-chef project and read the spec a while ago, but did not really connect it to our project. To be honest, i am not really sure what we would move and how to do it. Currently we have some wiki pages, but most of them are pretty old and completely outdated since we stopped caring for them after we dropped to only a few contributors and moved our focus to maintaining the project code itself.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Currently we own and maintain 12 service and ops cookbook repositories:</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;"><div id="bloop_customfont">cookbook-openstack-block-storage</div><div id="bloop_customfont">cookbook-openstack-common</div><div id="bloop_customfont">cookbook-openstack-compute</div><div id="bloop_customfont">cookbook-openstack-dashboard</div><div id="bloop_customfont">cookbook-openstack-identity</div><div id="bloop_customfont">cookbook-openstack-image</div><div id="bloop_customfont">cookbook-openstack-integration-test</div><div id="bloop_customfont">cookbook-openstack-network</div><div id="bloop_customfont">cookbook-openstack-ops-database</div><div id="bloop_customfont">cookbook-openstack-ops-messaging</div><div id="bloop_customfont">cookbook-openstack-orchestration</div><div id="bloop_customfont">cookbook-openstack-telemetry</div></div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">one (not very often used) specs repository:</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">openstack-chef-specs</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;"> and one repo to integrate them all:</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">openstack-chef-repo</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">All of these repos have some READMEs that contain some of the documentation needed to use these. The documentation on how to use the openstack-chef project as a combination of all these cookbooks, is located under <a href="https://github.com/openstack/openstack-chef-repo/tree/master/doc">https://github.com/openstack/openstack-chef-repo/tree/master/doc</a> (which might already be close to the right space ?). Looking through the openstack-manuals repo, i did not find any documentation specific for our projects, so i think we do not need to export/import any of it. In my opinion the easiest way to follow the proposed change of us would be to just move the stuff we have under the ‘openstack-chef-repo’ mentioned above and add some more files to follow the ‘minimal layout’. If you agree on this, i can try to push a patch for it next week and add you as a reviewer?</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Cheers,</div><div id="bloop_customfont" style="margin: 0px;">Jan</div></div> <br> <div id="bloop_sign_1498234213956128000" class="bloop_sign"></div> <br><p class="airmail_on">On 23. June 2017 at 16:16:58, Doug Hellmann (<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div></div><div>
<title class=""></title>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 23, 2017, at 8:57 AM, Renat Akhmerov
<<a href="mailto:renat.akhmerov@gmail.com" class="">renat.akhmerov@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div name="messageBodySection" class=""><font color="#333333" class="">I can say for Mistral . We only planned to add Mistral
docs to the central repo but didn’t do it yet. So, as far as I
understand, we don’t need to move anything. We’ll review the spec
and adjust the folder structure according to the
proposed.<br class=""></font></div>
</div>
</div>
</blockquote>
<div><br class=""></div>
<div>Please do review the steps in the spec. Not all of them are
about moving content. There are steps for setting up the new build
job so that the content will be published to the new URLs as
well.</div>
<div><br class=""></div>
<div>Doug</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<div name="messageSignatureSection" class=""><br class="">
Thanks<br class="">
<br class="">
Renat Akhmerov<br class="">
@Nokia</div>
<div name="messageReplySection" class=""><br class="">
23 июня 2017 г., 3:32 +0700, Doug Hellmann <<a href="mailto:doug@doughellmann.com" class="">doug@doughellmann.com</a>>, писал:<br class="">
<blockquote type="cite" class="">Excerpts from Alexandra Settle's
message of 2017-06-08 15:17:34 +0000:<br class="">
<blockquote type="cite" class="">Hi everyone,<br class="">
<br class="">
Doug and I have written up a spec following on from the
conversation [0] that we had regarding the documentation publishing
future.<br class="">
<br class="">
Please take the time out of your day to review the spec as this
affects *everyone*.<br class="">
<br class="">
See: <a href="https://review.openstack.org/#/c/472275/" class="">https://review.openstack.org/#/c/472275/</a><br class="">
<br class="">
I will be PTO from the 9th – 19th of June. If you have any pressing
concerns, please email me and I will get back to you as soon as I
can, or, email Doug Hellmann and hopefully he will be able to
assist you.<br class="">
<br class="">
Thanks,<br class="">
<br class="">
Alex<br class="">
<br class="">
[0] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html" class="">http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html</a><br class="">
</blockquote>
<br class="">
Andreas pointed out that the new documentation job will behave
a<br class="">
little differently from the old setup, and thought I should
mention<br class="">
it so that people aren't surprised.<br class="">
<br class="">
The new job is configured to update the docs for all repos
every<br class="">
time a patch is merged, not just when we tag releases. The
server<br class="">
projects have been working that way, but this is different for
some<br class="">
of the libraries, especially the clients.<br class="">
<br class="">
I will be going back and adding a step to build the docs when
we<br class="">
tag releases after the move actually starts, so that we can
link<br class="">
to docs for specific versions of projects. That change will
be<br class="">
transparent to everyone else, so I have it on the list for
after<br class="">
the migration is under way.<br class="">
<br class="">
Doug<br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage
questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</blockquote>
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage
questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></div></span></blockquote></body></html>