You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2017/10/12 20:34:17 UTC

Logging list for emails generated by tools

What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated. 

I would also say that we expect every committer to be subscribed to that list.

Ralph

Re: Logging list for emails generated by tools

Posted by Ralph Goers <ra...@dslextreme.com>.
All Jira, Jenkins and GitHub notifications should now be going to notifications@logging.apache.org <ma...@logging.apache.org>. Please subscribe and adjust your email setup.

Ralph

> On Oct 16, 2017, at 7:23 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> So mailto:notifications-subscribe@logging.apache.org to subscribe...
> 
> Gary
> 
> On Mon, Oct 16, 2017 at 7:53 AM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> 
>> The mailing list notifications@logging.apache.org <mailto:
>> notifications@logging.apache.org> has been created. All committers should
>> subscribe.
>> 
>> Ralph
>> 
>>> On Oct 15, 2017, at 3:22 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>> 
>>> It seems there is a self-service tool to create the mailing list.
>>> 
>>> Ralph
>>> 
>>>> On Oct 15, 2017, at 3:15 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>> 
>>>> I have opened a Jira issue with Infra to do this.
>>>> 
>>>> Ralph
>>>> 
>>>>> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote:
>>>>> 
>>>>> Sounds like a good idea.
>>>>> 
>>>>> 
>>>>> On 2017-10-12 22:34, Ralph Goers wrote:
>>>>>> What do others think about the idea of creating a separate mailing
>> list for emails generated by tools? This list gets a bit noisy from all the
>> extra emails and I have a hard time filtering this list because of how some
>> of the emails are generated.
>>>>>> I would also say that we expect every committer to be subscribed to
>> that list.
>>>>>> Ralph
>>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>> 
>> 


Re: Logging list for emails generated by tools

Posted by Gary Gregory <ga...@gmail.com>.
So mailto:notifications-subscribe@logging.apache.org to subscribe...

Gary

On Mon, Oct 16, 2017 at 7:53 AM, Ralph Goers <ra...@dslextreme.com>
wrote:

> The mailing list notifications@logging.apache.org <mailto:
> notifications@logging.apache.org> has been created. All committers should
> subscribe.
>
> Ralph
>
> > On Oct 15, 2017, at 3:22 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > It seems there is a self-service tool to create the mailing list.
> >
> > Ralph
> >
> >> On Oct 15, 2017, at 3:15 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>
> >> I have opened a Jira issue with Infra to do this.
> >>
> >> Ralph
> >>
> >>> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote:
> >>>
> >>> Sounds like a good idea.
> >>>
> >>>
> >>> On 2017-10-12 22:34, Ralph Goers wrote:
> >>>> What do others think about the idea of creating a separate mailing
> list for emails generated by tools? This list gets a bit noisy from all the
> extra emails and I have a hard time filtering this list because of how some
> of the emails are generated.
> >>>> I would also say that we expect every committer to be subscribed to
> that list.
> >>>> Ralph
> >>>
> >>
> >>
> >>
> >
> >
> >
>
>

Re: Logging list for emails generated by tools

Posted by Ralph Goers <ra...@dslextreme.com>.
The mailing list notifications@logging.apache.org <ma...@logging.apache.org> has been created. All committers should subscribe.

Ralph

> On Oct 15, 2017, at 3:22 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> It seems there is a self-service tool to create the mailing list.
> 
> Ralph
> 
>> On Oct 15, 2017, at 3:15 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> 
>> I have opened a Jira issue with Infra to do this.
>> 
>> Ralph
>> 
>>> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote:
>>> 
>>> Sounds like a good idea.
>>> 
>>> 
>>> On 2017-10-12 22:34, Ralph Goers wrote:
>>>> What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated.
>>>> I would also say that we expect every committer to be subscribed to that list.
>>>> Ralph
>>> 
>> 
>> 
>> 
> 
> 
> 


Re: Logging list for emails generated by tools

Posted by Ralph Goers <ra...@dslextreme.com>.
It seems there is a self-service tool to create the mailing list.

Ralph

> On Oct 15, 2017, at 3:15 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> I have opened a Jira issue with Infra to do this.
> 
> Ralph
> 
>> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote:
>> 
>> Sounds like a good idea.
>> 
>> 
>> On 2017-10-12 22:34, Ralph Goers wrote:
>>> What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated.
>>> I would also say that we expect every committer to be subscribed to that list.
>>> Ralph
>> 
> 
> 
> 



