cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <shaz...@gmail.com>
Subject Re: new meta data for plugin.xml
Date Fri, 18 Oct 2013 18:54:24 GMT
Perhaps either plugman or the registry should do some validation, and have
some "required" fields? I know that PhoneGap Build when you try to submit a
plugin they error out if you are missing some fields that they require.


On Fri, Oct 18, 2013 at 11:50 AM, Gorkem Ercan <gorkem.ercan@gmail.com>wrote:

> +1 for adding metadata but should more of the metadata be compulsory?
>
>  JBoss tools plugin discovery uses the cordova.io registry and some of the
> plugins are missing a lot to.  http://snag.gy/aAxjL.jpg is a screenshot
> that shows how the case. http://snag.gy/J8rl6.jpg is a screenshot of a few
> plugins that has most of its data. As you can see with the missing
> descriptions etc. it is not possible to do an informed decision on whether
> to use a plugin or not. Although information such as keywords does not seem
> like important it becomes quite useful when you are trying to find a
> certain plugin.
> --
> Gorkem
>
>
> On Fri, Oct 18, 2013 at 1:12 PM, Michal Mocny <mmocny@chromium.org> wrote:
>
> > +1 to repo / issue / website / docs etc metadata
> >
> > -1 *for now* to dependencies at specific versions, and testing related
> > changes like <mode>, just because its not clear what the right solution
> to
> > these problems is.  We do need to address it, but those topics will
> likely
> > move to separate discussions.
> >
> >
> > On Fri, Oct 18, 2013 at 12:24 PM, Lucas Holmquist <lholmqui@redhat.com
> > >wrote:
> >
> > > i was just thinking the same thing  :)
> > > On Oct 18, 2013, at 12:06 PM, Carlos Santana <csantana23@gmail.com>
> > wrote:
> > >
> > > > plugin.xml metadata is looking more and more like a package.json
> (i.e.
> > > npm)
> > > > ;-p
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Oct 18, 2013 at 11:40 AM, Steve Gill <stevengill97@gmail.com
> >
> > > wrote:
> > > >
> > > >> Yes I meant plugins.xml
> > > >>
> > > >>
> > > >>
> > > >>> On Oct 18, 2013, at 5:43 AM, Lucas Holmquist <lholmqui@redhat.com>
> > > >> wrote:
> > > >>>
> > > >>>
> > > >>>> On Oct 17, 2013, at 7:54 PM, Steven Gill <stevengill97@gmail.com>
> > > >> wrote:
> > > >>>>
> > > >>>> So looks like want to to start including more data on
> > > >>>> http://plugins.cordova.io.
> > > >>>>
> > > >>>> Repo tag -> points to repo where plugin lives
> > > >>>> Issue tag -> points to issue tracker (with component for
jira)
> > > >>>>
> > > >>>> Testing related (can get discussed more in testing thread
> > > >>>> Mode tag -> to differentiate between testing mode and normal
mode
> > > >>>> JS module tag for test module
> > > >>>>
> > > >>>> Dependency related
> > > >>>> adding version number to dependency tags so they don't just
grab
> > > latest
> > > >>>> always. Multiple approaches were discussed and this discussion
> > should
> > > >>>> probably happen in a new thread.
> > > >>>>
> > > >>>> Thoughts on above? Suggestions for other meta data we should
look
> > into
> > > >>>> adding to config.xml?
> > > >>> did you mean plugin.xml?
> > > >>>
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Carlos Santana
> > > > <csantana23@gmail.com>
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message