Where and how npmsearch getting the npmjs data then? I have to seat and read on what npmsearch is then and better understand . Do they have a service API with SLA and CDN pricing model etc etc... I'm asking because I don't think we want another unreliable registry web page that doesn't scale in our hands.
On Thu, Jul 16, 2015 at 1:45 AM Murat Sutunc <[email protected]> wrote: > There's no such thing as dumb questions! npmjs sadly doesn't give out much > information about packages.. > > From what I recall, they didnt have author name and license information.. > which are important for us. > > > On Jul 15, 2015, at 9:06 PM, Carlos Santana <[email protected]> > wrote: > > > > dumb question why we are using npmsearch? and not a direct api to npmjs, > > like I said it might be a dumb question > > > >> On Mon, Jul 13, 2015 at 6:39 PM Steven Gill <[email protected]> > wrote: > >> > >> Murat and I are going to meet tomorrow to try and launch this to > >> plugins.cordova.io. Once it is out there, we can collect more feedback > and > >> make improvements. > >> > >> On Mon, Jul 13, 2015 at 3:21 PM, Murat Sutunc <[email protected]> > >> wrote: > >> > >>> There were two issues: > >>> - Npmsearch uses npm2es on backend ( > https://www.npmjs.com/package/npm2es > >> ). > >>> The process running npm2es was hung. > >>> - Elijah (owner of npmsearch) also changed the mappings in > elasticsearch, > >>> but never pointed the http server at the new index. > >>> > >>> He fixed both issues and npmsearch is now in sync with npm. Gulp also > >>> relies on npmsearch for its plugin discovery so I'm hoping it will > remain > >>> stable. > >>> > >>> -----Original Message----- > >>> From: Homer, Tony [mailto:[email protected]] > >>> Sent: Monday, July 13, 2015 2:59 PM > >>> To: [email protected] > >>> Subject: Re: [DISCUSS] Release Cordova Plugin npm Search > >>> > >>> Great, looks much better now - thanks Murat! > >>> > >>> Can you shed some light on why this happened (and if it might happen > >>> again)? > >>> If the data is stale, it will hamper discovery of newly published > >> plugins. > >>> > >>> Thanks! > >>> Tony > >>> > >>>> On 7/13/15, 5:43 PM, "Murat Sutunc" <[email protected]> wrote: > >>>> > >>>> Ok, we've managed to resolve the result set issues. It should be now > in > >>>> sync with npm. Woo! > >>>> > >>>> -----Original Message----- > >>>> From: Murat Sutunc [mailto:[email protected]] > >>>> Sent: Friday, July 10, 2015 12:50 PM > >>>> To: <[email protected]> > >>>> Subject: Re: [DISCUSS] Release Cordova Plugin npm Search > >>>> > >>>> I've reached out to npmsearch.com - trying to figure out why it's not > >>>> updating. Will keep you guys updated. :/ > >>>> > >>>>> On Jul 10, 2015, at 12:46 PM, Homer, Tony <[email protected]> > >> wrote: > >>>>> > >>>>> That's true, but that doesn't account for the difference in the size > >>>>> of the result set. > >>>>> The query to both npmsearch.com and npmjs.com/search is > >>>>> "ecosystem:cordova". > >>>>> > >>>>> Tony > >>>>> > >>>>>> On 7/10/15, 2:26 PM, "Jesse" <[email protected]> wrote: > >>>>>> > >>>>>> The 370 results include lots of non-plugins. > >>>>>> > >>>>>> cordova-app-hello-world, cordova-wp8-testtest > >>>>>> > >>>>>> > >>>>>> My team is hiring! > >>>>>> @purplecabbage > >>>>>> risingj.com > >>>>>> > >>>>>> On Fri, Jul 10, 2015 at 10:57 AM, Homer, Tony <[email protected] > > > >>>>>> wrote: > >>>>>> > >>>>>>> I was just checking out the page - nice work, thanks for doing > this! > >>>>>>> > >>>>>>> I had a question about the number of results. > >>>>>>> There are 191 results listed on Cordova Plugin NPM search [1]. > >>>>>>> I also get 191 if I visit (a slightly modified version of) the > >>>>>>> search URL directly [2]. > >>>>>>> But if I visit npmjs and search there for ecosystem:cordova [3], I > >>>>>>> get > >>>>>>> 370 > >>>>>>> results. > >>>>>>> > >>>>>>> Is the large difference in results valid? > >>>>>>> > >>>>>>> 1. http://people.apache.org/~muratsu/?q= > >>>>>>> 2. > >>>>>>> > >>>>>>> > http://npmsearch.com/query?fields=name&q=keywords:%22ecosystem:cord > >>>>>>> o > >>>>>>> va%22 > >>>>>>> &s > >>>>>>> ize=500&start=0 > >>>>>>> 3. https://www.npmjs.com/search?q=ecosystem%3Acordova > >>>>>>> > >>>>>>> Thanks! > >>>>>>> Tony > >>>>>>> > >>>>>>>> On 7/10/15, 1:32 PM, "Jesse" <[email protected]> wrote: > >>>>>>>> > >>>>>>>> Sorting/filtering would be nice. > >>>>>>>> Resist the urge to duplicate the data shown on npm! > >>>>>>>> > >>>>>>>> > >>>>>>>> My team is hiring! > >>>>>>>> @purplecabbage > >>>>>>>> risingj.com > >>>>>>>> > >>>>>>>> On Fri, Jul 10, 2015 at 10:30 AM, Murat Sutunc > >>>>>>>> <[email protected]> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> Can I also get access to remote couchdb? It would be great to go > >>>>>>>>> live today. > >>>>>>>>> > >>>>>>>>> -----Original Message----- > >>>>>>>>> From: Murat Sutunc > >>>>>>>>> Sent: Friday, July 10, 2015 10:29 AM > >>>>>>>>> To: [email protected] > >>>>>>>>> Subject: RE: [DISCUSS] Release Cordova Plugin npm Search > >>>>>>>>> > >>>>>>>>> Nikhil just profiled the website to identify bottlenecks. It's > >>>>>>>>> definitely something I'll be improving. > >>>>>>>>> > >>>>>>>>> I think giving more detailed information about plugins (eg > >>>>>>>>> rendering README.md or showing GH issue count) and sorting is > >>>>>>>>> future work. I > >>>>>>> want > >>>>>>>>> to > >>>>>>>>> ship a MVP to customers and get as much feedback as possible > >>>>>>>>> before > >>>>>>> we > >>>>>>>>> start working on such features. > >>>>>>>>> > >>>>>>>>> -----Original Message----- > >>>>>>>>> From: Carlos Santana [mailto:[email protected]] > >>>>>>>>> Sent: Thursday, July 9, 2015 3:51 PM > >>>>>>>>> To: [email protected] > >>>>>>>>> Subject: Re: [DISCUSS] Release Cordova Plugin npm Search > >>>>>>>>> > >>>>>>>>> What about rendering the README.md, I don't want to duplicate > >>>>>>>>> npmjs, > >>>>>>> but > >>>>>>>>> it would might be better UX to have the readme rendered on the > >>>>>>>>> same > >>>>>>> page > >>>>>>>>> instead opening a new window to npmjs > >>>>>>>>> > >>>>>>>>> what are you using for sorting results, can we sort by most > >>>>>>>>> recent, plugins that get updated frequently tend to be more > >>>>>>>>> healthy, option > >>>>>>> to > >>>>>>>>> sort > >>>>>>>>> by download stat it's nice, but I guess that's on npmjs realm and > >>>>>>> they > >>>>>>>>> don't have that type of sorting in place. > >>>>>>>>> > >>>>>>>>>> On Thu, Jul 9, 2015 at 6:38 PM Shazron <[email protected]> > >> wrote: > >>>>>>>>>> > >>>>>>>>>> Plan looks good to me. > >>>>>>>>>> One problem (not a blocker) is the performance of the search > >> field. > >>>>>>>>>> Try typing "cordova", it stutters as you type (tested on Safari > >>>>>>>>>> 9 > >>>>>>> and > >>>>>>>>>> Chrome 43 > >>>>>>>>>> Mac) > >>>>>>>>>> > >>>>>>>>>> On Thu, Jul 9, 2015 at 3:09 PM, Murat Sutunc > >>>>>>> <[email protected]> > >>>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> Bump :) > >>>>>>>>>>> > >>>>>>>>>>> -----Original Message----- > >>>>>>>>>>> From: Murat Sutunc [mailto:[email protected]] > >>>>>>>>>>> Sent: Tuesday, July 7, 2015 3:19 PM > >>>>>>>>>>> To: [email protected] > >>>>>>>>>>> Subject: [DISCUSS] Release Cordova Plugin npm Search > >>>>>>>>>>> > >>>>>>>>>>> Hey Everyone, > >>>>>>>>>>> > >>>>>>>>>>> I've been working on Cordova Plugin npm Search over the last > >>>>>>>>>>> few weeks. I feel we're now in a good shape to get this > >> released. > >>>>>>>>>>> > >>>>>>>>>>> Please give it a spin: http://people.apache.org/~muratsu/ and > >>>>>>>>>>> use this thread to bring up any release blocking issues. > >>>>>>>>>>> > >>>>>>>>>>> My current thinking is that we handle the migration in two > >>>>>>> phases: > >>>>>>>>>>> > >>>>>>>>>>> Phase 1: > >>>>>>>>>>> > >>>>>>>>>>> - Create a new URL for the npm search - > >>>>>>>>>>> http://plugins.cordova.io/npm > >>>>>>>>>>> > >>>>>>>>>>> - Add a banner to the current CPR search re-directing > >>>>>>>>> traffic > >>>>>>>>>> use > >>>>>>>>>>> the new npm search - > >>>>>>>>>>> https://github.com/apache/cordova-registry-web/pull/17 > >>>>>>>>>>> > >>>>>>>>>>> - Continue making improvements based on feedback to > npm > >>>>>>>>> search > >>>>>>>>>>> > >>>>>>>>>>> Phase 2: (NPM search is default) - July 20th > >>>>>>>>>>> > >>>>>>>>>>> - Move http://plugins.cordova.io URL to the npm > plugin > >>>>>>>>> search > >>>>>>>>>>> page. > >>>>>>>>>>> > >>>>>>>>>>> - Move current CPR search > >>>>>>> http://plugins.cordova.io/lecacy/ > >>>>>>>>>>> > >>>>>>>>>>> PS: > >>>>>>>>>>> A special thank you to all who provided feedback on > >>>>>>>>>>> https://github.com/cordova/cordova-discuss/issues/7 and sent > >>>>>>>>>>> PRs > >>>>>>>>>>> > >>>>>>>>>>> Thanks, > >>>>>>>>>>> Murat > >>>>>>> ------------------------------------------------------------------- > >>>>>>> - > >>>>>>>>>>> - To unsubscribe, e-mail: [email protected] > >>>>>>>>>>> For additional commands, e-mail: [email protected] > >>>>>>> > >>>>>>> > >>>>>>> ------------------------------------------------------------------- > >>>>>>> - > >>>>>>> - To unsubscribe, e-mail: [email protected] > >>>>>>> For additional commands, e-mail: [email protected] > >>>>> > >>>>> > >>>>> --------------------------------------------------------------------- > >>>>> To unsubscribe, e-mail: [email protected] > >>>>> For additional commands, e-mail: [email protected] > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
