On Fri, Jun 02, 2006 at 06:09:26PM -0400, Charles Fry wrote: > 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. > 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-foo@l.d.o really won't help much besides a percieved seal of authenticity. sean --
Attachment:
signature.asc
Description: Digital signature