Hi Dominik, I think I would prefer option 3. Because then we see on the developer list when there are new issues, and the comments are tracked on the issue@ mailing list.
Cheers, Philipp Von: Dominik Riemer <[email protected]> Datum: Dienstag, 29. November 2022 um 21:31 An: [email protected] <[email protected]> Betreff: Notification scheme for Github issues Hi, before migrating to Github, our notification scheme was configured to send all newly created issues to the dev list and all other notifications to the issues list. This was a tradeoff between having not too many notification mails on the dev list while still allowing everyone on the dev list to see where work is going on. When we started the migration, we changed the asf.yaml settings to send all Github issue notifications to the issues list to avoid an email flood on dev. Which settings do we want to use now? As far as I can see, asf.yaml supports splitting of notifications between comment/status, so there are three options: 1) send all notifications related to issues to the issues list (not my favorite since only few people are subscribed to issues@) 2) send all notifications including issue comments to the dev list 3) send open/close notifications to dev@ and comments to issues@ What do you think? Cheers Dominik [1] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
