Okay, thank you Rich. Then, this is a great topic for the list to come to consensus on, yes?
For my part, I would like to see a separate list for ticket and one for discussion. Totally agree w/Rich on the value and I utilize a very similar model to Rich's in this case. d. On Tue, Oct 15, 2013 at 9:10 AM, Rich Bowen <[email protected]> wrote: > Projects I'm involved in have a separate bugs@ mailing list where the > tickets go. Historically, I do a terrible job of keeping up with ticket > traffic, but am subscribed to various keywords (usually 'documentation' in > my case) so that I can see what I need to see. > > If someone is heavily involved in development they would, of course, be > subscribed to both lists, but if someone was casually involved, or trying > to get involved, the huge volume of tickets traffic is somewhat > overwhelming. Unfortunately, removing the tickets from the dev list leaves > the impression that nothing happens on the dev list, which is also not true. > > So ... I don't know. I know we've discussed this before, and I should go > back and read that. I'm sure we've already arrived at a consensus, and I > just forgot in my frustration. :) > > I tried to set up GMail filters for the Allura tickets, but my patterns > seem to be matching everything. I need to figure that out. > > > On 10/15/2013 11:33 AM, Daniel Hinojosa wrote: > >> Hey Rich, >> >> As our mentor, do you have a recommendation here? What is ASF best >> practice >> in this regard? Do other teams also do things as we do, or do they deal >> with tickets only as tickets and have a separate discussion list? >> >> d. >> >> >> On Tue, Oct 15, 2013 at 7:35 AM, Rich Bowen <[email protected]> wrote: >> >> I'm finding it very, very difficult to keep up with traffic on the dev >>> mailing list, due to the huge volume of ticket auto-emails. I realize >>> that >>> most of the dev discussion does in fact happen in tickets, but the end >>> result is that I'm simply not keeping up. I wonder if it might be time to >>> split ticket mail into a separate list? Would that help, or would it just >>> move the problem to another list? >>> >>> I really want to keep up with how the project is doing but I'm not sure >>> how to do that as things are now, and I'm afraid that it also makes it >>> very >>> hard for new folks to get into the project. >>> >>> -- >>> Rich Bowen >>> [email protected] >>> Shosholoza >>> >>> >>> >> > > -- > Rich Bowen > [email protected] > Shosholoza > > -- *Daniel Hinojosa* *Community Manager, SourceForge / Slashdot Media* p: 415.890.3608 e: [email protected] Twitter: @hinojosad Skype: hinojosad
