<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 13, 2017 at 8:46 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:mwessend@redhat.com" target="_blank">mwessend@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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Dec 13, 2017 at 2:36 PM, Craig Brookes <span dir="ltr"><<a href="mailto:cbrookes@redhat.com" target="_blank">cbrookes@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">As mentioned by John having a consistent pattern for our services and their various pieces (cli, apb, ui) etc needs to be figured out.<div><br></div><div>The options:</div><div><br></div><div><b>Single Repo: </b> We kinda ruled this one out as it unlikely it would work well against 3rd part integrations such as 3scale or keycloak.</div><div><br></div><div><br></div><div><b>Repo for each piece: </b>Lots of overhead and different repos. Off the top of my head it would be:</div><div>- repo for any cli piece</div><div>- repo for client sdks (iOS, android, cordova) etc ..</div><div>- repo for APB</div></div></blockquote><div><br></div><div><br></div></span><div>I'd think this is cleanest - each artifact has it's own repository </div><div><br></div><div>In addition, I think we could also move all the apbs to its own GH org. (aerogearplaybookbundles)</div><div><br></div></div></div></div></blockquote><div><br></div><div>I think this makes the most sense as well. Tooling likes single repos, and a separate org let's us point user to the direct shiny things (in aerogear) with out them getting overwhelmed by infrastructure (apb repo). </div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div dir="ltr"><div><br></div><div><b>Single Repo for clients</b></div><div>- 1 repo for cli, sdks and (maybe UI too?)</div><div>- 1 repo for APB (not a client but is a deployment mechanism).</div><div><br></div><div><br></div><div>Any other or better options people can think of?</div><span class="m_4486372779199491663HOEnZb"><font color="#888888"><div><div><br></div>-- <br><div class="m_4486372779199491663m_9003178599930851079gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Craig Brookes<div>RHMAP </div><div>@maleck13 Github</div></div></div>
</div></font></span></div>
<br></span>______________________________<wbr>_________________<br>
feedhenry-dev mailing list<br>
<a href="mailto:feedhenry-dev@redhat.com" target="_blank">feedhenry-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/feedhenry-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/feedhenry-dev</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_4486372779199491663gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Project lead AeroGear.org</div></div>
</font></span></div></div>
<br>______________________________<wbr>_________________<br>
feedhenry-dev mailing list<br>
<a href="mailto:feedhenry-dev@redhat.com">feedhenry-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/feedhenry-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/feedhenry-dev</a><br>
<br></blockquote></div><br></div></div>