Re: [Discuss] Split the dev@ mailing list?

[Andy Seaborne <an...@apache.org>]

Ok, we can see how it goes.

I'll kick off the VOTE for the minimal proposal in a moment.

     Andy

On 13/12/2019 15:32, ajs6f wrote:
> I'm +1 to splitting off pr@, -0 to splitting off issues@. I don't see that the gain is worth creating another list, managing more subscriptions, missing replies when they go to the wrong list, etc., but if other folks would like to try it, I'm not -1 against it.
> 
> ajs6f
> 
>> On Dec 13, 2019, at 10:07 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>> Adam - where are we on this?
>>
>> My understanding is that the difference in the discussion is around how JIRA is handled after we direct all GH traffic to pr@.
>>
>> Either we leave JIRA emails coming to dev@ or we direct them to a new issues@.
>>
>> Even with GH not causing additional JIRA ticket entries, the dev@ list may still be a bit busy. JIRA has it's own level of additional emails.
>>
>> The sender is "jira@apache.org"; reply-to: is "dev@".
>>
>> How "reply" works is different for different email clients:
>>
>> GMail:
>>
>> I only get the option of replying to the dev@list and that will not get put back on the ticket.
>>
>> Thunderbird:
>>
>> I get "reply" which goes to "jira@apache.org" and will update the ticket, and "reply list" to "dev@".
>>
>> What are you hoping for by having JIRA emails go to dev@
>>
>>
>> I've just setup a personal JIRA filter subscription and now get a list of new tickets from the past 24 hours, sent to me once a day. I use this from JIRA cloud - I wanted to make sure it works for the Apache installation. The "watching" controls also work so a person can track specific tickets.
>>
>>     Andy
>>
>> On 10/12/2019 08:44, Andy Seaborne wrote:
>>> On 09/12/2019 20:51, Andy Seaborne wrote:
>>>>
>>>>
>>>> On 09/12/2019 16:26, ajs6f wrote:
>>>>> I'm not sure why I would want to use a clunky and less-functional (no reply-to to comment on PR, non-formatting-aware) email list instead of the more powerful_and_  more pleasant GH system.
>>>>
>>>> No one is asking you to.
>>>> It is not either-or.
>>>>
>>>> GH tools remain untouched as they are today.
>>>>   >> PR discussion is done on GH
>>>>
>>>>   > any comment on a PR creates at least three email messages in my inbox,
>>>>
>>>> One of the copies, the useful message, you get is direct from GH, not via ASF (assuming you have GH notifications on)
>>>>
>>>>> 1. Turn off auto-mirroring of all PR comments (which now starts once a ticket is mentioned) from GH to Jira.
>>>>
>>>> Yes
>>>>   >> all PR traffic to pr@
>>>>
>>>>   >2. Put PR comments on a separate pr@ list to record them.
>>>>
>>>> Yes
>>>>   >> all PR [email] traffic to pr@
>>>>
>>>>
>>>> The only difference here is whether JIRA goes to issues@.
>>>> Anyone can combine their email into one folder (as they can separate it today). The difference is really on the archives.
>>> missing the other big benefit - the dev@ is more approachable for people dropping in and showing an interest.
>>>>
>>>> The one thing we still JIRA for because there isn't "issues" on GH
>>>> (and they are weak as a long term record IMO).
>>>>
>>>>       Andy
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>