<div dir="ltr">Anna, hi,<div>Did I get it right? If I do this work somewhere in one of Murano's repositories then I just need to edit <font size="2" face="monospace"><span class="inbox-repo-root inbox-js-repo-root" style="box-sizing:border-box"><span class="inbox-js-path-segment" style="box-sizing:border-box"><span style="box-sizing:border-box">api-site</span></span></span><span class="inbox-separator" style="box-sizing:border-box">/</span><span class="inbox-js-path-segment" style="box-sizing:border-box"><span style="box-sizing:border-box">www</span></span><span class="inbox-separator" style="box-sizing:border-box">/</span><span class="inbox-final-path" style="box-sizing:border-box">index.html</span></font><span class="inbox-final-path" style="box-sizing:border-box;font-weight:600;color:rgb(51,51,51);font-family:-apple-system,blinkmacsystemfont,'segoe ui',roboto,helvetica,arial,sans-serif,'apple color emoji','segoe ui emoji','segoe ui symbol';font-size:16px"> </span>and add the link to the newly created Murano guide that must be published (hosted) somewhere outside the <a href="http://developer.openstack.org">developer.openstack.org</a>?</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Sep 15, 2016 at 3:40 PM Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
<br>
> On Sep 15, 2016, at 1:36 AM, Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>> wrote:<br>
><br>
><br>
>> On 2016-09-14 11:32, Evgeniy Mashkin wrote:<br>
>> Hi all,<br>
>> I'd like to publish First Murano App getting started guide on<br>
>> <a href="http://developers.openstack.org" rel="noreferrer" target="_blank">developers.openstack.org</a> <<a href="http://developers.openstack.org" rel="noreferrer" target="_blank">http://developers.openstack.org</a>>. The main<br>
>> purpose of this article is to facilitate the learning process for Murano<br>
>> App newcome developers and show how it's easy to create a Murano App for<br>
>> their own cloud applications.<br>
>> I intend to use this structure<br>
>> <<a href="https://docs.google.com/document/d/17XatsZ-qJgPtHq_CMHiu4yU88x7TKL-kjzR1qK4Hqjo/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/17XatsZ-qJgPtHq_CMHiu4yU88x7TKL-kjzR1qK4Hqjo/edit?usp=sharing</a>><br>
>> for First Murano App getting started guide. Does it fit my first app<br>
>> structure? You're welcome to comment on it.<br>
><br>
> The FirstApp guide has a different target than what you describe, I<br>
> suggest to name your guide differently.<br>
><br>
>> The another question I have is what the right steps to commit this<br>
>> guide. Marcela already has given me some information. If I got her right<br>
>> I should produce the following steps:<br>
>><br>
>> 1. Create a new directory for First Murano App guide in the root of<br>
>> openstack/api-site repository. For example "firstapp-murano". Its<br>
>> structure should be the same as firstapp directory has:<br>
>> <a href="https://github.com/openstack/api-site/tree/master/firstapp" rel="noreferrer" target="_blank">https://github.com/openstack/api-site/tree/master/firstapp</a><br>
>> 2. Include the folder with First Murano App guide in documentation builder.<br>
>> <a href="https://github.com/openstack/api-site/blob/master/tools/build-firstapp-rst.sh" rel="noreferrer" target="_blank">https://github.com/openstack/api-site/blob/master/tools/build-firstapp-rst.sh</a><br>
><br>
> We build from one directory several guides - for building from a<br>
> separate dir, use tools/build-all-rst.sh.<br>
><br>
>> 3. Update tox.ini file to add First Murano App guide for testing.<br>
>> <a href="https://github.com/openstack/api-site/blob/master/tox.ini" rel="noreferrer" target="_blank">https://github.com/openstack/api-site/blob/master/tox.ini</a><br>
><br>
>> Please, correct me if I'm wrong and give me initial feedback. Then I'm<br>
>> going to send it on review with workflow -1, so we can discuss<br>
>> particular commit at <a href="http://review.openstack.org" rel="noreferrer" target="_blank">review.openstack.org</a> <<a href="http://review.openstack.org" rel="noreferrer" target="_blank">http://review.openstack.org</a>>.<br>
><br>
><br>
> I'd like to see a spec for this kind of work - and consider this an<br>
> Ocata delivery,<br>
><br>
<br>
<br>
Me too - and seriously consider doing the work in the murano repository. I think you'll get more reviews that way. Then you don't need a docs spec either.<br>
<br>
Craig - you should consider this approach too, put the doc in the heat repo and publish to <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a>.<br>
<br>
Thanks,<br>
<br>
Anne<br>
> Andreas<br>
> --<br>
> Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
> HRB 21284 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-docs mailing list<br>
> <a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr">King regards,<div>Evgeniy Mashkin.</div></div></div>