Re: Logging list for emails generated by tools

Posted by Ralph Goers <ra...@dslextreme.com>.
I have opened a Jira issue with Infra to do this.

Ralph

> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal <mi...@apache.org> wrote:
> 
> Sounds like a good idea.
> 
> 
> On 2017-10-12 22:34, Ralph Goers wrote:
>> What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated.
>> I would also say that we expect every committer to be subscribed to that list.
>> Ralph
> 



Re: Logging list for emails generated by tools

Posted by Mikael Ståldal <mi...@apache.org>.
Sounds like a good idea.


On 2017-10-12 22:34, Ralph Goers wrote:
> What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated.
> 
> I would also say that we expect every committer to be subscribed to that list.
> 
> Ralph
> 

Re: Logging list for emails generated by tools

Posted by Matt Sicker <bo...@gmail.com>.
We haven't really discussed the use of gitbox in this project yet, so
that's not an issue right now. What we do have is a sync between PR
comments to the mentioned JIRA ticket, and that generates duplicate emails
as it is.

On 13 October 2017 at 01:56, Daan Hoogland <da...@shapeblue.com>
wrote:

> I don’t know if logging is a gitbox project but keep in mind that also a
> lot of the github discussions will disappear if you do this.
>
> On 13/10/2017, 00:56, "Remko Popma" <re...@gmail.com> wrote:
>
>     I think that's a good idea. (I really wish we could have fewer
> duplicate emails though.)
>
>     Remko
>
>
>
>
> Senior Software Developer
> daan.hoogland@shapeblue.com
> www.shapeblue.com
>
>
>
> > On Oct 13, 2017, at 6:59, Dominik Psenner <dp...@gmail.com> wrote:
>     >
>     > Stuff that requires human intervention should stay prominent. The
> rest can
>     > go away. :-)
>     >
>     > 2017-10-12 23:06 GMT+02:00 Ralph Goers <ra...@dslextreme.com>:
>     >
>     >> It will also make the quarterly board reports more accurate.
>     >> reporter.apache.org provides the number of emails received on the
> list
>     >> during the quarter. In my view, having the GitHub, Jira, Jenkins,
> etc
>     >> emails on the dev list skews things as they dominate they number of
> “real”
>     >> discussion emails that happen on the list, which is what I think is
> the
>     >> important part of what the board wants to know.
>     >>
>     >> Ralph
>     >>
>     >>> On Oct 12, 2017, at 1:58 PM, Matt Sicker <bo...@gmail.com> wrote:
>     >>>
>     >>> If it makes email filter rules easier to configure, I'd say go for
> it.
>     >> It'd
>     >>> be just like the commits@ list though with floods of emails
> coming in
>     >> every
>     >>> so often that I just have to skip over (e.g., rebasing a long lived
>     >> branch).
>     >>>
>     >>> On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com>
>     >> wrote:
>     >>>
>     >>>> I do not care either way.
>     >>>>
>     >>>> Gary
>     >>>>
>     >>>> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <
>     >> ralph.goers@dslextreme.com>
>     >>>> wrote:
>     >>>>
>     >>>>> What do others think about the idea of creating a separate
> mailing list
>     >>>>> for emails generated by tools? This list gets a bit noisy from
> all the
>     >>>>> extra emails and I have a hard time filtering this list because
> of how
>     >>>> some
>     >>>>> of the emails are generated.
>     >>>>>
>     >>>>> I would also say that we expect every committer to be subscribed
> to
>     >> that
>     >>>>> list.
>     >>>>>
>     >>>>> Ralph
>     >>>>>
>     >>>>
>     >>>
>     >>>
>     >>>
>     >>> --
>     >>> Matt Sicker <bo...@gmail.com>
>     >>
>     >>
>     >>
>     >
>     >
>     > --
>     > Dominik Psenner
>
>
>


-- 
Matt Sicker <bo...@gmail.com>

Re: Logging list for emails generated by tools

Posted by Daan Hoogland <da...@shapeblue.com>.
I don’t know if logging is a gitbox project but keep in mind that also a lot of the github discussions will disappear if you do this.

