[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team

On 05/30/2012 03:51 AM, Jonas Smedegaard wrote:
> I strongly object to this as a general principle: Debian freezing is no 
> excuse for hijacking!

That's not the reason, the reason is that we've been working on tools to
PHP package quality, and recently noticed that php-codesniffer was left
unmaintained since 2008.

> Seems you had several years of solving this issue, yet you waited until 
> just before freeze

No, me and Luis Uribe just recently found interest in it, and thought
it'd be
great to have it in Wheezy too.

> and the option you came up with was to kick a 
> maintainer.

We aren't kicking him, we want to have the package team maintained.
He's fine to come and join!

> Did you consider an NMU?

Yes, but the issue is that there's lots of invasive changes that we would
like to make to the packaging. Having a look to the current state of the
package, it'd be nearly totally re-written. There's not a single line in the
debian/control file that satisfies me, I'd like to move from dh_php_make
to pkg-php-tools (that implies, from CDBS to dh 8 sequencer), etc.

This doesn't really qualify for an NMU, nor does the upgrade to the latest
upstream version.

On 05/30/2012 07:45 AM, Charles Plessy wrote:
> I concur.  It is socially and technically safer to give about two week-ends to
> answer, keeping time zones in mind.

My reasoning over the one week only was that the package hasn't been
maintained since 2008, so that anyways, it feels like the package isn't
well enough maintained to be left to Jack sole responsibility. Again, he
would be free to join the PKG PEAR team. But I'll wait one more week
as you suggest then, this doesn't mater much...

> If after this delay you have no news, my
> opinion is that hijacking is the best solution.  The maintainer's other
> packages have already attracted three NMUs in total, and I have not seen a bug
> report with his answer after 2009 (although got some packages sponsored in
> 2011).  By the way, perhaps you can keep his sponosor (rmgolbeck) in the loop,
> maybe he knows other ways to contact the maintainer ?
rmgolbeck is Cc: to this mail.


Thomas Goirand (zigo)

Reply to: