cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: Question About Official Plugins
Date Mon, 28 Jul 2014 20:54:58 GMT
Hello Peter,

The id field is useless without registering your plugin (via plugman) so
that it shows up on plugins.cordova.io[1], and plugman[2] will not allow
you to do so using the apache.cordova namespace/id.

People will only be able to install your plugin via github url, or local
repo path...

I recommend that you change the id immediately, regardless of what happens
in the future.  Adoption is what would drive this to be considered for
inclusion as an official plugin, and currently the only way to track
adoption is via stats collected by plugins.cordova.io

Thanks for bringing this to everyone's attention, I will have a look at it.
 And thanks for your willingness to contribute your code to cordova!

Cheers,
  Jesse

[1] http://plugins.cordova.io
[2] https://github.com/apache/cordova-plugman



@purplecabbage
risingj.com


On Mon, Jul 28, 2014 at 1:36 PM, Peter Metz <peter.metz@unarin.com> wrote:

> Hello Cordova Devs,
>
>
> I wrote a Cordova plugin
> <https://github.com/petermetz/cordova-plugin-ibeacon> which kind of
> accidentally ended up with an official-like plugin ID:
> org.apache.cordova.ibeacon.
> I know that's lame, and would like to state that I didn't intend to
> infringe any copyrights and if instructed so, will change plugin ID, no
> questions asked.
>
> But before all that, please, read on!
>
> I've been advised
> <https://github.com/petermetz/cordova-plugin-ibeacon/issues/24>, that
> because of the fake-official ID, it is not possible to submit the plugin to
> Phonegap Build which I never use, but would not want to leave out people
> who do, for obvious reasons.
>
> Is there even, tiny bit of chance that my plugin could become an official
> one (so it can be present on Phonegap Build), while I'm still able to
> commit changes to it?
> The very first requirement for this I can think if is to comply with the
> licensing of other official plugins which is not a problem.
>
> The plan B is to rename the plugin and include a domain name in the plugin
> ID that I control, but that would put additional workload on the fellow
> users when they want to upgrade their plugin which I'm trying to avoid
> here.
>
> Any help in this matter is very much appreciated, thanks in advance!
>
>
> Kind regards,
> Peter Metz
>

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