Re: [DISCUSS] EOL cordova-medic

2016-12-12 Thread Vladimir Kotikov (Akvelon)
Hey all! I’m +1 for killing Medic, since it hasn’t been used for months and I guess hardly ever will be used in the future. Though I have a bit different proposal about moving configs – IMO they are a part of CI and should live somewhere inside a CI. I don’t think there is a need to either

Re: [DISCUSS] EOL cordova-medic

2016-12-12 Thread Filip Maj
On Mon, Dec 12, 2016 at 1:46 PM, Jesse wrote: > What would be the added responsibilities for cordova-paramedic? Good question. As far as I can tell, I believe paramedic would need to additionally house the helper JSON files containing configuration that one passes into

Re: [DISCUSS] EOL cordova-medic

2016-12-12 Thread Jesse
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

Re: [DISCUSS] EOL cordova-medic

2016-12-12 Thread Steven Gill
+1 On Mon, Dec 12, 2016 at 10:57 AM, Filip Maj 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

[DISCUSS] EOL cordova-medic

2016-12-12 Thread Filip Maj
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,