debian-php mailing list

[Charles Fry]

It would be nice to have a dedicated Debian mailing list for PHP,
similar to those for other prominent languages. While the webapps
mailing list has its role with respect to web applications, I can't help
but thinking that we would benefit from a debian-php list as well.

Charles

[Neil McGovern]

Post by Charles Fry
It would be nice to have a dedicated Debian mailing list for PHP,
similar to those for other prominent languages. While the webapps
mailing list has its role with respect to web applications, I can't help
but thinking that we would benefit from a debian-php list as well.

Well, this was the original name for debian-webapps :)

Have a look at the following refs for discussion of why this isn't just
debian-php:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264069
http://lists.debian.org/debian-devel/2005/04/msg01144.html

Cheers,
Neil

[Charles Fry]

Post by Neil McGovern

Post by Charles Fry
It would be nice to have a dedicated Debian mailing list for PHP,
similar to those for other prominent languages. While the webapps
mailing list has its role with respect to web applications, I can't help
but thinking that we would benefit from a debian-php list as well.

Well, this was the original name for debian-webapps :)
Have a look at the following refs for discussion of why this isn't just
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264069
http://lists.debian.org/debian-devel/2005/04/msg01144.html

And I am arguing that we should also have a debian-php list. :-)

I think that the arguments for a webapps mailing list are justified, but
I feel that they tried to provide a single solution to two different
problems.

I think that there are (at least) two distinct types of discussions on
debian-webapps. Those that are specific to PHP, that really belong on a
debian-php list. And those that are about webapp policy type issues,
which are more fit for the webapps list. I personally see almost no
overlap here.

The biggest problem that I have with the current setup (i.e. the lack of
a debian-php list) is visibility. Someone comes along and wants to
package some PHP modules. They do a quick search and find no PHP list,
so go off and do things on their own. There is no reason why someone
working with some PHP packages (especially that aren't webapps) would be
attracted to the webapps mailing list, any more than someone packaging
an apache module would be attracted to webapps.

The webapps list may have its own unique purpose, but I don't think that
makes up for the lack of a debian-php list.

Charles

[sean finney]

Post by Charles Fry
I think that the arguments for a webapps mailing list are justified, but
I feel that they tried to provide a single solution to two different
problems.

i would say more than two. you're right that the php stuff can easily
be extracted out of the equation into a single project, as can some
of the other topics. the real question is whether further splintering
of the project into subprojects would do a service or disservice.

i tend to think that it wouldn't benefit things in the long run unless
there were sufficient numbers of people interested in purely doing php
related stuff to keep things going. with the volume of traffic on this list,
i can't say i'm confident in that. but with the recent talk of forming a
super-archive for php maintainance via pkg-php, this could be changing.

Post by Charles Fry
The biggest problem that I have with the current setup (i.e. the lack of
a debian-php list) is visibility. Someone comes along and wants to
package some PHP modules. They do a quick search and find no PHP list,

i would argue this point isn't really an issue. try a google search
for debian php policy:

http://www.google.se/search?q=debian+php+policy

if you want to work on visibility, i think helping the php draft to the
point that it gets into the developers' reference and new maintainers'
guide is the best thing you can do. having debian-***@l.d.o really
won't help much besides a percieved seal of authenticity.


sean


--