Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of tommy@devgeeks.org designates
 209.85.220.53 as permitted sender)
Subject: Re: Time to do something about the PhoneGap Plugins repo
References: <174C27A6-2F45-4785-BFF5-E0487514159C@devgeeks.org>
 <CAE6O_-YuEGmsP_tgfhP0mwA8sKMkHfA+aEKtB1oeo=cdMHKbtw@mail.gmail.com>
From: tommy-carlos Williams <tommy@devgeeks.org>
Content-Type: text/plain;
	charset=utf-8
In-Reply-To: 
 <CAE6O_-YuEGmsP_tgfhP0mwA8sKMkHfA+aEKtB1oeo=cdMHKbtw@mail.gmail.com>
Message-Id: <8B23DFDD-CAF4-4A17-BF4B-E4DA419C5281@devgeeks.org>
Date: Fri, 25 Jan 2013 07:08:45 +1100
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Thanks Shazron,

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

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

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


- tommy

On 25/01/2013, at 6:32, Shazron <shazron@gmail.com> 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.
>=20
> 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.
>=20
> I've started it off here:
> https://github.com/phonegap/phonegap-plugins/issues/995
>=20
>=20
> On Thu, Jan 24, 2013 at 1:44 AM, Tommy-Carlos Williams
> <tommy@devgeeks.org>wrote:
>=20
>> Hi all (especially Shazron, Simon and anyone else working day-to-day on
>> the Plugins repo),
>>=20
>> There seems to be a trend at the moment with the plugins repo for users t=
o
>> get angry and jump on the entitlement train when the plugin they wanna us=
e
>> isn't maintained and updated quickly enough, even though that would have t=
o
>> 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 ne=
w
>> plugins they submit in their own repos and only have a link to them in th=
e
>> README on the main repo=E2=80=A6 but=E2=80=A6.
>>=20
>> I am proposing that we get proactive about the authors looking after thei=
r
>> own plugins.
>>=20
>> 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).
>>=20
>> 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=E2=80=A6=
 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.
>>=20
>> What say you?
>>=20
>>=20
>>=20
>> - tommy