Notifications list

[Keith Turner <ke...@deenlo.com>]

Should Github issues and pull request be going to the notifications lists?

Re: Notifications list

[Keith Turner <ke...@deenlo.com>]

Personally, I would prefer all automatically generated traffic go to
notifications.

On Thu, Jul 7, 2016 at 2:13 PM, Josh Elser <jo...@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<ct...@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<ke...@deenlo.com>  wrote:
>>>
>>> Should Github issues and pull request be going to the notifications
>>>> lists?
>>>>
>>>>
>>

Re: Notifications list

[Josh Elser <jo...@gmail.com>]

Hrm. I have no idea how to be sure. I am still watching the repo (from 
before the transition, I guess?).

Christopher wrote:
> Are you sure you're not getting the ones from GitHub because you are
> "Watching" the repo?
>
> On Thu, Jul 7, 2016 at 2:41 PM Christopher<ct...@apache.org>  wrote:
>
>> Oh, hmm.
>>
>> On Thu, Jul 7, 2016 at 2:40 PM Josh Elser<jo...@gmail.com>  wrote:
>>
>>> Really? I've been getting them.
>>>
>>> Christopher wrote:
>>>> Right now, they don't appear to be going anywhere.
>>>>
>>>> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>
>>>   wrote:
>>>>>>>> Should Github issues and pull request be going to the notifications
>>>>> lists?
>

Re: Notifications list

[Christopher <ct...@apache.org>]

Are you sure you're not getting the ones from GitHub because you are
"Watching" the repo?

On Thu, Jul 7, 2016 at 2:41 PM Christopher <ct...@apache.org> wrote:

> Oh, hmm.
>
> On Thu, Jul 7, 2016 at 2:40 PM Josh Elser <jo...@gmail.com> wrote:
>
>> Really? I've been getting them.
>>
>> Christopher wrote:
>> > Right now, they don't appear to be going anywhere.
>> >
>> > On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>
>>  wrote:
>> >>>>
>> >>>>> Should Github issues and pull request be going to the notifications
>> >> lists?
>> >
>>
>

Re: Notifications list

[Christopher <ct...@apache.org>]

Oh, hmm.

On Thu, Jul 7, 2016 at 2:40 PM Josh Elser <jo...@gmail.com> wrote:

> Really? I've been getting them.
>
> Christopher wrote:
> > Right now, they don't appear to be going anywhere.
> >
> > On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>
>  wrote:
> >>>>
> >>>>> Should Github issues and pull request be going to the notifications
> >> lists?
> >
>

Re: Notifications list

[Josh Elser <jo...@gmail.com>]

Really? I've been getting them.

Christopher wrote:
> Right now, they don't appear to be going anywhere.
>
> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>   wrote:
>>>>
>>>>> Should Github issues and pull request be going to the notifications
>> lists?
>

Re: Notifications list

[Josh Elser <jo...@gmail.com>]

Slack could be used instead of IRC if desired. Same goes for Hipchat or 
any other number of services.

End of the day, things still need to happen on the mailing list, yes.

Keith Turner wrote:
> Using slack could possibly be something we could do in addition to properly
> setting up the mailing list.  For Apache purpose I think we need all
> project activity archived in the mailing list.
>
> I have never used slack. Do any other Apache projects use it?  How would
> Slack work with Apache's requirements for archiving project decisions in
> the mailing list?
>
>
>
> On Thu, Jul 7, 2016 at 2:40 PM, Garvit Bansal<ga...@gmail.com>
> 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<ct...@apache.org>  wrote:
>>
>>> Right now, they don't appear to be going anywhere.
>>>
>>> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>
>>> wrote:
>>>>>>> Should Github issues and pull request be going to the notifications
>>>> lists?
>>
>>
>> --
>> *Garvit Bansal,*
>> Software Developer at Flipkart
>> B.Tech in Computer Science and Engineering
>> The LNM Institute of Information Technology
>> Jaipur, Rajasthan-302001
>> *Mobile: *9886384276
>> *Website: *www.garvitbansal.xyz
>>
>> <https://in.linkedin.com/pub/garvit-bansal/50/129/433>
>>
>

Re: Notifications list

[Keith Turner <ke...@deenlo.com>]

Using slack could possibly be something we could do in addition to properly
setting up the mailing list.  For Apache purpose I think we need all
project activity archived in the mailing list.

I have never used slack. Do any other Apache projects use it?  How would
Slack work with Apache's requirements for archiving project decisions in
the mailing list?



On Thu, Jul 7, 2016 at 2:40 PM, Garvit Bansal <ga...@gmail.com>
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 <ct...@apache.org> wrote:
>
> > Right now, they don't appear to be going anywhere.
> >
> > On Thu, Jul 7, 2016 at 2:18 PM Josh Elser <jo...@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<ct...@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<ke...@deenlo.com>
> > wrote:
> > > >>
> > > >>> Should Github issues and pull request be going to the notifications
> > > lists?
> > > >>>
> > > >
> > >
> >
>
>
>
> --
> *Garvit Bansal,*
> Software Developer at Flipkart
> B.Tech in Computer Science and Engineering
> The LNM Institute of Information Technology
> Jaipur, Rajasthan-302001
> *Mobile: *9886384276
> *Website: *www.garvitbansal.xyz
>
> <https://in.linkedin.com/pub/garvit-bansal/50/129/433>
>

Re: Notifications list

[Josh Elser <jo...@gmail.com>]

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.

http://apache.org/foundation/mailinglists.html

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<ct...@apache.org>  wrote:
>
>> Right now, they don't appear to be going anywhere.
>>
>> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser<jo...@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<ct...@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<ke...@deenlo.com>
>> wrote:
>>>>>> Should Github issues and pull request be going to the notifications
>>> lists?
>
>
>

Re: Notifications list

[Garvit Bansal <ga...@gmail.com>]

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 <ct...@apache.org> wrote:

> Right now, they don't appear to be going anywhere.
>
> On Thu, Jul 7, 2016 at 2:18 PM Josh Elser <jo...@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<ct...@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<ke...@deenlo.com>
> wrote:
> > >>
> > >>> Should Github issues and pull request be going to the notifications
> > lists?
> > >>>
> > >
> >
>



-- 
*Garvit Bansal,*
Software Developer at Flipkart
B.Tech in Computer Science and Engineering
The LNM Institute of Information Technology
Jaipur, Rajasthan-302001
*Mobile: *9886384276
*Website: *www.garvitbansal.xyz

<https://in.linkedin.com/pub/garvit-bansal/50/129/433>

Re: Notifications list

[Christopher <ct...@apache.org>]

Right now, they don't appear to be going anywhere.

On Thu, Jul 7, 2016 at 2:18 PM Josh Elser <jo...@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<ct...@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<ke...@deenlo.com>  wrote:
> >>
> >>> Should Github issues and pull request be going to the notifications
> lists?
> >>>
> >
>

Re: Notifications list

[Josh Elser <jo...@gmail.com>]

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<ct...@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<ke...@deenlo.com>  wrote:
>>
>>> Should Github issues and pull request be going to the notifications lists?
>>>
>

Re: Notifications list

[Christopher <ct...@apache.org>]

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 <ct...@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 <ke...@deenlo.com> wrote:
>
>> Should Github issues and pull request be going to the notifications lists?
>>
>

Re: Notifications list

[Christopher <ct...@apache.org>]

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 <ke...@deenlo.com> wrote:

> Should Github issues and pull request be going to the notifications lists?
>