I fully agree, Scott.
We should also not forget users using mailing list archives. It would be
a nightmare to follow dev@ discussions on ponymail with all these Jira
notifications.
I see no evidence that we attract more new contributors through Jira
notifications, I assume the contrary.
The problem is that jira notification volume far exceeds dev list volume
which has the effect of stifling dev list discussions due to them being
pushed far down the list of recent emails. The only solution to that is to
filter the jira notifications. Right now in gmail I can see one week's
worth
We can not prevent those not interested in what is happening to
unsubscribe. And with modern mail clients (or online solutions) anyone not
interested to see posting about specific categories (commits, JIRA
notifications) can set filters there to:
1. have the postings of these categories
I used to have a filter on "(OFBIZ-" to redirect to my OFBiz Jira folder.
Having a specific list is easier indeed.
Jacques
Le 25/04/2019 à 13:39, Swapnil M Mane a écrit :
I am also inline with Michael's comments.
- Best Regards,
Swapnil M Mane,
ofbiz.apache.org
On Thu, Apr 25, 2019 at
I am also inline with Michael's comments.
- Best Regards,
Swapnil M Mane,
ofbiz.apache.org
On Thu, Apr 25, 2019 at 4:48 PM Michael Brohl
wrote:
> I strongly suggest to stay with the split between notifications@ and dev@.
>
> It makes the dev@ discussions a lot better to follow, these would
I strongly suggest to stay with the split between notifications@ and dev@.
It makes the dev@ discussions a lot better to follow, these would drown
in the Jira notifications. I suspect that we would make users
unsubscribe dev@ if we would have notifications@ in there also.
If people are
