<div dir="ltr">+1 on all of that <br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 15, 2017 at 12:15 PM, David Martin <span dir="ltr"><<a href="mailto:davmarti@redhat.com" target="_blank">davmarti@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"><div>Thoughts on doing this welcome</div><div><br></div>TLDR<div>* Move the mcp-standalone repo to Aerogear github org</div><div>* remove the mcp server</div><div>* remove the mcp-standalone service from the Android, iOS & Cordova APBs</div><div>* remove the Mobile Tab from the UI</div><div>* use the remaining ansible stuff for local development</div><div><br></div><div><br></div><div>Goals of a 5.x local development environment<br class="m_5739706433240134649gmail-Apple-interchange-newline">* environment for developing services<br class="m_5739706433240134649gmail-Apple-interchange-newline">* a running OpenShift for developing the CLI against<div>* ability to develop the OpenShift UI with a quick feedback loop</div><div>* has the Service Catalog & OpenShift Ansible Broker (for developing APBs)</div><div><br></div><div><br></div><div>DETAILS</div><div>Move the mcp-standalone repo to Aerogear github org<br></div><div>* part of the overall shift to the aerogear community, and drawing a line under the 5.x POC work</div><div><br></div><div>Remove the mcp server<br></div><div>* the mcp server is not going to be continued</div><div>* it was providing some smarts around openshift, which will ultimately live in APBs or the CLI/UI</div><div><br></div><div><div>Remove the mcp-standalone service from the Android, iOS & Cordova APBs</div></div><div>* See last point as the server is not required</div><div>* these App APBs will just need to create a mobile app representation in OpenShift e.g. a ConfigMap or Mobile App CRD [1] (Separate proposal/discussion for switching to a CRD)</div><div><br></div><div><div>Remove the Mobile Tab from the UI</div></div><div>* Working with UX people, the Mobile tab is not the route we're taking</div><div>* Mobile will become more relevant on the main OpenShift Overview page</div><div>* UI development can continue similar to before (via UI extensions) until a decision is made about how mobile bits make it into the Openshift Web Console</div><div><br></div><div><div>Use the remaining ansible stuff for local development</div></div><div>* The ansible playbooks & roles in this repo are very useful for setting up openshift with the ansible service broker</div><div><br></div><div><br></div><div>[1] <a href="https://kubernetes.io/docs/concepts/api-extension/custom-resources/" target="_blank">https://kubernetes.io/<wbr>docs/concepts/api-extension/<wbr>custom-resources/</a></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_5739706433240134649gmail_signature"><div dir="ltr"><div><div dir="ltr">David Martin<div>Red Hat Mobile</div><div>Twitter: <span style="font-size:12.8px">@irldavem</span></div><div><span style="font-size:12.8px">IRC: @irldavem (feedhenry, mobile-internal)</span></div></div></div></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><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Project lead AeroGear.org</div></div>
</div></div>