Hey Justin - looks like I'm living in the past on this topic. OK, I
figured out what's going on.
I had a filter for the gitbox messages going into a separate gmail
folder/label. Now that I'm looking at it carefully, all of the content in
there is ancient. SO, it appears when the gitbox
Art, can you clarify the "hint, hint"? Perhaps I missed some context
somewhere. The GitBox emails stopped hitting the dev list over 4 years ago
now. Are you saying that you haven't looked over the dev list in 4 years?
:-)
Justin
On Tue, Mar 7, 2023 at 11:01 AM Arthur Naseef wrote:
> Just saw
Just saw this from a rare look over DEV list messages (hint hint) ;-).
So glad to see this action. Easy-to-Use is top priority, and a dev list
that requires filtering to use - why? Just why?
Art
On Thu, Mar 14, 2019 at 11:40 AM jgenender wrote:
> +1 to github notifications on another list.
+1 to github notifications on another list. It does indeed drown out the
communication here and not everyone can use a filter. I use Nabble, so its
not as easy.
Jeff
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
Awesome... thanks for doing this!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
t; >> > >
> > >> > > and I will check if I can change the existing lists to gitbox, but I
> > >> > > believe I will need infra to help on that.
> > >> > >
> > >> > > On Fri, Feb 22, 2019 at 4:49 PM Clebert Suconic
> >
> On Fri, Feb 22, 2019 at 4:49 PM Clebert Suconic
> >> > > wrote:
> >> > > >
> >> > > > Ok, so far the best choice is git...@activemq.apache.org
> >> > > >
> >> > > >
> >> > > > If an
y partly> > contained in the
>> > > issues@ emails. I dont see a need to end up with two> > non-dev@
>> lists
>> > > for such highly related and very similar volumes of> > content. I
>> dont see
>> > > that anyone interested enough in
ated and very similar volumes of> > content. I dont
> see
> > > that anyone interested enough in our development> > to follow either
> issues@
> > > or dev@ currently should really be looking at> > just one or the
> other of
> > > those mail sets
> > I'd have it all on dev@ personally.
> > I'm not one of those proposing> > otherwise however).> >> > Robbie> >> > On
> > Thu, 21 Feb 2019 at 20:01, michael.andre.pearce> > <
> > michael.andre.pea...@me.com.invalid>
ng as people get notice of the
> specific> > change and time to chipin about it, as im going to filter it
> all back into> > one pot anyway.RobbieOn Thu, 21 Feb 2019 at 17:08,> >
> michael.andre.pearce wrote:>> If
> (+0> > on it moving) we move i would rather it
ate: 22/02/2019 18:53 (GMT+00:00) To:
> > dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on
> > a separate list I'm actually -0 on the move as noted below, which is to say
> > I dontthink we should do it but I'm not objecting to the move generally
l message From: Robbie Gemmell
> Date: 22/02/2019 18:53 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
> separate list I'm actually -0 on the move as noted below, which is to say I
> dontthink we should do it but I'm not
gitbox@ sounds good to me.Sent from my Samsung Galaxy smartphone.
Original message From: Robbie Gemmell
Date: 22/02/2019 18:53 (GMT+00:00) To:
dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
separate list I'm actually -0 on the move as noted
elopment. And actually i quite like having
> > them in the dev, and i actually do follow and pick up on stuff because its
> > there.Thats why im not ecstatic about moving them thus a +0 vote. Sent from
> > my Samsung Galaxy smartphone.
> > > Original mess
---From: Robbie Gemmell <
> robbie.gemm...@gmail.com> Date: 21/02/2019 17:49 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [Discuss] automated github messages
> on a separate list I wouldn't entirely agree there. The issue as described
> is that peoplewant to see general d
> Galaxy smartphone.> Original message ----From: Clebert Suconic
> Date: 21/02/2019 16:05 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
> separate list I made a mistake assuming lazy consensus.. .I did not intend
-From: Robbie Gemmell
Date: 21/02/2019 17:49 (GMT+00:00) To:
dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
separate list I wouldn't entirely agree there. The issue as described is that
peoplewant to see general dev@ discussions separate from issues traffi
Original message From: Robbie Gemmell
> Date: 21/02/2019 17:49 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
> separate list I wouldn't entirely agree there. The issue as described is that
> peoplewant to see general dev@
from my
Samsung Galaxy smartphone.
Original message From: Robbie Gemmell
Date: 21/02/2019 17:49 (GMT+00:00) To:
dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
separate list I wouldn't entirely agree there. The issue as described
hose two lists I'd say> > >
> >>>> that> > > >>>>>>> makes a far better destination, if it isn't to be a
> completely new> > > >>>>>>> list.> > > >>>>>>>> > > >>&g
estination, if it isn't to
be a completely new> > > >>>>>>> list.> > > >>>>>>>> > > >>>>>>> If folks
mostly think using commits@ is great, so be it, but we> > > >>>> should> >
nd between those two lists I'd say
> > > >>>> that
> > > >>>>>>> makes a far better destination, if it isn't to be a completely new
> > > >>>>>>> list.
> > > >>>>>>>
> > &
hold off moving things while we do so.
> > >>> > > >
> > >>> > > > I'm -0 on the overall move as I too think the messages are fine
> > >>> where
> > >>> > > > they are and are easily filterable, but I do admit
> > where
> > > > > > > they are and are easily filterable, but I do admit the same
> > > > > > > applies
> > > > in
> > > > > > > reverse; if we move them I'll typically just filter them back into
> > &
gt;>>>>
> > >>>>>>> If folks mostly think using commits@ is great, so be it, but we
> > >>>> should
> > >>>>>>> actually discuss that. I have posted on the JIRA to ask that Infra
> > >>>> to
>
erse; if we move them I'll typically just filter them back into
> >>> the
> >>> > > > same place they were going originally.
> >>> > > >
> >>> > > > Robbie
> >>> > > >
> >>> > >
gt; Robbie
> > > > > >
> > > > > > On Wed, 20 Feb 2019 at 16:01, Clebert Suconic <
> > > clebert.suco...@gmail.com> wrote:
> > > > > > >
> > > > > > > I'm assuming consensus and I'm asking infra to m
gt; > > On Mon, Feb 18, 2019 at 11:44 AM Clebert Suconic
> > > > > > wrote:
> > > > > > >
> > > > > > > Don’t get me wrong. I can do with filters personally.
> > > > > > >
> > > > > > > I just think this could be more
;>> I'm -0 on the overall move as I too think the messages are fine
> >>>> where
> >>>>>>> they are and are easily filterable, but I do admit the same
> >>>> applies in
> >>>>>>> reverse; if we move them I'll typic
> > >
>>> > > > > I'm assuming consensus and I'm asking infra to move the gitbox
>>> > > > > messages to the commit message.
>>> > > > >
>>> > > > >
>>> > > > > On Mon, Feb 18, 2019 at 11:44
From: Clebert Suconic <
clebert.suco...@gmail.com> Date: 15/02/2019 22:39 (GMT+00:00) To:
dev@activemq.apache.org Subject: Re: [Discuss] automated github
messages on a separate list The thing is. I can do fine with filtering.
So in a way I’m doing thisbased on a feedback of someone el
gt; > Don’t get me wrong. I can do with filters personally.
>> > > > > >
>> > > > > > I just think this could be more friendly for new people joining
>> in. Like Ryan yeats who just posted his opinion (as if someone just
>> joining)
>> > &g
s if someone just
> joining)
> > > > > >
> > > > > > What about this. We could ask Infra to move GitHub messages to
> a new list.
> > > > > >
> > > > > > I already follow GitHub messages on my email directly anyways.
> > &g
> > > > >
> > > > > What about this. We could ask Infra to move GitHub messages to a
> > > > > new list.
> > > > >
> > > > > I already follow GitHub messages on my email directly anyways.
> > > > >
>
subscribe to the new list.
> > > >
> > > > On Sun, Feb 17, 2019 at 9:21 AM michael.andre.pearce
> > > > wrote:
> > > >>
> > > >> I am also +0 on this. I find email filters more than adequate, and
> > > >> av
9:21 AM michael.andre.pearce
> > > wrote:
> > >>
> > >> I am also +0 on this. I find email filters more than adequate, and avoid
> > >> me having to maintain several mail group subscriptions, it will all come
> > >> to one mailbox anyhow.Sent fro
il group subscriptions, it will all come
> >> to one mailbox anyhow.Sent from my Samsung Galaxy smartphone.
> >> ---- Original message ----From: Clebert Suconic
> >> Date: 15/02/2019 22:39 (GMT+00:00) To:
> >> dev@activemq.apache.org Subject: Re: [D
>>
> >> I am also +0 on this. I find email filters more than adequate, and avoid
> >> me having to maintain several mail group subscriptions, it will all come
> >> to one mailbox anyhow.Sent from my Samsung Galaxy smartphone.
> >> ---- Original messa
nt from my Samsung Galaxy smartphone.
>> Original message From: Clebert Suconic
>> Date: 15/02/2019 22:39 (GMT+00:00) To:
>> dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on
>> a separate list The thing is. I can do fine with fil
ptions, it will all come to
> one mailbox anyhow.Sent from my Samsung Galaxy smartphone.
> Original message From: Clebert Suconic <
> clebert.suco...@gmail.com> Date: 15/02/2019 22:39 (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [Discuss] automated github
As someone who just subscribes to the dev list to stay in the loop on upcoming
changes or bugs, I had to recently add a filter to trash all of the messages
coming from GitHub because it was way too much. I would still be interested in
seeing what PR's are opened but the noise from getting
+00:00) To:
dev@activemq.apache.org Subject: Re: [Discuss] automated github messages on a
separate list The thing is. I can do fine with filtering. So in a way I’m
doing thisbased on a feedback of someone else.So I am putting myself in the
shoes of someone coming on board now. Justtrying
The thing is. I can do fine with filtering. So in a way I’m doing this
based on a feedback of someone else.
So I am putting myself in the shoes of someone coming on board now. Just
trying to make it easy for new people.
On Fri, Feb 15, 2019 at 6:58 AM Christopher Shannon <
Hi Clebert,
I agree, I think it would be more "readable" to have gitbox mail on
com...@activemq.apache.org mailing list for instance.
Regards
JB
On 15/02/2019 00:36, Clebert Suconic wrote:
> I work on this dev list on my daily basis. We had some members here
> suggesting doing this in the past
I am +0 on this because either way is fine with me as it's really easy to
do mail filters on either addresses or on subject tags.
There is a ton of Github traffic right now obviously so to make it
manageable I have filters and labels setup on my gmail account so that
GitHub related messages get
People are probably missing this discussion because of that noise.
On Fri, Feb 15, 2019 at 7:47 AM Otavio Piske wrote:
> Sharing my perspective as someone who also would like to contribute more
> often: I think that it be good.
>
> I think that the Github messages create a lot of noise in the
Sharing my perspective as someone who also would like to contribute more
often: I think that it be good.
I think that the Github messages create a lot of noise in the mailbox. It
requires constant cleaning/filtering and it is easy to miss discussions
about subjects that interest me and for which
I work on this dev list on my daily basis. We had some members here
suggesting doing this in the past and we decided to let just people to
filter out stuff with filters. Etc.
But this doesn’t make easy to recruit new open source devs.
I just heard from a guy who only subscribed users list
49 matches
Mail list logo
