<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">https://github.com/aerogear/aerogear-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">https://github.com/aerogear/aerogear-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">https://github.com/aerogearcatalog/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><div><br></div>-- <br><div class="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></div>