PHP module maintenance

[Charles Fry]

Hi,

I was just thinking that it would be nice to have a PHP module
maintenance group, much like the groups which maintain Perl and Java
modules (pkg-perl and pkg-java resepectively, I believe). This would
primarily involve a common repository, and some packaging guidelines.
Uwe's dh-make-php (especially the new version which is about to be
released) makes it very easy to package Pear and Pecl modules. Having
some group-maintained modules might make it easier to add more modules
than we currently have, as it removes the maintenance burdon from single
individuals.

Is anyone else interested in this? If so, could it fit in as part of
pkg-php, or should we create an entirely new Alioth project?

cheers,
Charles

[Ondrej Sury]

Post by Charles Fry
Hi,
I was just thinking that it would be nice to have a PHP module
maintenance group, much like the groups which maintain Perl and Java
modules (pkg-perl and pkg-java resepectively, I believe). This would
primarily involve a common repository, and some packaging guidelines.
Uwe's dh-make-php (especially the new version which is about to be
released) makes it very easy to package Pear and Pecl modules. Having
some group-maintained modules might make it easier to add more modules
than we currently have, as it removes the maintenance burdon from single
individuals.
Is anyone else interested in this? If so, could it fit in as part of
pkg-php, or should we create an entirely new Alioth project?

+1 from me...

Adam?

Ondrej

[Adam Conrad]

Post by Ondrej Sury

Post by Charles Fry
Is anyone else interested in this? If so, could it fit in as part of
pkg-php, or should we create an entirely new Alioth project?

+1 from me...

I'd be fine with granting wider access to pkg-php for a module packaging
group, but then I'd want some promises that they'd play in their own
playground and not wander over to the main php4/ and php5/ parts of the
tree without consulting me first. :)

... Adam

[Charles Fry]

Post by Adam Conrad
I'd be fine with granting wider access to pkg-php for a module packaging
group, but then I'd want some promises that they'd play in their own
playground and not wander over to the main php4/ and php5/ parts of the
tree without consulting me first. :)

Sounds perfectly reasonable. And on second thought, while I think it
makes most sense for modules, I think that other common PHP utilities
might also fit here (stuff like phpDocumentor when it gets packaged).

I like the model adopted by pkg-java, outlined at:

http://java.debian.net/

"There are two kinds of packages in this project:

1. Packages with "Maintainer: Debian Java maintainers
<pkg-java-***@lists.alioth...>" are "public packages":
All members of the pkg-java project are allowed to modify and
upload the package without asking first.

2. Packages with an individual maintainer: Please ask the
maintainer before changing the package or adding yourself to
Uploaders: first.

"The goal is to make all base and library package public so that you
can change them easily e.g. when your application needs an updated
version. You don't have to file a bug report in this case and wait
for the maintainer to upload a new version, you can simply upload
the fixed package yourself. This will hopefully speed up the
integration of Java packages in Debian since most maintainers work
in "bursts" and are unable to spend time for Debian from time to
time."

I would propose we adopt a model like this, with the exception of the
main php4/php5 packages.

If this sounds good to everyone, perhaps you could grant me membership
in the pkg-php project (my username is currently cfry-guest, though the
DAM should be changing that any day now). I'll start by importing the
modules which I maintain (php-cache-lite, php-pager, and php-simpletest)
and by putting together a basic webpage, similar to the pkg-java page
referenced above.

Charles

[Charles Fry]

I would like to move forward with this proposal, as no opposition has
yet been expressed.

I just noticed that pkg-php-maint already maintains a handful of PHP
modules:

http://qa.debian.org/developer.php?login=pkg-php-***@lists.alioth.debian.org

I think it would be valuable to bring more such modules under the
pkg-php-maint umbrella, thus facilitating the packaging of additional
modules that maintainers might lack the motivation to support on their
own.

Charles

-----Original Message-----

Subject: Re: [php-maint] PHP module maintenance
Date: Wed, 31 May 2006 11:33:03 -0400

Post by Adam Conrad
I'd be fine with granting wider access to pkg-php for a module packaging
group, but then I'd want some promises that they'd play in their own
playground and not wander over to the main php4/ and php5/ parts of the
tree without consulting me first. :)

Sounds perfectly reasonable. And on second thought, while I think it
makes most sense for modules, I think that other common PHP utilities
might also fit here (stuff like phpDocumentor when it gets packaged).
http://java.debian.net/
1. Packages with "Maintainer: Debian Java maintainers
All members of the pkg-java project are allowed to modify and
upload the package without asking first.
2. Packages with an individual maintainer: Please ask the
maintainer before changing the package or adding yourself to
Uploaders: first.
"The goal is to make all base and library package public so that you
can change them easily e.g. when your application needs an updated
version. You don't have to file a bug report in this case and wait
for the maintainer to upload a new version, you can simply upload
the fixed package yourself. This will hopefully speed up the
integration of Java packages in Debian since most maintainers work
in "bursts" and are unable to spend time for Debian from time to
time."
I would propose we adopt a model like this, with the exception of the
main php4/php5 packages.
If this sounds good to everyone, perhaps you could grant me membership
in the pkg-php project (my username is currently cfry-guest, though the
DAM should be changing that any day now). I'll start by importing the
modules which I maintain (php-cache-lite, php-pager, and php-simpletest)
and by putting together a basic webpage, similar to the pkg-java page
referenced above.
Charles
--
A guy
Who wants
To middle-aisle it
Must never scratch
His little Violet
Burma-Shave
http://burma-shave.org/jingles/1963/a_guy