Re: [aerogear-dev] [feedhenry-dev] 5.x Local Development

I wonder about renaming mcp-standalone as part of the move - perhaps to "mobile-core" or similar. -- John Frizelle Chief Architect, Red Hat Mobile Consulting Engineer mobile: *+353 87 290 1644 <//+353872901644>* twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell(a)redhat.com <jfrizell(a)redhat.com&gt;* On 15 December 2017 at 11:32, Matthias Wessendorf <mwessend(a)redhat.com&gt; wrote: > +1 on all of that > > On Fri, Dec 15, 2017 at 12:15 PM, David Martin <davmarti(a)redhat.com&gt; > wrote: > >> Thoughts on doing this welcome >> >> TLDR >> * Move the mcp-standalone repo to Aerogear github org >> * remove the mcp server >> * remove the mcp-standalone service from the Android, iOS & Cordova APBs >> * remove the Mobile Tab from the UI >> * use the remaining ansible stuff for local development >> >> >> Goals of a 5.x local development environment >> * environment for developing services >> * a running OpenShift for developing the CLI against >> * ability to develop the OpenShift UI with a quick feedback loop >> * has the Service Catalog & OpenShift Ansible Broker (for developing >> APBs) >> >> >> DETAILS >> Move the mcp-standalone repo to Aerogear github org >> * part of the overall shift to the aerogear community, and drawing a >> line under the 5.x POC work >> >> Remove the mcp server >> * the mcp server is not going to be continued >> * it was providing some smarts around openshift, which will ultimately >> live in APBs or the CLI/UI >> >> Remove the mcp-standalone service from the Android, iOS & Cordova APBs >> * See last point as the server is not required >> * 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) >> >> Remove the Mobile Tab from the UI >> * Working with UX people, the Mobile tab is not the route we're taking >> * Mobile will become more relevant on the main OpenShift Overview page >> * 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 >> >> Use the remaining ansible stuff for local development >> * The ansible playbooks & roles in this repo are very useful for setting >> up openshift with the ansible service broker >> >> >> [1] https://kubernetes.io/docs/concepts/api-extension/custom-resources/ >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev(a)redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > Project lead AeroGear.org > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev(a)redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > >