You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Mark Struberg <st...@yahoo.de.INVALID> on 2018/04/25 20:14:53 UTC
please disable GitBox spamming to dev@
GitBox should imo get directed to committs@cxf.a.o
Would make it much easier to see what's going on.
txs and LieGrue,
strub
Re: please disable GitBox spamming to dev@
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
I talked with Greg and he pointed me to a discussion they had over at dubbo (incubating)
https://lists.apache.org/thread.html/70d41e2208fc3bc69ba0297aeb08a1a4f48db987f15ca041241007a4@%3Cdev.dubbo.apache.org%3E
May be of interest for some.
txs and LieGrue,
strub
> Am 26.04.2018 um 07:13 schrieb Mark Struberg <st...@yahoo.de.INVALID>:
>
> I see your point.
> But right now it's really very hard to follow any discussions because the gitbox bot spams the list like crazy.
>
> I know it's not only a CXF problem, but there is one more thing which I noticed in projects which co-went to github.
> Previously we had mailing list + Jira.
>
> But with gitbox integration all the information is all over the place
> mailing list + jira + PRs + github tickets + other github repos + +
> That makes it really hard to read up.
>
> Again: not a CXF issue, we need to tackle this on a general infra level.
>
> LieGrue,
> strub
>
>
>> Am 26.04.2018 um 00:21 schrieb Daniel Kulp <dk...@apache.org>:
>>
>>
>> We have a notifications@ list, but that is for build notification (Jenkins) which is very different than discussions on PR’s.
>>
>> If GitBox would allow the Open/Close to go to commits@ and the comments to remain on dev@, I could be open to that idea.
>>
>> Dan
>>
>>
>>
>>> On Apr 25, 2018, at 4:56 PM, John D. Ament <jo...@apache.org> wrote:
>>>
>>> Lots of projects have been struggling with this. Many podlings have been
>>> creating notifications@ to reduce the dev list clutter. Those interested
>>> can subscribe there.
>>>
>>> On Wed, Apr 25, 2018, 4:51 PM Daniel Kulp <dk...@apache.org> wrote:
>>>
>>>>
>>>> I disagree…. Comments on PR’s should go to dev so the developers can see
>>>> what is happening with the discussions.
>>>>
>>>> Dan
>>>>
>>>>
>>>>
>>>>> On Apr 25, 2018, at 4:14 PM, Mark Struberg <st...@yahoo.de.INVALID>
>>>> wrote:
>>>>>
>>>>> GitBox should imo get directed to committs@cxf.a.o
>>>>>
>>>>> Would make it much easier to see what's going on.
>>>>>
>>>>> txs and LieGrue,
>>>>> strub
>>>>
>>>> --
>>>> Daniel Kulp
>>>> dkulp@apache.org - http://dankulp.com/blog
>>>> Talend Community Coder - http://coders.talend.com
>>>>
>>>>
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>
Re: please disable GitBox spamming to dev@
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
I see your point.
But right now it's really very hard to follow any discussions because the gitbox bot spams the list like crazy.
I know it's not only a CXF problem, but there is one more thing which I noticed in projects which co-went to github.
Previously we had mailing list + Jira.
But with gitbox integration all the information is all over the place
mailing list + jira + PRs + github tickets + other github repos + +
That makes it really hard to read up.
Again: not a CXF issue, we need to tackle this on a general infra level.
LieGrue,
strub
> Am 26.04.2018 um 00:21 schrieb Daniel Kulp <dk...@apache.org>:
>
>
> We have a notifications@ list, but that is for build notification (Jenkins) which is very different than discussions on PR’s.
>
> If GitBox would allow the Open/Close to go to commits@ and the comments to remain on dev@, I could be open to that idea.
>
> Dan
>
>
>
>> On Apr 25, 2018, at 4:56 PM, John D. Ament <jo...@apache.org> wrote:
>>
>> Lots of projects have been struggling with this. Many podlings have been
>> creating notifications@ to reduce the dev list clutter. Those interested
>> can subscribe there.
>>
>> On Wed, Apr 25, 2018, 4:51 PM Daniel Kulp <dk...@apache.org> wrote:
>>
>>>
>>> I disagree…. Comments on PR’s should go to dev so the developers can see
>>> what is happening with the discussions.
>>>
>>> Dan
>>>
>>>
>>>
>>>> On Apr 25, 2018, at 4:14 PM, Mark Struberg <st...@yahoo.de.INVALID>
>>> wrote:
>>>>
>>>> GitBox should imo get directed to committs@cxf.a.o
>>>>
>>>> Would make it much easier to see what's going on.
>>>>
>>>> txs and LieGrue,
>>>> strub
>>>
>>> --
>>> Daniel Kulp
>>> dkulp@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>>
>>>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
Re: please disable GitBox spamming to dev@
Posted by Daniel Kulp <dk...@apache.org>.
We have a notifications@ list, but that is for build notification (Jenkins) which is very different than discussions on PR’s.
If GitBox would allow the Open/Close to go to commits@ and the comments to remain on dev@, I could be open to that idea.
Dan
> On Apr 25, 2018, at 4:56 PM, John D. Ament <jo...@apache.org> wrote:
>
> Lots of projects have been struggling with this. Many podlings have been
> creating notifications@ to reduce the dev list clutter. Those interested
> can subscribe there.
>
> On Wed, Apr 25, 2018, 4:51 PM Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> I disagree…. Comments on PR’s should go to dev so the developers can see
>> what is happening with the discussions.
>>
>> Dan
>>
>>
>>
>>> On Apr 25, 2018, at 4:14 PM, Mark Struberg <st...@yahoo.de.INVALID>
>> wrote:
>>>
>>> GitBox should imo get directed to committs@cxf.a.o
>>>
>>> Would make it much easier to see what's going on.
>>>
>>> txs and LieGrue,
>>> strub
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: please disable GitBox spamming to dev@
Posted by "John D. Ament" <jo...@apache.org>.
Lots of projects have been struggling with this. Many podlings have been
creating notifications@ to reduce the dev list clutter. Those interested
can subscribe there.
On Wed, Apr 25, 2018, 4:51 PM Daniel Kulp <dk...@apache.org> wrote:
>
> I disagree…. Comments on PR’s should go to dev so the developers can see
> what is happening with the discussions.
>
> Dan
>
>
>
> > On Apr 25, 2018, at 4:14 PM, Mark Struberg <st...@yahoo.de.INVALID>
> wrote:
> >
> > GitBox should imo get directed to committs@cxf.a.o
> >
> > Would make it much easier to see what's going on.
> >
> > txs and LieGrue,
> > strub
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: please disable GitBox spamming to dev@
Posted by Daniel Kulp <dk...@apache.org>.
I disagree…. Comments on PR’s should go to dev so the developers can see what is happening with the discussions.
Dan
> On Apr 25, 2018, at 4:14 PM, Mark Struberg <st...@yahoo.de.INVALID> wrote:
>
> GitBox should imo get directed to committs@cxf.a.o
>
> Would make it much easier to see what's going on.
>
> txs and LieGrue,
> strub
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com