Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: 76.96.27.227 is neither permitted nor
 denied by domain of dave@brondsema.net)
Message-ID: <525D7804.8040507@brondsema.net>
Date: Tue, 15 Oct 2013 13:14:44 -0400
From: Dave Brondsema <dave@brondsema.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: allura-dev@incubator.apache.org
Subject: Re: Tickets mailing list?
References: <525D52A5.3060300@rcbowen.com>
 <CAM+nhkQNRaN5Wz-PjTUT5F6shdBVYvWKjjAZrM1e1jXp0ncf5g@mail.gmail.com>
 <525D68F7.5060902@rcbowen.com>
 <CAM+nhkT9Hxa=184xUm5PHt_6UERd8Wsps2mAiEa-=X0ij1_y-A@mail.gmail.com>
In-Reply-To: 
 <CAM+nhkT9Hxa=184xUm5PHt_6UERd8Wsps2mAiEa-=X0ij1_y-A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

That's a good use case and a separate bugs list is a good solution.  Asking
everyone to set up a filter for the bugs is not too friendly.

For reference, spamassassin's dev list gets a lot of ticket updates.  Just an
example, doesn't mean it's better.
http://mail-archives.apache.org/mod_mbox/spamassassin-dev/

I'd be ok with tickets on a separate mailing list.

I'd also be interested in merging the allura-dev and allura-users mailing lists.
 The users list is very quiet currently and most new incubator projects only
start with one (add the -users list when the need is there).


On 10/15/13 1:01 PM, Daniel Hinojosa wrote:
> 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 <rbowen@rcbowen.com> 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 <rbowen@rcbowen.com> 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
>>>> rbowen@rcbowen.com
>>>> Shosholoza
>>>>
>>>>
>>>>
>>>
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com
>> Shosholoza
>>
>>
> 
> 


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><