You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2011/09/09 23:22:53 UTC
Mailing list noise
Aha, I have finally subscribed to the dev list.
First thing I've noticed is that most of the traffic on *-dev list constitutes
of JIRA comments. I'd suggest to redirect these to *-commit list (unless we
want to create a separate list for bugs notifications ;) instead of polluting
dev discussions.
The problem with current setup is that most ppl are likely to filter out JIRA
traffic to somewhere (like /dev/null), but all these messages will sit in the
archive and will simply create difficulties if someone needs to find stuff
later on.
--
Take care,
Cos
Re: Mailing list noise
Posted by Bruno Mahé <bm...@apache.org>.
On 09/09/2011 04:04 PM, Roman Shaposhnik wrote:
> On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
>> The problem with current setup is that most ppl are likely to filter out JIRA
>> traffic to somewhere (like /dev/null), but all these messages will sit in the
>> archive and will simply create difficulties if someone needs to find stuff
>> later on.
> A strong +1. Do you know what needs to be done in order to make it happen?
> I expect it to be an INFRA JIRA but would be nice to know for sure.
>
> Thanks,
> Roman.
+1
Re: Mailing list noise
Posted by Patrick Hunt <ph...@apache.org>.
in my experience typically such changes require jira admin rights,
enter an INFRA jira.
On Tue, Sep 13, 2011 at 9:05 AM, Andrew Bayer <an...@gmail.com> wrote:
> INFRA JIRA is probably the way to go.
>
> A.
>
> On Tue, Sep 13, 2011 at 8:47 AM, Roman Shaposhnik <rv...@apache.org> wrote:
>
>> On Sun, Sep 11, 2011 at 2:21 PM, Konstantin Boudnik <co...@apache.org>
>> wrote:
>> > Right. This is what I was kinda referring as a separate list for
>> notification
>> > in my OP (Hadoop keep separate *-issues@ list for every component).
>> However,
>> > the mixed approached might be even better as it allows to avoid any
>> update
>> > traffic unless a person is specifically watching an issue.
>> >
>> > To summarize (under assumption that *-issues@ list is being created)
>> > - JIRA create notifications are to go to bigtop-dev@ and bigtop-issues@lists
>> > - following updates to go only to bigtop-issues@ list
>>
>> I think we all agree on the above.
>>
>> At this point, do we need to chant to get attention of one of the
>> Apache arhats?
>> Or should we just file an INFRA JIRA?
>>
>> Thanks,
>> Roman.
>>
>
Re: Mailing list noise
Posted by Andrew Bayer <an...@gmail.com>.
INFRA JIRA is probably the way to go.
A.
On Tue, Sep 13, 2011 at 8:47 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> On Sun, Sep 11, 2011 at 2:21 PM, Konstantin Boudnik <co...@apache.org>
> wrote:
> > Right. This is what I was kinda referring as a separate list for
> notification
> > in my OP (Hadoop keep separate *-issues@ list for every component).
> However,
> > the mixed approached might be even better as it allows to avoid any
> update
> > traffic unless a person is specifically watching an issue.
> >
> > To summarize (under assumption that *-issues@ list is being created)
> > - JIRA create notifications are to go to bigtop-dev@ and bigtop-issues@lists
> > - following updates to go only to bigtop-issues@ list
>
> I think we all agree on the above.
>
> At this point, do we need to chant to get attention of one of the
> Apache arhats?
> Or should we just file an INFRA JIRA?
>
> Thanks,
> Roman.
>
Re: Mailing list noise
Posted by Roman Shaposhnik <rv...@apache.org>.
On Sun, Sep 11, 2011 at 2:21 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Right. This is what I was kinda referring as a separate list for notification
> in my OP (Hadoop keep separate *-issues@ list for every component). However,
> the mixed approached might be even better as it allows to avoid any update
> traffic unless a person is specifically watching an issue.
>
> To summarize (under assumption that *-issues@ list is being created)
> - JIRA create notifications are to go to bigtop-dev@ and bigtop-issues@ lists
> - following updates to go only to bigtop-issues@ list
I think we all agree on the above.
At this point, do we need to chant to get attention of one of the
Apache arhats?
Or should we just file an INFRA JIRA?
Thanks,
Roman.
Re: Mailing list noise
Posted by Konstantin Boudnik <co...@apache.org>.
Right. This is what I was kinda referring as a separate list for notification
in my OP (Hadoop keep separate *-issues@ list for every component). However,
the mixed approached might be even better as it allows to avoid any update
traffic unless a person is specifically watching an issue.
To summarize (under assumption that *-issues@ list is being created)
- JIRA create notifications are to go to bigtop-dev@ and bigtop-issues@ lists
- following updates to go only to bigtop-issues@ list
Cos
On Sat, Sep 10, 2011 at 07:41AM, Alan Gates wrote:
> You should consider the approach Hadoop has taken where JIRA creates and
> resolves go to the dev list, but comments go to some other list (not sure
> which one). This makes it easy for people to see what is changing, and if
> they are interested in a particular JIRA when it is created, they can watch
> it and keep up to date. Just moving all JIRA traffic to commits will hide
> much of the work of the community from many potential contributors.
>
> Alan.
>
> On Sep 9, 2011, at 4:20 PM, Konstantin Boudnik wrote:
>
> > Someone with JIRA admin karma should be able to do the switch in no time. I
> > think we have plenty of guys like that among the mentors of the project.
> >
> > Owen, could you redirect BigTop JIRA notification traffic from bigtop-dev@ to
> > bigtop-commits@ ? Or do we need to go through the official INFRA process for
> > that?
> >
> > Thanks,
> > Cos
> >
> > On Fri, Sep 09, 2011 at 04:04PM, Roman Shaposhnik wrote:
> >> On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
> >>> The problem with current setup is that most ppl are likely to filter out JIRA
> >>> traffic to somewhere (like /dev/null), but all these messages will sit in the
> >>> archive and will simply create difficulties if someone needs to find stuff
> >>> later on.
> >>
> >> A strong +1. Do you know what needs to be done in order to make it happen?
> >> I expect it to be an INFRA JIRA but would be nice to know for sure.
> >>
> >> Thanks,
> >> Roman.
>
Re: Mailing list noise
Posted by Alan Gates <ga...@hortonworks.com>.
You should consider the approach Hadoop has taken where JIRA creates and resolves go to the dev list, but comments go to some other list (not sure which one). This makes it easy for people to see what is changing, and if they are interested in a particular JIRA when it is created, they can watch it and keep up to date. Just moving all JIRA traffic to commits will hide much of the work of the community from many potential contributors.
Alan.
On Sep 9, 2011, at 4:20 PM, Konstantin Boudnik wrote:
> Someone with JIRA admin karma should be able to do the switch in no time. I
> think we have plenty of guys like that among the mentors of the project.
>
> Owen, could you redirect BigTop JIRA notification traffic from bigtop-dev@ to
> bigtop-commits@ ? Or do we need to go through the official INFRA process for
> that?
>
> Thanks,
> Cos
>
> On Fri, Sep 09, 2011 at 04:04PM, Roman Shaposhnik wrote:
>> On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
>>> The problem with current setup is that most ppl are likely to filter out JIRA
>>> traffic to somewhere (like /dev/null), but all these messages will sit in the
>>> archive and will simply create difficulties if someone needs to find stuff
>>> later on.
>>
>> A strong +1. Do you know what needs to be done in order to make it happen?
>> I expect it to be an INFRA JIRA but would be nice to know for sure.
>>
>> Thanks,
>> Roman.
Re: Mailing list noise
Posted by Konstantin Boudnik <co...@apache.org>.
Someone with JIRA admin karma should be able to do the switch in no time. I
think we have plenty of guys like that among the mentors of the project.
Owen, could you redirect BigTop JIRA notification traffic from bigtop-dev@ to
bigtop-commits@ ? Or do we need to go through the official INFRA process for
that?
Thanks,
Cos
On Fri, Sep 09, 2011 at 04:04PM, Roman Shaposhnik wrote:
> On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > The problem with current setup is that most ppl are likely to filter out JIRA
> > traffic to somewhere (like /dev/null), but all these messages will sit in the
> > archive and will simply create difficulties if someone needs to find stuff
> > later on.
>
> A strong +1. Do you know what needs to be done in order to make it happen?
> I expect it to be an INFRA JIRA but would be nice to know for sure.
>
> Thanks,
> Roman.
Re: Mailing list noise
Posted by Roman Shaposhnik <rv...@apache.org>.
On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
> The problem with current setup is that most ppl are likely to filter out JIRA
> traffic to somewhere (like /dev/null), but all these messages will sit in the
> archive and will simply create difficulties if someone needs to find stuff
> later on.
A strong +1. Do you know what needs to be done in order to make it happen?
I expect it to be an INFRA JIRA but would be nice to know for sure.
Thanks,
Roman.