Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.martin@wandisco.com
 designates 74.125.83.47 as permitted sender)
Message-ID: <4F71F70D.3020505@wandisco.com>
Date: Tue, 27 Mar 2012 18:21:17 +0100
From: Gary <gary.martin@wandisco.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #21: Site notification of ticket and wiki
 activity
References: <052.ab4a4bdf8989ee9557a3b5a0c01706d1@incubator.apache.org>
 <4F71E84E.9020002@wandisco.com>
In-Reply-To: <4F71E84E.9020002@wandisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 03/27/2012 05:18 PM, Gary wrote:
>
>>   The Bloodhound instance should send notifications to appropriate 
>> apache
>>   mailing lists:
>>    * wiki edit notifications to bloodhound-commits
>>    * issue changes to bloodhound-dev
>>
>>   This may require new plugins.
>>
>

To continue this discussion.. is there an argument for sending all the 
relevant notifications to the bloodhound-commits mailing list with the 
Reply-To set to bloodhound-dev?

I don't think we get wiki change notifications out of the box so I will 
look at both http://trac-hacks.org/wiki/AnnouncerPlugin and 
http://trac-hacks.org/wiki/WikiNotificationPlugin to see how well those 
work.

Cheers,
     Gary