<div dir="ltr"><div>We started writing user stories for SDK's (splitting between contributor and user roles )</div><div><span style="font-size:12.8px">SDK'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><br><div style="font-size:12.8px">> and docs for android sdk would end up in:</div><div style="font-size:12.8px"><br></div><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 class="gmail_quote">On Mon, Feb 12, 2018 at 3:11 PM, Paul Wright <span dir="ltr"><<a href="mailto:pwright@redhat.com" target="_blank">pwright@redhat.com</a>></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-<service>-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 'metrics' 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't think switching org is a good experience for anyone (user or contributor), so I'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 'code' repo</div><div>* something else</div><div><div><br></div><div>thanks,</div><div>Paul</div><span class="m_-6405770064194124612m_1934406252705371101HOEnZb"><font color="#888888"><div><br></div>-- <br><div class="m_-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_-6405770064194124612m_1934406252705371101HOEnZb"><font color="#888888">
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "Aerogear" 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&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>-- <br><div class="m_-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>