<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;">It’s always hard to chip away from your code, even from documentation =))) But if that is the way most OpenStack projects do and if it would make our install docs more visible — I agree with the idea.</div> <br> <div id="bloop_sign_1471956819531200768" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev</div><div style="font-family:helvetica,arial;font-size:13px">Murano Project Tech Lead</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer at</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div> <br><p class="airmail_on">On 16 août 2016 at 23:19:39, Serg Melikyan (<a href="mailto:smelikyan@mirantis.com">smelikyan@mirantis.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hi folks,
<br>
<br>at this moment all murano documentation (including admin & user
<br>guides) is published only in one place [0], but actually all other
<br>projects store there only developer documentation and guides are
<br>separated. I propose to follow same model with murano documentation.
<br>What do you think?
<br>
<br>References:
<br>[0] docs.openstack.org/developer/murano/
<br>
<br>--
<br>Serg Melikyan, Development Manager at Mirantis, Inc.
<br>http://mirantis.com | smelikyan@mirantis.com
<br>
<br>__________________________________________________________________________
<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>