[php-maint] Co-maintenance of phpunit ? - Was: Re: Packaging PHP_CodeCoverage and others from phpunit.de (needed by phpunit 3.5)

Olivier Berger olivier.berger at it-sudparis.eu
Sat Feb 5 11:19:10 UTC 2011

Le samedi 05 février 2011 à 11:26 +0800, Thomas Goirand a écrit :
> On 02/04/2011 06:16 PM, Olivier Berger wrote:
> > May I suggest to those interested in maintaining phpunit to subscribe (and
> > eventually followup) to bug #607393 [0].
> Ok, subscribed.
> > I'm thinking about co-maintenance if others are interested, through this project
> > or another.
> I'd be happy to give a hand for reviewing and sponsoring packages (even
> if my time may be limited). 


I think Roland Mas could be another sponsor too, as he mentioned it too.
We'll ask on the list when it's time, in any case.

> But once again: I don't do CDBS packages, so
> please use debhelper instead.

Hmmm... I'm not sure it's worth the pain to change what just works.

Is it such a big thing to review other's work in CDBS... after all, only
the content once packaged may matter, and if there's no problem, so CDBS
could be fine ? ... anyway, it's a matter of taste, so I guess there's
no point arguing.

phpunit is currently using CDBS, so I'll probably stick to it unless I'm
stuck on technical issues (I've never really used CDBS myself before...
but seems it's working so far).

> > I'm not sure I could find that info : is there some collaborative
> > maintenance git repo for PEAR modules ?
> On Alioth, see /git/pkg-php. There's all the php PEAR modules that I
> maintain there, and few others. 

OK, now I can see them... I added a pointer in the wiki page too.

> > Also, note that the phpunit-related packages aren't maintained
> > upstream in the standard PEAR repos, but instead in phpunit.de ...
> > would it make a difference, relating to their maintenance ?
> I don't see why we would need to make it differently. These are still
> some PEAR packages, and should be maintained the same way. 


> I just think
> that we might take care a bit more about the licensing if it is using
> the PHP license (because only PHP and PEAR things are acceptable in
> Debian if they are licensed under the PHP license). I'm not saying it's
> a blocker, I'm saying that I don't know... :) Can you tell what type of
> license is in use there? I saw some FreeBSD things, which is of course
> more than OK...

Upstream seems to mention BSD, but I guess we'll have to check a bit
more in details before uploading an updated package.

> > Oh, and forgot to say I was open to collab maintenance on this one (as
> > well as on the rest of PHPUnit, unless someone wants it for his own
> > profit ;)
> I think it would be best if you join the pkg-php project on Alioth, so
> you can use /git/pkg-php for your packages. We'd better avoid spreading
> all the packages across the HDDs of Alioth, because it will become a
> mess! Note that I'm not an admin on pkg-php, so Raphael or someone else
> will have to approve you in.

Well do.

Thanks for the details.

Best regards,
Olivier BERGER <olivier.berger at it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)

More information about the pkg-php-maint mailing list