I have requested this https://issues.apache.org/jira/browse/INFRA-20419
On Thu, Jun 11, 2020 at 11:37 AM Wes McKinney <[email protected]> wrote: > > jira@ was just created so I think you can go ahead and request the > notification scheme changes. Thanks for doing this > > On Wed, Jun 10, 2020, 11:14 PM Wes McKinney <[email protected]> wrote: >> >> I just requested [email protected] be created >> >> On Wed, Jun 10, 2020, 11:06 PM Neal Richardson <[email protected]> >> wrote: >>> >>> I like it. That has some symmetry with how we handle github notifications: >>> github@ for everything, commits@ for just commits. >>> >>> I looked into creating new mailing lists, and it appears that it's not >>> available to all PMC members, only the PMC chair: >>> https://selfserve.apache.org/mail.html. But once that is done, I'm happy to >>> handle working with INFRA on updating what goes where. >>> >>> Neal >>> >>> >>> On Wed, Jun 10, 2020 at 8:16 PM Wes McKinney <[email protected]> wrote: >>> >>> > Here's my proposal: >>> > >>> > * Create new mailing list [email protected] and move all JIRA >>> > activity to that list (what currently goes to issues@) >>> > * Send new issues notifications to [email protected]. Stop sending >>> > these e-mails to dev@ >>> > * Encourage dev@ subscribers to subscribe to [email protected] >>> > >>> > Absent dissent I would suggest going ahead and asking INFRA to do >>> > this. Note that any PMC member can create the new jira@ mailing list >>> > (do this first, don't ask INFRA to do it) >>> > >>> > On Mon, Jun 8, 2020 at 2:33 PM Wes McKinney <[email protected]> wrote: >>> > > >>> > > I'm openly not very sympathetic toward people who don't take time to >>> > > set up e-mail filters but I support having two e-mail lists: >>> > > >>> > > * One having new issues only. I think that active developers need to >>> > > see new issues to create awareness of what others are doing in the >>> > > project, so I think we should really encourage people to subscribe to >>> > > this list (and set up an e-mail filter if they don't want the e-mails >>> > > coming into their inbox). While I think having less "noise" on dev@ is >>> > > a good thing (even though it's only "noise" if you don't set up e-mail >>> > > filters) I'm concerned that this action will decrease developer >>> > > engagement in the project. There are of course other ways [1] to >>> > > subscribe to the JIRA activity feed if getting notifications in Slack >>> > > or Zulip is your thing. >>> > > * One having all JIRA traffic (i.e. what is currently at >>> > > https://lists.apache.org/[email protected]) >>> > > >>> > > [1]: https://github.com/ursa-labs/jira-zulip-bridge >>> > > >>> > > On Mon, Jun 8, 2020 at 1:57 PM Antoine Pitrou <[email protected]> >>> > wrote: >>> > > > >>> > > > >>> > > > I would welcome a separate list, but only with notifications of new >>> > JIRA >>> > > > issues. I am not interested in generic JIRA traffic. >>> > > > >>> > > > Regards >>> > > > >>> > > > Antoine. >>> > > > >>> > > > >>> > > > Le 08/06/2020 à 20:46, Neal Richardson a écrit : >>> > > > > And if you're like me, and this message got filtered out of your >>> > inbox >>> > > > > because it is from dev@ and contains "JIRA" in the subject, well, >>> > maybe >>> > > > > that demonstrates the problem ;) >>> > > > > >>> > > > > On Mon, Jun 8, 2020 at 11:43 AM Neal Richardson < >>> > [email protected]> >>> > > > > wrote: >>> > > > > >>> > > > >> Hi all, >>> > > > >> I've noticed that some other Apache projects have a separate >>> > mailing list >>> > > > >> for JIRA notifications (Spark, for example, has >>> > [email protected]). >>> > > > >> The result is that the dev@ mailing list is focused on actual >>> > discussions >>> > > > >> threads (like this!), votes, and other official business. Would we >>> > be >>> > > > >> interested in doing the same? >>> > > > >> >>> > > > >> In my opinion, the status quo is not great. The dev@ archives ( >>> > > > >> https://lists.apache.org/[email protected]) aren't >>> > that >>> > > > >> readable/browseable to me, and if I want to see what's going on in >>> > JIRA, I >>> > > > >> go to JIRA. In fact, the first thing I/we recommend to people >>> > signing up >>> > > > >> for the mailing list is to set up email filters to exclude the JIRA >>> > noise. >>> > > > >> Having a separate mailing list will make it easier for people to >>> > manage >>> > > > >> their own informations streams better. >>> > > > >> >>> > > > >> The counterargument is that moving JIRA traffic to a separate >>> > mailing >>> > > > >> list, requiring an additional subscribe action, might mean that >>> > developers >>> > > > >> miss out on things like new issues being created. I'm not >>> > > > >> personally >>> > > > >> worried about this because I suspect that many of us already aren't >>> > using >>> > > > >> the mailing list to stay on top of JIRA issues, and that those who >>> > want the >>> > > > >> JIRA stream in their email can easily opt-in (subscribe). But I'm >>> > > > >> interested in the community's opinions on this. >>> > > > >> >>> > > > >> Thoughts? >>> > > > >> >>> > > > >> Neal >>> > > > >> >>> > > > > >>> >
