I'm actually open to any suggestions here. That said, consolidating down to the a few of the more trafficked lists seems to be the most popular option so far. That seems reasonable to me; I'm more concerned about lists that might be ambiguous to the new user- like 'fw-core', 'fw-server', or 'fw-formats', which also happened to be the less trafficked ones. I would put forth that the only reason we have a subscribe all function is that we have too many lists. :) Having a separate list for 'developers' (ie users) and 'contributors' is an interesting idea, although there are those questions that could work in both, and I'd be reluctant to give any contributor an easy means for avoiding the basic usage questions. ;) There are positives and negatives to this idea, let's think about it.
,Wil > -----Original Message----- > From: Gunter Sammet [mailto:[EMAIL PROTECTED] > Sent: Monday, December 17, 2007 8:35 AM > To: [email protected] > Subject: Re: [fw-general] Project Teams and Separate Mailing Lists. . . > > The way I understood it, Will didn't suggest to move to one list. He > just suggested that we could remove a few that don't generate traffic. > One reason they might didn't generate traffic is the reason that the > subscribe all didn't work. For the longest time I didn't receive the > MVC emails because I subscibed to all and it didn't work. > > I think MVC and DB are fine. general might be split in general usage > and general FW development. But this might result in less emails > answered in general usage if developers skip that list. > > Just my thoughts. > > Gunter
