<div dir="ltr">Thanks Jose,<div>I will follow up and move things appropriately after we agree on the layout.</div><div>So what you&#39;re saying (and I like it) is:</div><div><br></div><div><div><a href="https://github.com/aerogear">https://github.com/aerogear</a>:</div><div>* mobile-docs<br></div><div>* &lt;sdk&gt;/docs</div><div>* mobile-cli/docs</div></div><div><div><br></div><div><a href="https://github.com/aerogearcatalog">https://github.com/aerogearcatalog</a></div><div>* &lt;service&gt;-apb/docs</div></div><div><br></div><div>I&#39;m assuming that the release tagging for &lt;service&gt;-apb repo is always the &#39;version number&#39; we want to communicate to end users?</div><div><br></div><div>It&#39;s unfortunate that it&#39;s split over two github organizations, but we can &#39;fix that in docs&#39; if agreed,</div><div><br></div><div>Paul</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 13, 2018 at 7:49 AM, Jose Miguel Gallas Olmedo <span dir="ltr">&lt;<a href="mailto:jgallaso@redhat.com" target="_blank">jgallaso@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi Paul,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default"><font face="arial, helvetica, sans-serif">think docs should live into their respective repos (including references and guides) since it&#39;s always easier for everyone to find them. Documentation about services in the -apb repos, SDKs in -sdk repos and so on.</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><br></font></div><div class="gmail_default"><span class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><font color="#0000ff">At a meeting a few weeks ago, we decided not to centralize all the docs for mobile.next, because:<br>* keep docs closer to code<br>* keep docs and code versioned together<br>* allow devs update docs in same repo as they are working<br>We also decided not to create sidecar repos, eg a mobile-&lt;service&gt;-docs repo.</font></blockquote><div> </div></span><div><span style="font-family:arial,helvetica,sans-serif">Assuming <i>we </i>as in <i>we, Aerogear, </i>several of docs from </span><a href="https://github.com/aerogear/mobile-docs/tree/master/services" style="font-family:arial,helvetica,sans-serif" target="_blank">https://github.com/<wbr>aerogear/mobile-docs/</a><span style="font-family:arial,helvetica,sans-serif"> should be moved into their respective repos.</span><br></div><div><span style="font-family:arial,helvetica,sans-serif"><br></span></div></div><div class="gmail_default"><span style="font-family:arial,helvetica,sans-serif">I however think mobile-docs would be good to have general documentation and how-tos that affects several services or the platform itself like </span><i style="font-family:arial,helvetica,sans-serif">adding-services-to-<wbr>ansible-broker.adoc</i><span style="font-family:arial,helvetica,sans-serif">.</span></div><div class="gmail_default"><span style="font-family:arial,helvetica,sans-serif"><br></span></div><div class="gmail_default"><span style="font-family:arial,helvetica,sans-serif">Regards,</span></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-5453504667726397075gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>JOSE MIGUEL</span> <span>GALLAS OLMEDO</span></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>ASSOCIATE QE, mobile</span></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat <span><br><br></span></a></p><p style="font-family:overpass,sans-serif;margin:0px 0px 6px;font-size:10px;color:rgb(153,153,153)"><span href="tel:+34618488633">M: <a href="http://redhatemailsignature-marketing.itos.redhat.com/" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+34618488633</a>    </span></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png" width="90" height="auto"></a></td></tr></tbody></table></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On 12 February 2018 at 16:24, Wojciech Trocki <span dir="ltr">&lt;<a href="mailto:wtrocki@redhat.com" target="_blank">wtrocki@redhat.com</a>&gt;</span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>We started writing user stories for SDK&#39;s (splitting between contributor and user roles )</div><div><span style="font-size:12.8px">SDK&#39;s already have solid base that will be extended over the time, with similar patterns across platforms.</span></div><div><br></div><b>IOS: </b><br><a href="https://github.com/aerogear/aerogear-ios-sdk/tree/master/docs" target="_blank">https://github.com/aerogear/ae<wbr>rogear-ios-sdk/tree/master/doc<wbr>s</a><br><div> </div><div><b>Android </b>(WIP - going to be updated soon)<br></div><div><a href="https://github.com/aerogear/aerogear-android-sdk/tree/master/docs" target="_blank">https://github.com/aerogear/ae<wbr>rogear-android-sdk/tree/master<wbr>/docs</a></div><div><span><br><div style="font-size:12.8px">&gt; and docs for android sdk would end up in:</div><div style="font-size:12.8px"><br></div></span><div style="font-size:12.8px"><span style="font-size:small"><a href="https://github.com/aerogear/aerogear-android-sdk/tree/master/docs" target="_blank">https://github.com/aerogear/ae<wbr>rogear-android-sdk/tree/master<wbr>/docs</a></span>/push</div></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Android-sdk repository is just used for Mobile OpenShift Service Catalog (AeroGear Services) </div><div style="font-size:12.8px">so push SDK may be probably in separate repository and be imported into AeroGear Services SDK.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Regards</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Wojtek</div><div style="font-size:12.8px"><br></div><div class="gmail_extra"><div><div class="m_-5453504667726397075h5"><div class="gmail_quote">On Mon, Feb 12, 2018 at 3:11 PM, Paul Wright <span dir="ltr">&lt;<a href="mailto:pwright@redhat.com" target="_blank">pwright@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div>At a meeting a few weeks ago, we decided not to centralize all the docs for mobile.next, because:</div><div><br></div><div>* keep docs closer to code</div><div>* keep docs and code versioned together</div><div>* allow devs update docs in same repo as they are working</div><div><br></div><div>We also decided not to create sidecar repos, eg a mobile-&lt;service&gt;-docs repo.</div><div><br></div><div>With that in mind, I thought that docs for push would end up in:</div><div><a href="https://github.com/aerogear/aerogear-unifiedpush-server" target="_blank">https://github.com/aerogear/ae<wbr>rogear-unifiedpush-server</a><br></div><div><br></div><div>and docs for android sdk would end up in:</div><div><br></div><div><a href="https://github.com/aerogear/aerogear-android-sdk" target="_blank">https://github.com/aerogear/ae<wbr>rogear-android-sdk</a><br></div><div><br></div><div>but that was before I discovered that the following is the nearest thing to a &#39;metrics&#39; repo that would be suitable for /docs:</div><div><a href="https://github.com/aerogearcatalog/metrics-apb" target="_blank">https://github.com/aerogearcat<wbr>alog/metrics-apb</a><br></div><div><br></div><div>However, I don&#39;t think switching org is a good experience for anyone (user or contributor), so I&#39;m wondering if anyone has a good idea where to docs should live (relative to the code), eg:</div><div><br></div><div>* service and sdk docs live the apb repos</div><div>* service docs in apb repos, and sdk docs in &#39;code&#39; repo</div><div>* something else</div><div><div><br></div><div>thanks,</div><div>Paul</div><span class="m_-5453504667726397075m_-1085515170274940889m_-6405770064194124612m_1934406252705371101HOEnZb"><font color="#888888"><div><br></div>-- <br><div class="m_-5453504667726397075m_-1085515170274940889m_-6405770064194124612m_1934406252705371101m_-4843949379156810704gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Paul Wright<div>Senior Technical Writer</div><div>Red Hat, Waterford, Ireland</div><div>gitlab: finp<br></div></div></div></div></div></div></div>
</font></span></div></div><span class="m_-5453504667726397075m_-1085515170274940889m_-6405770064194124612m_1934406252705371101HOEnZb"><font color="#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &quot;Aerogear&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:aerogear+unsubscribe@googlegroups.com" target="_blank">aerogear+unsubscribe@googlegro<wbr>ups.com</a>.<br>
To post to this group, send email to <a href="mailto:aerogear@googlegroups.com" target="_blank">aerogear@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/aerogear/CALLRKFhFVgDt1KiAiJ1R22qmcP%2Be_%2Bp3g9hbYnrrRoqXFuvKzQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank">https://groups.google.com/d/ms<wbr>gid/aerogear/CALLRKFhFVgDt1KiA<wbr>iJ1R22qmcP%2Be_%2Bp3g9hbYnrrRo<wbr>qXFuvKzQ%40mail.gmail.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/op<wbr>tout</a>.<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div>-- <br><div class="m_-5453504667726397075m_-1085515170274940889m_-6405770064194124612m_1934406252705371101gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:12.8px"><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>WOJCIECH</span> <span>TROCKI</span></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px;text-decoration:none" target="_blank">Red Hat <span>Mobile</span></a></p><p style="font-family:overpass,sans-serif;margin:0px 0px 6px;font-size:10px;color:rgb(153,153,153)"><span>IM: <span>wtrocki</span></span></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a></td></tr></tbody></table></div></div></div></div></div></div></div></div></div>
</div></div><span>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &quot;Aerogear&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:aerogear+unsubscribe@googlegroups.com" target="_blank">aerogear+unsubscribe@googlegro<wbr>ups.com</a>.<br>
To post to this group, send email to <a href="mailto:aerogear@googlegroups.com" target="_blank">aerogear@googlegroups.com</a>.<br></span></div></div>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/aerogear/CAO0%2Bn%2BrSV8fD5A4fuTJiKrXoba2MpnXrSB1CLrmV%3DrYgnZ%2BCzA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank">https://groups.google.com/d/ms<wbr>gid/aerogear/CAO0%2Bn%2BrSV8fD<wbr>5A4fuTJiKrXoba2MpnXrSB1CLrmV%<wbr>3DrYgnZ%2BCzA%40mail.gmail.com</a><wbr>.<span class=""><div class="m_-5453504667726397075HOEnZb"><div class="m_-5453504667726397075h5"><br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/op<wbr>tout</a>.<br>
</div></div></span></blockquote></div><br></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">Paul Wright<div>Senior Technical Writer</div><div>Red Hat, Waterford, Ireland</div><div>gitlab: finp<br></div></div></div></div></div></div></div>
</div>