<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Pete,</div>
<div><br>
</div>
<div>The main problem with that is publishing docs to docs.oo which would then confuse the reader even more then they are already confused by reading our docs ;)</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Pete Birley <<a href="mailto:pete@port.direct">pete@port.direct</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, November 21, 2016 at 5:11 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible<br>
</div>
<div><br>
</div>
<span style="mso-bookmark:_MailOriginalBody">
<div>
<div>
<div dir="ltr">I think Jeffrey's raised a good point here. Though I agree we should keep the development side under a single umbrella/namespace, to better co-ordinate our efforts, I think it makes more sense to move the end-user documentation and to the repo
that it's associated with. I feel this is the right approach as it makes it much less likely for users to confuse/mix documents. With this in mind would it not make sense to spit out the docs as follows?
<div>
<ul>
<li>Kolla: images (building/specs), contributing, development</li><li>Kolla-ansible: deployment via ansible, ansible specific specs</li><li>Kolla-kubernetes: deployment via k8s, k8s specific specs</li></ul>
<div>- Pete</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 21, 2016 at 10:13 AM, Jeffrey Zhang <span dir="ltr">
<<a href="mailto:zhang.lei.fly@gmail.com" target="_blank">zhang.lei.fly@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Then what's the case of kolla-kubernetes?<br>
<div class="HOEnZb">
<div class="h5"><br>
On Mon, Nov 21, 2016 at 5:54 PM, Paul Bourke <<a href="mailto:paul.bourke@oracle.com">paul.bourke@oracle.com</a>> wrote:<br>
> Propose all docs stay under the kolla namespace<br>
> (<a href="http://docs.openstack.org/developer/kolla" rel="noreferrer" target="_blank">http://docs.openstack.org/<wbr>developer/kolla</a>).<br>
><br>
> Steve mentioned that we should try to keep all components (e.g. mailing list<br>
> tags) under the same umbrella which I agree with.<br>
><br>
> On 21/11/16 08:05, Jeffrey Zhang wrote:<br>
>><br>
>> After the split, we have two projects and two develop docs[0][1].<br>
>> These two sites have lots of duplicated lines.<br>
>><br>
>> So will we split the doc site?<br>
>> if so, we need to remove the duplicated doc in the repos.<br>
>> if not, we need to remove one site's doc.<br>
>><br>
>> [0] <a href="http://docs.openstack.org/developer/kolla" rel="noreferrer" target="_blank">
http://docs.openstack.org/<wbr>developer/kolla</a><br>
>> [1] <a href="http://docs.openstack.org/developer/kolla-ansible/" rel="noreferrer" target="_blank">
http://docs.openstack.org/<wbr>developer/kolla-ansible/</a><br>
>><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
<br>
</div>
</div>
<span class="im HOEnZb">--<br>
Regards,<br>
Jeffrey Zhang<br>
Blog: <a href="http://xcodest.me" rel="noreferrer" target="_blank">http://xcodest.me</a><br>
<br>
</span>
<div class="HOEnZb">
<div class="h5">______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<table border="0" cellpadding="0" width="450" style="color:rgb(0,0,0);font-family:'Times New Roman';font-size:medium;table-layout:fixed">
<tbody>
<tr>
<td align="left" valign="top" width="90">
<p style="margin-right:10px;font-family:Helvetica,Arial,sans-serif;font-size:10px;line-height:12px;margin-bottom:10px">
<a href="https://port.direct" style="text-decoration:none" target="_blank"><img src="https://raw.githubusercontent.com/encharm/Font-Awesome-SVG-PNG/master/black/png/256/anchor.png" alt="Port.direct" border="0" height="80" width="80"></a></p>
</td>
<td align="left" nowrap="" width="370">
<p style="font-family:Helvetica,Arial,sans-serif;font-size:10px;line-height:12px;color:rgb(33,33,33);margin-bottom:10px">
<span style="font-weight:bold;display:inline">Pete Birley</span> <span style="display:inline">/</span> <span style="display:inline">Director</span> <span style="display:inline"><br>
</span><a href="mailto:pete@port.direct" style="color:rgb(71,124,204);text-decoration:none;display:inline" target="_blank">pete@port.direct</a><span style="display:inline"> / </span><span style="display:inline">+447446862551</span></p>
<p style="font-family:Helvetica,Arial,sans-serif;font-size:10px;line-height:12px;margin-bottom:10px">
<span style="font-weight:bold;color:rgb(33,33,33);display:inline"><strong>PORT.</strong>DIRECT</span> <span style="display:inline"><br>
</span><span></span><span style="color:rgb(33,33,33);display:inline">United Kingdom</span> <span></span><span style="display:inline"><br>
</span><a href="https://port.direct" style="color:rgb(71,124,204);text-decoration:none;display:inline" target="_blank">https://port.direct</a></p>
<p style="font-size:0px;line-height:0;font-family:Helvetica,Arial,sans-serif"></p>
</td>
</tr>
<tr>
<td colspan="2"></td>
</tr>
<tr>
<td colspan="2"></td>
</tr>
<tr>
<td colspan="2">
<p style="font-family:Helvetica,Arial,sans-serif;color:rgb(33,33,33);font-size:9px;line-height:12px">
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information
herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Port.direct is not responsible
for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent
those of the company.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span></span>
</body>
</html>