Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of ctubbsii@gmail.com designates
 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAF1jEfBVJ3J6eVY1s7KWJnjJuZcJuV3jNf4D5vwy_30_Dy7PQA@mail.gmail.com>
References: 
 <CAL5zq9aga1DDuJh_B79nk8yHgtef-TmF0ecPQHMieYYLF8Tu0Q@mail.gmail.com>
	<CAF1jEfBVJ3J6eVY1s7KWJnjJuZcJuV3jNf4D5vwy_30_Dy7PQA@mail.gmail.com>
Date: Thu, 6 Sep 2012 21:58:55 -0400
Message-ID: 
 <CAL5zq9bwngLZG3ae=53bXjemddxRrjtKFxdExOEhoQzwhw3OCA@mail.gmail.com>
Subject: Re: Dev list spam
From: Christopher Tubbs <ctubbsii@gmail.com>
To: dev@accumulo.apache.org
Content-Type: text/plain; charset=ISO-8859-1

A separate list would be great. Replies working that way would be
great. The JIRA notifications have the type in the subject line, so
that's easy enough to filter, once you've decided to explicitly
subscribe to the jira notifications list (versus getting them when you
might not have expected to on the dev list).

On Thu, Sep 6, 2012 at 9:50 PM, Billie Rinaldi <billie@apache.org> wrote:
> We're halfway through the process of getting a separate notifications list
> set up for JIRA notifications.  The reply-to for things sent to this list
> will be jira@apache, so if you reply to one of the notifications your reply
> will get posted on the ticket as a comment.  (This can be simulated now by
> replying to a ticket and changing the to address to jira@apache.)  The list
> has been created, but the step to switch jira emails so they are sent to
> that list has not been made.  We need to open an INFRA ticket to do that.
> I'm not sure how hard it would be to remove some types of notifications,
> but this is really only an issue when we are doing cleanups like this one.
>
> Billie
>
>
> On Thu, Sep 6, 2012 at 6:35 PM, Christopher Tubbs <ctubbsii@gmail.com>wrote:
>
>> All-
>>
>> It seems to me that notification emails to the dev list for every
>> minor ticket change, even just routine pedantic checks for documenting
>> the affected versions and fix versions, tags, or affected components,
>> is unnecessary. Is it possible to unlink these from the mailing list?
>> Or to make them less spammy?
>>
>> I think new tickets would be useful to get notifications for, but it
>> seems to me that there should be an RSS feed or something similar for
>> that (maybe also for these changes).
>>
>> Another confusing thing is that when these notifications go to the
>> mailing list, people can respond there instead of on the ticket, and
>> you lose important conversation history (or at least, it's harder to
>> piece it together).
>>
>> These are just my thoughts, but what do you guys think?
>>
>> -Christopher
>>
>> P.S. I sincerely apologize for the spam regarding my cleaning up
>> tickets today. I thank you for your patience in this regard.
>>