Re: No Readme for plugin packages on npm
alright finee On Fri, May 8, 2015 at 11:41 AM, Shazron wrote: > It's a new release - so in short, yes in regards to a vote (you'll need to > up the ver# to publish to npm correct? So it's a new release). > > > On Friday, May 8, 2015, Steven Gill wrote: > > > Not sure if we need to do a release if all we change is the readme. Shaz, > > any thoughts? > > > > On Fri, May 8, 2015 at 10:02 AM, Nikhil Khandelwal < > nikhi...@microsoft.com > > > > > wrote: > > > > > Thanks, Steve. Let me know if you run into headwind with fixing this - > > > I'll be happy to help out removing the problematic comments. Though > that > > > would require another plugin release to get it out. From Shaz's > previous > > > reference to Apache policy, it might be fine for the .md files to not > > have > > > the Apache license header. > > > > > > Thanks, > > > Nikhil > > > > > > > > > -----Original Message- > > > From: Steven Gill [mailto:stevengil...@gmail.com ] > > > Sent: Thursday, May 7, 2015 6:18 PM > > > To: dev@cordova.apache.org > > > Subject: Re: No Readme for plugin packages on npm > > > > > > https://github.com/npm/marky-markdown/issues/42 > > > > > > I will try to see if I can fix marky-markdown myself. If it isn't easy, > > we > > > could just update our readme's and republish. > > > > > > On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal < > > nikhi...@microsoft.com > > > > > > > wrote: > > > > > > > Thanks, Steven! Do you have a pointer to the issue? In case they > can't > > > > get do this soon - perhaps we should explore a workaround. > > > > > > > > -Nikhil > > > > > > > > -Original Message- > > > > From: Steven Gill [mailto:stevengil...@gmail.com ] > > > > Sent: Thursday, April 23, 2015 6:34 PM > > > > To: dev@cordova.apache.org > > > > Subject: Re: No Readme for plugin packages on npm > > > > > > > > I filed the issue a few days ago with npm. They are working on fixing > > it. > > > > The parser is struggling with html comments On Apr 23, 2015 6:14 PM, > > > > "Nikhil Khandelwal" > wrote: > > > > > > > > > It looks like npm cannot find the readme for plugin packages: > > > > > https://www.npmjs.com/package/cordova-plugin-battery-status > > > > > > > > > > Github can find it just fine though: > > > > > https://github.com/apache/cordova-plugin-battery-status > > > > > > > > > > Thanks, > > > > > Nikhil > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > >
Re: No Readme for plugin packages on npm
It's a new release - so in short, yes in regards to a vote (you'll need to up the ver# to publish to npm correct? So it's a new release). On Friday, May 8, 2015, Steven Gill wrote: > Not sure if we need to do a release if all we change is the readme. Shaz, > any thoughts? > > On Fri, May 8, 2015 at 10:02 AM, Nikhil Khandelwal > > wrote: > > > Thanks, Steve. Let me know if you run into headwind with fixing this - > > I'll be happy to help out removing the problematic comments. Though that > > would require another plugin release to get it out. From Shaz's previous > > reference to Apache policy, it might be fine for the .md files to not > have > > the Apache license header. > > > > Thanks, > > Nikhil > > > > > > -Original Message- > > From: Steven Gill [mailto:stevengil...@gmail.com ] > > Sent: Thursday, May 7, 2015 6:18 PM > > To: dev@cordova.apache.org > > Subject: Re: No Readme for plugin packages on npm > > > > https://github.com/npm/marky-markdown/issues/42 > > > > I will try to see if I can fix marky-markdown myself. If it isn't easy, > we > > could just update our readme's and republish. > > > > On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal < > nikhi...@microsoft.com > > > > > wrote: > > > > > Thanks, Steven! Do you have a pointer to the issue? In case they can't > > > get do this soon - perhaps we should explore a workaround. > > > > > > -Nikhil > > > > > > -Original Message- > > > From: Steven Gill [mailto:stevengil...@gmail.com ] > > > Sent: Thursday, April 23, 2015 6:34 PM > > > To: dev@cordova.apache.org > > > Subject: Re: No Readme for plugin packages on npm > > > > > > I filed the issue a few days ago with npm. They are working on fixing > it. > > > The parser is struggling with html comments On Apr 23, 2015 6:14 PM, > > > "Nikhil Khandelwal" > wrote: > > > > > > > It looks like npm cannot find the readme for plugin packages: > > > > https://www.npmjs.com/package/cordova-plugin-battery-status > > > > > > > > Github can find it just fine though: > > > > https://github.com/apache/cordova-plugin-battery-status > > > > > > > > Thanks, > > > > Nikhil > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > >
Re: No Readme for plugin packages on npm
Not sure if we need to do a release if all we change is the readme. Shaz, any thoughts? On Fri, May 8, 2015 at 10:02 AM, Nikhil Khandelwal wrote: > Thanks, Steve. Let me know if you run into headwind with fixing this - > I'll be happy to help out removing the problematic comments. Though that > would require another plugin release to get it out. From Shaz's previous > reference to Apache policy, it might be fine for the .md files to not have > the Apache license header. > > Thanks, > Nikhil > > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Thursday, May 7, 2015 6:18 PM > To: dev@cordova.apache.org > Subject: Re: No Readme for plugin packages on npm > > https://github.com/npm/marky-markdown/issues/42 > > I will try to see if I can fix marky-markdown myself. If it isn't easy, we > could just update our readme's and republish. > > On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal > > wrote: > > > Thanks, Steven! Do you have a pointer to the issue? In case they can't > > get do this soon - perhaps we should explore a workaround. > > > > -Nikhil > > > > -Original Message- > > From: Steven Gill [mailto:stevengil...@gmail.com] > > Sent: Thursday, April 23, 2015 6:34 PM > > To: dev@cordova.apache.org > > Subject: Re: No Readme for plugin packages on npm > > > > I filed the issue a few days ago with npm. They are working on fixing it. > > The parser is struggling with html comments On Apr 23, 2015 6:14 PM, > > "Nikhil Khandelwal" wrote: > > > > > It looks like npm cannot find the readme for plugin packages: > > > https://www.npmjs.com/package/cordova-plugin-battery-status > > > > > > Github can find it just fine though: > > > https://github.com/apache/cordova-plugin-battery-status > > > > > > Thanks, > > > Nikhil > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
RE: No Readme for plugin packages on npm
Thanks, Steve. Let me know if you run into headwind with fixing this - I'll be happy to help out removing the problematic comments. Though that would require another plugin release to get it out. From Shaz's previous reference to Apache policy, it might be fine for the .md files to not have the Apache license header. Thanks, Nikhil -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Thursday, May 7, 2015 6:18 PM To: dev@cordova.apache.org Subject: Re: No Readme for plugin packages on npm https://github.com/npm/marky-markdown/issues/42 I will try to see if I can fix marky-markdown myself. If it isn't easy, we could just update our readme's and republish. On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal wrote: > Thanks, Steven! Do you have a pointer to the issue? In case they can't > get do this soon - perhaps we should explore a workaround. > > -Nikhil > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Thursday, April 23, 2015 6:34 PM > To: dev@cordova.apache.org > Subject: Re: No Readme for plugin packages on npm > > I filed the issue a few days ago with npm. They are working on fixing it. > The parser is struggling with html comments On Apr 23, 2015 6:14 PM, > "Nikhil Khandelwal" wrote: > > > It looks like npm cannot find the readme for plugin packages: > > https://www.npmjs.com/package/cordova-plugin-battery-status > > > > Github can find it just fine though: > > https://github.com/apache/cordova-plugin-battery-status > > > > Thanks, > > Nikhil > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: No Readme for plugin packages on npm
https://github.com/npm/marky-markdown/issues/42 I will try to see if I can fix marky-markdown myself. If it isn't easy, we could just update our readme's and republish. On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal wrote: > Thanks, Steven! Do you have a pointer to the issue? In case they can't get > do this soon - perhaps we should explore a workaround. > > -Nikhil > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Thursday, April 23, 2015 6:34 PM > To: dev@cordova.apache.org > Subject: Re: No Readme for plugin packages on npm > > I filed the issue a few days ago with npm. They are working on fixing it. > The parser is struggling with html comments On Apr 23, 2015 6:14 PM, > "Nikhil Khandelwal" wrote: > > > It looks like npm cannot find the readme for plugin packages: > > https://www.npmjs.com/package/cordova-plugin-battery-status > > > > Github can find it just fine though: > > https://github.com/apache/cordova-plugin-battery-status > > > > Thanks, > > Nikhil > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
RE: No Readme for plugin packages on npm
Thanks, Steven! Do you have a pointer to the issue? In case they can't get do this soon - perhaps we should explore a workaround. -Nikhil -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Thursday, April 23, 2015 6:34 PM To: dev@cordova.apache.org Subject: Re: No Readme for plugin packages on npm I filed the issue a few days ago with npm. They are working on fixing it. The parser is struggling with html comments On Apr 23, 2015 6:14 PM, "Nikhil Khandelwal" wrote: > It looks like npm cannot find the readme for plugin packages: > https://www.npmjs.com/package/cordova-plugin-battery-status > > Github can find it just fine though: > https://github.com/apache/cordova-plugin-battery-status > > Thanks, > Nikhil > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: No Readme for plugin packages on npm
I filed the issue a few days ago with npm. They are working on fixing it. The parser is struggling with html comments On Apr 23, 2015 6:14 PM, "Nikhil Khandelwal" wrote: > It looks like npm cannot find the readme for plugin packages: > https://www.npmjs.com/package/cordova-plugin-battery-status > > Github can find it just fine though: > https://github.com/apache/cordova-plugin-battery-status > > Thanks, > Nikhil >