On 13/10/2017, 00:56, "Remko Popma" <re...@gmail.com> wrote:

    I think that's a good idea. (I really wish we could have fewer duplicate emails though.)
    
    Remko
    
    
    

Senior Software Developer
daan.hoogland@shapeblue.com
www.shapeblue.com
 
 

> On Oct 13, 2017, at 6:59, Dominik Psenner <dp...@gmail.com> wrote:
    > 
    > Stuff that requires human intervention should stay prominent. The rest can
    > go away. :-)
    > 
    > 2017-10-12 23:06 GMT+02:00 Ralph Goers <ra...@dslextreme.com>:
    > 
    >> It will also make the quarterly board reports more accurate.
    >> reporter.apache.org provides the number of emails received on the list
    >> during the quarter. In my view, having the GitHub, Jira, Jenkins, etc
    >> emails on the dev list skews things as they dominate they number of “real”
    >> discussion emails that happen on the list, which is what I think is the
    >> important part of what the board wants to know.
    >> 
    >> Ralph
    >> 
    >>> On Oct 12, 2017, at 1:58 PM, Matt Sicker <bo...@gmail.com> wrote:
    >>> 
    >>> If it makes email filter rules easier to configure, I'd say go for it.
    >> It'd
    >>> be just like the commits@ list though with floods of emails coming in
    >> every
    >>> so often that I just have to skip over (e.g., rebasing a long lived
    >> branch).
    >>> 
    >>> On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com>
    >> wrote:
    >>> 
    >>>> I do not care either way.
    >>>> 
    >>>> Gary
    >>>> 
    >>>> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <
    >> ralph.goers@dslextreme.com>
    >>>> wrote:
    >>>> 
    >>>>> What do others think about the idea of creating a separate mailing list
    >>>>> for emails generated by tools? This list gets a bit noisy from all the
    >>>>> extra emails and I have a hard time filtering this list because of how
    >>>> some
    >>>>> of the emails are generated.
    >>>>> 
    >>>>> I would also say that we expect every committer to be subscribed to
    >> that
    >>>>> list.
    >>>>> 
    >>>>> Ralph
    >>>>> 
    >>>> 
    >>> 
    >>> 
    >>> 
    >>> --
    >>> Matt Sicker <bo...@gmail.com>
    >> 
    >> 
    >> 
    > 
    > 
    > -- 
    > Dominik Psenner
    


Re: Logging list for emails generated by tools

Posted by Remko Popma <re...@gmail.com>.
I think that's a good idea. (I really wish we could have fewer duplicate emails though.)

Remko


> On Oct 13, 2017, at 6:59, Dominik Psenner <dp...@gmail.com> wrote:
> 
> Stuff that requires human intervention should stay prominent. The rest can
> go away. :-)
> 
> 2017-10-12 23:06 GMT+02:00 Ralph Goers <ra...@dslextreme.com>:
> 
>> It will also make the quarterly board reports more accurate.
>> reporter.apache.org provides the number of emails received on the list
>> during the quarter. In my view, having the GitHub, Jira, Jenkins, etc
>> emails on the dev list skews things as they dominate they number of “real”
>> discussion emails that happen on the list, which is what I think is the
>> important part of what the board wants to know.
>> 
>> Ralph
>> 
>>> On Oct 12, 2017, at 1:58 PM, Matt Sicker <bo...@gmail.com> wrote:
>>> 
>>> If it makes email filter rules easier to configure, I'd say go for it.
>> It'd
>>> be just like the commits@ list though with floods of emails coming in
>> every
>>> so often that I just have to skip over (e.g., rebasing a long lived
>> branch).
>>> 
>>> On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com>
>> wrote:
>>> 
>>>> I do not care either way.
>>>> 
>>>> Gary
>>>> 
>>>> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <
>> ralph.goers@dslextreme.com>
>>>> wrote:
>>>> 
>>>>> What do others think about the idea of creating a separate mailing list
>>>>> for emails generated by tools? This list gets a bit noisy from all the
>>>>> extra emails and I have a hard time filtering this list because of how
>>>> some
>>>>> of the emails are generated.
>>>>> 
>>>>> I would also say that we expect every committer to be subscribed to
>> that
>>>>> list.
>>>>> 
>>>>> Ralph
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Matt Sicker <bo...@gmail.com>
>> 
>> 
>> 
> 
> 
> -- 
> Dominik Psenner

