cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tommy-carlos Williams <>
Subject Re: Time to do something about the PhoneGap Plugins repo
Date Thu, 24 Jan 2013 20:08:45 GMT
Thanks Shazron,

I am more than happy to help go through and try and contact authors. 

As for taking over some semi-abandoned plugins, haven't we all already sort of had to in the
past? Heh. 

There are a couple off the top of my head that I use regularly enough that if the author can't
be contacted or determined I would be happy to take on.  

- tommy

On 25/01/2013, at 6:32, Shazron <> wrote:

> Sure. We could come up with standard boilerplate migration text,
> @github_username them in a new issue and see what happens, and give them 2
> weeks - then we add the a standard "UNMAINTAINED" text to the README.
> Beyond doing that, there's not much we should or can do.
> Moving them to our own repos, that's another story since that requires
> commitment not only in maintenance but also knowing how the code works etc.
> I'd say that if the plugin is "abandoned" we solicit volunteers to take it
> over into their own repo. If there are no takers, we "archive" it in the
> same repo until someone wants to resurrect it.
> I've started it off here:
> On Thu, Jan 24, 2013 at 1:44 AM, Tommy-Carlos Williams
> <>wrote:
>> Hi all (especially Shazron, Simon and anyone else working day-to-day on
>> the Plugins repo),
>> There seems to be a trend at the moment with the plugins repo for users to
>> get angry and jump on the entitlement train when the plugin they wanna use
>> isn't maintained and updated quickly enough, even though that would have to
>> be a full time job to maintain that many plugins authored by other people.
>> We have taken a step in the right direction encouraging people to keep new
>> plugins they submit in their own repos and only have a link to them in the
>> README on the main repo… but….
>> I am proposing that we get proactive about the authors looking after their
>> own plugins.
>> I am proposing that we go through the plugins and where we *can* discern
>> who the author *is*, try and contact them and ask them to host the plugin
>> in their own repo as we have started to do (and therefore have their own
>> issue tracking for their own code).
>> Where we cannot, we should decide if it is a plugin one of us is willing
>> to maintain. If so, great, we move it to one of our repos. If not… Put a
>> note right in the top of the README that the plugin might not be up to
>> date, etc. Caveat Emptor and all that.
>> What say you?
>> - tommy

View raw message