fluo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: Notifications list
Date Thu, 07 Jul 2016 19:31:12 GMT
Hi Garvit,

No, using Slack as the "notification delivery" mechanism isn't an 
option. Here at Apache, email is very important and a hard requirement 
that all discussions related to the project get recorded on the list 
(which the ASF archives and makes searchable).

Slack, or any other chat service, can also get a copy of notifications 
and be used for informal discussions, but, the mailing list needs to 
have the final copy.


Garvit Bansal wrote:
> Just a opinion: Can we used slack for Notification. It will be helpful to
> keep track when pull request raised, commits made in repos and to keep
> track of all overall activity done on Github.
> On Thu, Jul 7, 2016 at 11:52 PM, Christopher<ctubbsii@apache.org>  wrote:
>> Right now, they don't appear to be going anywhere.
>> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<josh.elser@gmail.com>  wrote:
>>> By default, they go to the dev list. I believe we can ask for them to be
>>> sent to notifications if we so desire.
>>> Christopher wrote:
>>>> After thinking about it, even though I'd have expected things to go to
>>> the
>>>> dev list, I'd prefer they go to notifications.
>>>> On Thu, Jul 7, 2016 at 11:30 AM Christopher<ctubbsii@apache.org>
>> wrote:
>>>>> I'd expect them to go to the dev list. Perhaps that part of Fluo's
>>> GItHub
>>>>> integration was never set up?
>>>>> On Thu, Jul 7, 2016 at 10:09 AM Keith Turner<keith@deenlo.com>
>> wrote:
>>>>>> Should Github issues and pull request be going to the notifications
>>> lists?

View raw message