+1 to #2 On Fri, Oct 21, 2022 at 5:48 PM Jesse <purplecabb...@gmail.com> wrote:
> #2 makes the most sense to me too, easiest to support long term > > > On Oct 21, 2022, at 8:17 AM, julio cesar sanchez <jcesarmob...@gmail.com> > wrote: > > > > +1 to option #2 > > > > Niklas, option 2 already mentions having a link to the npm search with > > cordova ecosystem prefilled for easier searching of other 3rd party > plugins > > > >> El El vie, 21 oct 2022 a las 16:39, Niklas Merz <niklasm...@apache.org> > >> escribió: > >> > >> I'm +1 on #2, too. Making clear which plugins are Official and supported > >> actively is a good idea. And just a simple note on how to find more on > >> npm is enough IMHO. > >> > >>> On October 21, 2022, Norman Breau <nor...@nbsolutions.ca> wrote: > >>> Hi Team, > >>> > >>> I want to reach a final verdict on how deal with the broken search > >>> page > >>> at https://cordova.apache.org/plugins/ > >>> > >>> We have an active issue being tracked at > >>> https://github.com/apache/cordova-docs/issues/1128 but in summary, > >>> the rest service used to power the search has gone offline and > >>> doesn't > >>> appear to be coming back. > >>> > >>> Throughout the thread there has been several ideals about how to move > >>> forward including: > >>> > >>> 1. Using another third-party API service: https://api-docs.npms.io/ > >>> 2. Having a static page listing the officially supported Apache > >>> plugins, > >>> with a link to https://www.npmjs.com/search?q=ecosystem%3Acordova > >>> 3. Removing the page entirely, maybe with a blog post explaining how > >>> to > >>> find third-party plugins. > >>> > >>> Additionally there are few ideas floated around with using the NPM > >>> Couch > >>> API directly, but there may be terms of use issues involved without > >>> having self-managed server hosting a mirror. > >>> > >>> Personally, I vote -1 for #1 and #3. npms.io doesn't have a clear > >>> terms > >>> of use, as far as I can find. I'm not sure if the API matches the old > >>> npmsearch that we did use, and we may just run into the same issue > >>> down the road. For #3, community members have already explicitly > >>> expressed dissent with removing the page entirely. > >>> > >>> I vote +1 for #2, having the static page with a mention + link to NPM > >>> for third-party plugins. I think this is most likely the best path > >>> forward. > >>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> 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 > > -- Tim Brust timbrust3...@gmail.com