Re: Logging list for emails generated by tools

Posted by Dominik Psenner <dp...@gmail.com>.
Stuff that requires human intervention should stay prominent. The rest can
go away. :-)

2017-10-12 23:06 GMT+02:00 Ralph Goers <ra...@dslextreme.com>:

> It will also make the quarterly board reports more accurate.
> reporter.apache.org provides the number of emails received on the list
> during the quarter. In my view, having the GitHub, Jira, Jenkins, etc
> emails on the dev list skews things as they dominate they number of “real”
> discussion emails that happen on the list, which is what I think is the
> important part of what the board wants to know.
>
> Ralph
>
> > On Oct 12, 2017, at 1:58 PM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > If it makes email filter rules easier to configure, I'd say go for it.
> It'd
> > be just like the commits@ list though with floods of emails coming in
> every
> > so often that I just have to skip over (e.g., rebasing a long lived
> branch).
> >
> > On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> >> I do not care either way.
> >>
> >> Gary
> >>
> >> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <
> ralph.goers@dslextreme.com>
> >> wrote:
> >>
> >>> What do others think about the idea of creating a separate mailing list
> >>> for emails generated by tools? This list gets a bit noisy from all the
> >>> extra emails and I have a hard time filtering this list because of how
> >> some
> >>> of the emails are generated.
> >>>
> >>> I would also say that we expect every committer to be subscribed to
> that
> >>> list.
> >>>
> >>> Ralph
> >>>
> >>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
>


-- 
Dominik Psenner

Re: Logging list for emails generated by tools

Posted by Ralph Goers <ra...@dslextreme.com>.
It will also make the quarterly board reports more accurate. reporter.apache.org provides the number of emails received on the list during the quarter. In my view, having the GitHub, Jira, Jenkins, etc emails on the dev list skews things as they dominate they number of “real” discussion emails that happen on the list, which is what I think is the important part of what the board wants to know.

Ralph

> On Oct 12, 2017, at 1:58 PM, Matt Sicker <bo...@gmail.com> wrote:
> 
> If it makes email filter rules easier to configure, I'd say go for it. It'd
> be just like the commits@ list though with floods of emails coming in every
> so often that I just have to skip over (e.g., rebasing a long lived branch).
> 
> On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com> wrote:
> 
>> I do not care either way.
>> 
>> Gary
>> 
>> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> 
>>> What do others think about the idea of creating a separate mailing list
>>> for emails generated by tools? This list gets a bit noisy from all the
>>> extra emails and I have a hard time filtering this list because of how
>> some
>>> of the emails are generated.
>>> 
>>> I would also say that we expect every committer to be subscribed to that
>>> list.
>>> 
>>> Ralph
>>> 
>> 
> 
> 
> 
> -- 
> Matt Sicker <bo...@gmail.com>



Re: Logging list for emails generated by tools

Posted by Matt Sicker <bo...@gmail.com>.
If it makes email filter rules easier to configure, I'd say go for it. It'd
be just like the commits@ list though with floods of emails coming in every
so often that I just have to skip over (e.g., rebasing a long lived branch).

On 12 October 2017 at 15:45, Gary Gregory <ga...@gmail.com> wrote:

> I do not care either way.
>
> Gary
>
> On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
> > What do others think about the idea of creating a separate mailing list
> > for emails generated by tools? This list gets a bit noisy from all the
> > extra emails and I have a hard time filtering this list because of how
> some
> > of the emails are generated.
> >
> > I would also say that we expect every committer to be subscribed to that
> > list.
> >
> > Ralph
> >
>



-- 
Matt Sicker <bo...@gmail.com>

Re: Logging list for emails generated by tools

Posted by Gary Gregory <ga...@gmail.com>.
I do not care either way.

Gary

On Thu, Oct 12, 2017 at 2:34 PM, Ralph Goers <ra...@dslextreme.com>
wrote:

> What do others think about the idea of creating a separate mailing list
> for emails generated by tools? This list gets a bit noisy from all the
> extra emails and I have a hard time filtering this list because of how some
> of the emails are generated.
>
> I would also say that we expect every committer to be subscribed to that
> list.
>
> Ralph
>