On Tue, Apr 10, 2001 at 11:47:26AM -0400, James A. Treacy wrote: > The closest thing to a solution we've come up with to date is that the > web team maintain the list description information themselves. While > this has potential to succeed it also suffers from a communication > problem. How does the web team know when a new list is created. > Additionally, how do we create a description when we know nothing > about the list.
Maybe we could have a data file containing the names and subscription of all the lists, which the web team would pick up from the listmaster data, and have a separate system for descriptions, that the web team would maintain. That way the worst thing that could happen with new lists is that they have no description listed. This is basically how the descriptions on the lists.debian.org web page work: if there's no mention of a list in the configuration file, it gets mentioned in the "other" section, without a description. But the archives are there. > Perhaps this could all be pushed off on the people requesting the > list. Wherever it is explained how to request a list, it could be > explained that it is their responsibility to send the necessary info > to debian-www (list name, section, description, whether moderated and > whether open or closed subscription). Most of this is needed by the > listmasters already. The listmasters could simply drop a note (or forward the mail) to debian-www when they create a list. They have to close the bug report anyway, so another CC: can't be much work :) -- Digital Electronic Being Intended for Assassination and Nullification
