You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary <ga...@wandisco.com> on 2012/03/27 18:18:22 UTC

Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity

Ticket raised associated with Greg's suggestion for notifications going 
direct to the mailing lists.

On 03/27/2012 04:12 PM, Apache Bloodhound wrote:
> #21: Site notification of ticket and wiki activity
> -----------------------+-----------------
>   Reporter:  gjm        |      Owner:  gjm
>       Type:  task       |     Status:  new
>   Priority:  blocker    |  Milestone:
> Component:  siteadmin  |    Version:
>   Keywords:             |
> -----------------------+-----------------
>   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.
>


Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity

Posted by Gary <ga...@wandisco.com>.
On 03/27/2012 06:29 PM, Greg Stein wrote:
> On Tue, Mar 27, 2012 at 13:21, Gary<ga...@wandisco.com>  wrote:
>> 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?
> That would be best. DIscussion should be steered onto -dev, so a
> Reply-To on any commit (or wiki edit) would be excellent. Note: I
> *think* that ezmlm sets the Reply-To header for bloodhound-commits@.
> Assuming that's true, then the BH instance doesn't need to bother with
> it. I'd say "just try it" :-)

Well, emails are currently sent direct to a person when they update a 
ticket and so I had already set the Reply-To to bloodhound-dev@. I think 
this is the right thing to do as we might not expect a user to be 
subscribed to bloodhound-commits@.

I am thinking that always emailing the ticket owner or the ticket 
reporter might feel a bit like spam if they are not able to turn it off 
so I have not enabled those options. I believe that users should be able 
to use the cc ticket field for that purpose if they are interested.

Does that seem reasonable for now?

Cheers,
     Gary

Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity

Posted by Greg Stein <gs...@gmail.com>.
On Tue, Mar 27, 2012 at 13:21, Gary <ga...@wandisco.com> wrote:
> 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?

That would be best. DIscussion should be steered onto -dev, so a
Reply-To on any commit (or wiki edit) would be excellent. Note: I
*think* that ezmlm sets the Reply-To header for bloodhound-commits@.
Assuming that's true, then the BH instance doesn't need to bother with
it. I'd say "just try it" :-)

> 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.

Thanks!

Cheers,
-g

Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity

Posted by Gary <ga...@wandisco.com>.
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