You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Florian Micklich <mi...@apache.org> on 2022/12/04 19:43:17 UTC

Re: Notification scheme for Github issues

Hi Dominik and Philipp,

I would prefer option 3 as well.
But if the emails are spitted into different mailing lists, is it guaranteed that I have following structure in my emails to track every related step?

```
New Issue
 |–– discussion
 |–– discussion
 |   |–– discussion
 |...
 |
 |__closed issue
```

Greetings
Florian

Am Mittwoch, dem 30.11.2022 um 13:58 +0000 schrieb Philipp Zehnder:
> Hi Dominik,<br>
> 
> I think I would prefer option 3.<br>
> Because then we see on the developer list when there are new issues, and the comments are tracked on the issue@ mailing list.<br>
> 
> Cheers,<br>
> Philipp<br>
> 
> Von: Dominik Riemer <[dominik.riemer@bytefabrik.ai](mailto:dominik.riemer@bytefabrik.ai)><br>
> Datum: Dienstag, 29. November 2022 um 21:31<br>
> An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)><br>
> Betreff: Notification scheme for Github issues<br>
> Hi,<br>
> 
> 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.<br>
> 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.<br>
> 
> 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.<br>
> 
> Which settings do we want to use now?<br>
> 
> As far as I can see, asf.yaml supports splitting of notifications between comment/status, so there are three options:<br>
> 
> 1) send all notifications related to issues to the issues list (not my favorite since only few people are subscribed to issues@)<br>
> 2) send all notifications including issue comments to the dev list<br>
> 3) send open/close notifications to dev@ and comments to issues@<br>
> 
> What do you think?<br>
> 
> Cheers<br>
> Dominik<br>
> 
> 
> [1] [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features](https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features)<br>
>