On Sun, 2005-05-01 at 12:08 +0200, Francesco Paolo Lovergine wrote: > On Sun, May 01, 2005 at 11:56:47AM +0200, Alexis Sukrieh wrote: > > Pascal Hakim wrote: > > >Speaking as a listmaster, I believe that a list that would be used to > > >provide people with a place to discuss the packaging of web-apps, as > > >well as standard things associated with it is a great idea. It's better > > >than debian-apache (after all, there's other web servers out there), and > > >it's better than creating a debian-php list. We want this to be used by > > >all web-apps, whether they be in php, python, perl or whatever the > > >flavour of the week is. > > > > Ok. > > It seems that everyone here agrees on the fact that such a list would be > > helpful and could enhance the way webapp packages are made. > > > > I find Frankie's suggestion interesting and would vote for an Alioth > > account for hosting the mailinglist. Moreover, if we want to start > > writing a "Debian Webapp Policy Manual", alioth is a good idea too, I > > suppose. > > > > First of all we have to find a correct name for such a project. I was > > thinking at something generic like "webapp-policy" but other ideas are > > welcome. > > > > I think a suitable section in debian policy would be appropriate. And > mere technical discussions about the policy contents are also > appropriate in d-policy. All other technical discussions should go > in an alioth list. My suggestion of an alioth list is due to
Do the policy discussion on the new list, and make a new debian web apps sub policy, in the same way we have perl and emacs policies. Leave the main debian policy out of it, until we have something that works, and is used by most web apps. This is how the system is meant to work. > current discouraging (and long delays) for a new proper list on > lists.debian.org. If interested people would think a l.d.o list > is better, that could also be nice. Once you've got me convinced the list is a good idea, it usually doesn't take too long to create it. Cheers, Pasc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
