You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Christofer Dutz <ch...@c-ware.de> on 2023/01/21 17:37:40 UTC
Updating the notification schema for GitHub?
Hi all,
GitHub emails have been annoying in this project for quite some time, with the increased usage of discussions, this has become worse.
This is not something unique to StreamPipes, but also happens in other projects.
I did manage to convince Infra to update their notification bot to customize the email subjects of auto-generated emails.
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
I have updated the settings in PLC4X and now both my email-client as also lists.apache.org can correctly thread the emails.
Perhaps something worth discussing on changing here too?
https://github.com/apache/plc4x/blob/develop/.asf.yaml
What do you folks think?
Chris
Re: AW: Updating the notification schema for GitHub?
Posted by Christofer Dutz <ch...@c-ware.de>.
Yeah … looks a lot better this way … now all I gotta do is motivate infra to add support for the discussions too :-)
Chris
From: Dominik Riemer <do...@bytefabrik.ai>
Date: Thursday, 26. January 2023 at 09:13
To: dev@streampipes.apache.org <de...@streampipes.apache.org>
Subject: RE: AW: Updating the notification schema for GitHub?
Hi,
I've updated the asf.yaml according to the PLC4X scheme.
You can find the PR here:
https://github.com/apache/streampipes/pull/1163
Cheers
Dominik
-----Original Message-----
From: Tim <bo...@posteo.de>
Sent: Wednesday, January 25, 2023 5:59 PM
To: dev@streampipes.apache.org
Subject: Re: AW: Updating the notification schema for GitHub?
Hi all,
I'm also in favor of applying the notification schema that PLC4x uses.
Let's try that out and see how this improves our notification mess.
+1 for Philipp's idea to name PRs consistently, but I'd handle this in a
seperate discussion.
Best
Tim
Am 23.01.2023 17:06 schrieb Philipp Zehnder:
> Hi,
>
> I like the changes Chris suggested. This week we have a community call
> (see [1]).
> There we will talk about the change from JIRA to GitHub. I suggest
> talking about this as well and then changing the configurations
> accordingly.
> Maybe we can also talk about a convention to set the name for PRs.
>
> Cheers,
> Philipp
>
> Von: Christofer Dutz <ch...@c-ware.de>
> Datum: Montag, 23. Januar 2023 um 11:45
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Re: Updating the notification schema for GitHub?
> Well, a PR is a PR and an Issue is an Issue …
>
> If there’s an issue related to a PR … well that’s one thing we can’t
> automate … there will be two email threads.
> But everything is better than the way it currently is … for me without
> any changes this list is unusable.
>
> Chris
>
>
>
> From: Dominik Riemer <do...@bytefabrik.ai>
> Date: Monday, 23. January 2023 at 09:51
> To: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Subject: RE: Updating the notification schema for GitHub?
> Hi Chris,
>
> thanks for the hint, that's a very useful new feature!
>
> So we could add the same configuration as PLC4X:
>
> # Attempt to make the auto-generated github emails more easily
> readable in email clients.
> custom_subjects:
> new_pr: "[PR] {title} ({repository})"
> close_pr: "Re: [PR] {title} ({repository})"
> comment_pr: "Re: [PR] {title} ({repository})"
> diffcomment: "Re: [PR] {title} ({repository})"
> merge_pr: "Re: [PR] {title} ({repository})"
> new_issue: "[I] {title} ({repository})"
> comment_issue: "Re: [I] {title} ({repository})"
> close_issue: "Re: [I] {title} ({repository})"
> catchall: "[GH] {title} ({repository})"
>
> Do we need to pay attention that the PR titles match the related issue
> titles with this config?
>
> What do others think?
>
> Best,
> Dominik
>
>
> -----Original Message-----
> From: Christofer Dutz <ch...@c-ware.de>
> Sent: Saturday, January 21, 2023 6:38 PM
> To: dev@streampipes.apache.org
> Subject: Updating the notification schema for GitHub?
>
> Hi all,
>
> GitHub emails have been annoying in this project for quite some time,
> with the increased usage of discussions, this has become worse.
> This is not something unique to StreamPipes, but also happens in other
> projects.
>
> I did manage to convince Infra to update their notification bot to
> customize the email subjects of auto-generated emails.
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
>
> I have updated the settings in PLC4X and now both my email-client as
> also lists.apache.org can correctly thread the emails.
>
> Perhaps something worth discussing on changing here too?
>
> https://github.com/apache/plc4x/blob/develop/.asf.yaml
>
> What do you folks think?
>
>
> Chris
RE: AW: Updating the notification schema for GitHub?
Posted by Dominik Riemer <do...@bytefabrik.ai>.
Hi,
I've updated the asf.yaml according to the PLC4X scheme.
You can find the PR here:
https://github.com/apache/streampipes/pull/1163
Cheers
Dominik
-----Original Message-----
From: Tim <bo...@posteo.de>
Sent: Wednesday, January 25, 2023 5:59 PM
To: dev@streampipes.apache.org
Subject: Re: AW: Updating the notification schema for GitHub?
Hi all,
I'm also in favor of applying the notification schema that PLC4x uses.
Let's try that out and see how this improves our notification mess.
+1 for Philipp's idea to name PRs consistently, but I'd handle this in a
seperate discussion.
Best
Tim
Am 23.01.2023 17:06 schrieb Philipp Zehnder:
> Hi,
>
> I like the changes Chris suggested. This week we have a community call
> (see [1]).
> There we will talk about the change from JIRA to GitHub. I suggest
> talking about this as well and then changing the configurations
> accordingly.
> Maybe we can also talk about a convention to set the name for PRs.
>
> Cheers,
> Philipp
>
> Von: Christofer Dutz <ch...@c-ware.de>
> Datum: Montag, 23. Januar 2023 um 11:45
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Re: Updating the notification schema for GitHub?
> Well, a PR is a PR and an Issue is an Issue …
>
> If there’s an issue related to a PR … well that’s one thing we can’t
> automate … there will be two email threads.
> But everything is better than the way it currently is … for me without
> any changes this list is unusable.
>
> Chris
>
>
>
> From: Dominik Riemer <do...@bytefabrik.ai>
> Date: Monday, 23. January 2023 at 09:51
> To: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Subject: RE: Updating the notification schema for GitHub?
> Hi Chris,
>
> thanks for the hint, that's a very useful new feature!
>
> So we could add the same configuration as PLC4X:
>
> # Attempt to make the auto-generated github emails more easily
> readable in email clients.
> custom_subjects:
> new_pr: "[PR] {title} ({repository})"
> close_pr: "Re: [PR] {title} ({repository})"
> comment_pr: "Re: [PR] {title} ({repository})"
> diffcomment: "Re: [PR] {title} ({repository})"
> merge_pr: "Re: [PR] {title} ({repository})"
> new_issue: "[I] {title} ({repository})"
> comment_issue: "Re: [I] {title} ({repository})"
> close_issue: "Re: [I] {title} ({repository})"
> catchall: "[GH] {title} ({repository})"
>
> Do we need to pay attention that the PR titles match the related issue
> titles with this config?
>
> What do others think?
>
> Best,
> Dominik
>
>
> -----Original Message-----
> From: Christofer Dutz <ch...@c-ware.de>
> Sent: Saturday, January 21, 2023 6:38 PM
> To: dev@streampipes.apache.org
> Subject: Updating the notification schema for GitHub?
>
> Hi all,
>
> GitHub emails have been annoying in this project for quite some time,
> with the increased usage of discussions, this has become worse.
> This is not something unique to StreamPipes, but also happens in other
> projects.
>
> I did manage to convince Infra to update their notification bot to
> customize the email subjects of auto-generated emails.
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
>
> I have updated the settings in PLC4X and now both my email-client as
> also lists.apache.org can correctly thread the emails.
>
> Perhaps something worth discussing on changing here too?
>
> https://github.com/apache/plc4x/blob/develop/.asf.yaml
>
> What do you folks think?
>
>
> Chris
Re: AW: Updating the notification schema for GitHub?
Posted by Tim <bo...@posteo.de>.
Hi all,
I'm also in favor of applying the notification schema that PLC4x uses.
Let's try that out and see how this improves our notification mess.
+1 for Philipp's idea to name PRs consistently, but I'd handle this in a
seperate discussion.
Best
Tim
Am 23.01.2023 17:06 schrieb Philipp Zehnder:
> Hi,
>
> I like the changes Chris suggested. This week we have a community call
> (see [1]).
> There we will talk about the change from JIRA to GitHub. I suggest
> talking about this as well and then changing the configurations
> accordingly.
> Maybe we can also talk about a convention to set the name for PRs.
>
> Cheers,
> Philipp
>
> Von: Christofer Dutz <ch...@c-ware.de>
> Datum: Montag, 23. Januar 2023 um 11:45
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Re: Updating the notification schema for GitHub?
> Well, a PR is a PR and an Issue is an Issue …
>
> If there’s an issue related to a PR … well that’s one thing we can’t
> automate … there will be two email threads.
> But everything is better than the way it currently is … for me without
> any changes this list is unusable.
>
> Chris
>
>
>
> From: Dominik Riemer <do...@bytefabrik.ai>
> Date: Monday, 23. January 2023 at 09:51
> To: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Subject: RE: Updating the notification schema for GitHub?
> Hi Chris,
>
> thanks for the hint, that's a very useful new feature!
>
> So we could add the same configuration as PLC4X:
>
> # Attempt to make the auto-generated github emails more easily
> readable in email clients.
> custom_subjects:
> new_pr: "[PR] {title} ({repository})"
> close_pr: "Re: [PR] {title} ({repository})"
> comment_pr: "Re: [PR] {title} ({repository})"
> diffcomment: "Re: [PR] {title} ({repository})"
> merge_pr: "Re: [PR] {title} ({repository})"
> new_issue: "[I] {title} ({repository})"
> comment_issue: "Re: [I] {title} ({repository})"
> close_issue: "Re: [I] {title} ({repository})"
> catchall: "[GH] {title} ({repository})"
>
> Do we need to pay attention that the PR titles match the related issue
> titles with this config?
>
> What do others think?
>
> Best,
> Dominik
>
>
> -----Original Message-----
> From: Christofer Dutz <ch...@c-ware.de>
> Sent: Saturday, January 21, 2023 6:38 PM
> To: dev@streampipes.apache.org
> Subject: Updating the notification schema for GitHub?
>
> Hi all,
>
> GitHub emails have been annoying in this project for quite some time,
> with the increased usage of discussions, this has become worse.
> This is not something unique to StreamPipes, but also happens in other
> projects.
>
> I did manage to convince Infra to update their notification bot to
> customize the email subjects of auto-generated emails.
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
>
> I have updated the settings in PLC4X and now both my email-client as
> also lists.apache.org can correctly thread the emails.
>
> Perhaps something worth discussing on changing here too?
>
> https://github.com/apache/plc4x/blob/develop/.asf.yaml
>
> What do you folks think?
>
>
> Chris
AW: Updating the notification schema for GitHub?
Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
Hi,
I like the changes Chris suggested. This week we have a community call (see [1]).
There we will talk about the change from JIRA to GitHub. I suggest talking about this as well and then changing the configurations accordingly.
Maybe we can also talk about a convention to set the name for PRs.
Cheers,
Philipp
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Montag, 23. Januar 2023 um 11:45
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: Re: Updating the notification schema for GitHub?
Well, a PR is a PR and an Issue is an Issue …
If there’s an issue related to a PR … well that’s one thing we can’t automate … there will be two email threads.
But everything is better than the way it currently is … for me without any changes this list is unusable.
Chris
From: Dominik Riemer <do...@bytefabrik.ai>
Date: Monday, 23. January 2023 at 09:51
To: dev@streampipes.apache.org <de...@streampipes.apache.org>
Subject: RE: Updating the notification schema for GitHub?
Hi Chris,
thanks for the hint, that's a very useful new feature!
So we could add the same configuration as PLC4X:
# Attempt to make the auto-generated github emails more easily readable in email clients.
custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
Do we need to pay attention that the PR titles match the related issue titles with this config?
What do others think?
Best,
Dominik
-----Original Message-----
From: Christofer Dutz <ch...@c-ware.de>
Sent: Saturday, January 21, 2023 6:38 PM
To: dev@streampipes.apache.org
Subject: Updating the notification schema for GitHub?
Hi all,
GitHub emails have been annoying in this project for quite some time, with the increased usage of discussions, this has become worse.
This is not something unique to StreamPipes, but also happens in other projects.
I did manage to convince Infra to update their notification bot to customize the email subjects of auto-generated emails.
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
I have updated the settings in PLC4X and now both my email-client as also lists.apache.org can correctly thread the emails.
Perhaps something worth discussing on changing here too?
https://github.com/apache/plc4x/blob/develop/.asf.yaml
What do you folks think?
Chris
Re: Updating the notification schema for GitHub?
Posted by Christofer Dutz <ch...@c-ware.de>.
Well, a PR is a PR and an Issue is an Issue …
If there’s an issue related to a PR … well that’s one thing we can’t automate … there will be two email threads.
But everything is better than the way it currently is … for me without any changes this list is unusable.
Chris
From: Dominik Riemer <do...@bytefabrik.ai>
Date: Monday, 23. January 2023 at 09:51
To: dev@streampipes.apache.org <de...@streampipes.apache.org>
Subject: RE: Updating the notification schema for GitHub?
Hi Chris,
thanks for the hint, that's a very useful new feature!
So we could add the same configuration as PLC4X:
# Attempt to make the auto-generated github emails more easily readable in email clients.
custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
Do we need to pay attention that the PR titles match the related issue titles with this config?
What do others think?
Best,
Dominik
-----Original Message-----
From: Christofer Dutz <ch...@c-ware.de>
Sent: Saturday, January 21, 2023 6:38 PM
To: dev@streampipes.apache.org
Subject: Updating the notification schema for GitHub?
Hi all,
GitHub emails have been annoying in this project for quite some time, with the increased usage of discussions, this has become worse.
This is not something unique to StreamPipes, but also happens in other projects.
I did manage to convince Infra to update their notification bot to customize the email subjects of auto-generated emails.
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
I have updated the settings in PLC4X and now both my email-client as also lists.apache.org can correctly thread the emails.
Perhaps something worth discussing on changing here too?
https://github.com/apache/plc4x/blob/develop/.asf.yaml
What do you folks think?
Chris
RE: Updating the notification schema for GitHub?
Posted by Dominik Riemer <do...@bytefabrik.ai>.
Hi Chris,
thanks for the hint, that's a very useful new feature!
So we could add the same configuration as PLC4X:
# Attempt to make the auto-generated github emails more easily readable in email clients.
custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
Do we need to pay attention that the PR titles match the related issue titles with this config?
What do others think?
Best,
Dominik
-----Original Message-----
From: Christofer Dutz <ch...@c-ware.de>
Sent: Saturday, January 21, 2023 6:38 PM
To: dev@streampipes.apache.org
Subject: Updating the notification schema for GitHub?
Hi all,
GitHub emails have been annoying in this project for quite some time, with the increased usage of discussions, this has become worse.
This is not something unique to StreamPipes, but also happens in other projects.
I did manage to convince Infra to update their notification bot to customize the email subjects of auto-generated emails.
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
I have updated the settings in PLC4X and now both my email-client as also lists.apache.org can correctly thread the emails.
Perhaps something worth discussing on changing here too?
https://github.com/apache/plc4x/blob/develop/.asf.yaml
What do you folks think?
Chris