What would be the added responsibilities for cordova-paramedic? I am all about deleting code, but if we are simply reshuffling responsibilities then we are really not gaining/losing anything.
Originally, and metaphorically ... 'medic' was the hospital and 'paramedic' was the ambulance. To elaborate, for those who don't get metaphors medic was meant to test all the things paramedic was meant to quickly test any simple combo of a plugin+platform Substantial code was added to paramedic to support some other use cases (Appium,Sauce,...), but I would still REALLY like to prevent us turning paramedic into a behemoth travelling hospital ... it may already be too late though. @purplecabbage risingj.com On Mon, Dec 12, 2016 at 1:31 PM, Steven Gill <stevengil...@gmail.com> wrote: > +1 > > On Mon, Dec 12, 2016 at 10:57 AM, Filip Maj <maj....@gmail.com> wrote: > > > Dearest cordova devs, > > > > I'd like to discuss the possibility of killing off the cordova-medic > > repo. Kinda funny, as I landed the first commit in that repo over 4 > > years ago. > > > > I recently sent some updates in a pull request to medic [1], updating > > some appium stuff, and after some discussion with Alex, he pointed out > > that medic is pretty much not used these days. With paramedic taking > > over as both the local testing tool as well as the keystone piece for > > Cordova's CI on cloudapp, I don't think it is worth maintaining two > > similar repositories with lots of code duplication between them. > > > > It looks to me like Apache's buildbot configs for Cordova exist in the > > medic repo. How valuable are these? Worth keeping around? Is execution > > on Apache buildbot going to be a thing once more in the future? > > Cloudapp seems to be doing an excellent job for us on its own... > > > > Other than the buildbot configs, I believe the only thing that needs > > to be migrated out are the Jenkins configs. This would be a beneficial > > move for our CI system anyways, as right now every single Jenkins job > > pulls down the medic repo _solely to get the Jenkins configs_. Moving > > the Jenkins configs into the paramedic repo would save every cloudapp > > job a repo pull, saving some time, and in CI, every second counts :) > > > > Anything else I'm missing? What do y'all think? Good idea? Bad idea? > > > > Thanks for your feedback! > > > > -Fil > > > > [1] https://github.com/apache/cordova-medic/pull/106 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
