[POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
Starting a new thread as the last one sort of dried up and didn’t quite form anything actionable. Being subscribed to many of our mailing-lists and most recently looking into every project, dev-lists when reviewing board reports, I have seen many of our lists literally being rendered useless. Useless, because it’s almost impossible to follow these lists, as a large percentage of the emails are: * Generated emails and the way they are currently generated makes it impossible for email clients to correctly display them as threads. * Contain so much redundant information, that the actual start of the header that I’m interested in reading is usually not readable on mobile phones. * Most discussions have been moved away from the lists (notifications@, commits@), having left over only skeletons in which every now and then a vote is being handled. My proposal is to change the default settings for auto-generated GitHub emails for all projects (not just the new ones) to be a much more condensed version. With these changes, all existing lists, that haven’t manually configured the format of the emails, instantly get readable lists again. Some would argue that there might be projects that could object these changes, but I would on the other hand bet that more projects would be in favor of such a change than not. Those who don’t want a change, can simply go back to the old format, by specifying it in one commit for which we can even provide a default .asf.yaml snippet. Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much information to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter version allows displaying more of the subject on mobile email clients. Here’s an example of a project list before the changes: https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 Here’s an example of the same list after using the other defaults: https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 Here’s an example on how even ponymail is now able to display something happening on GitHub as a discussion you can also follow nicely via email: https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc I would propose to keep the repository as part of the templates, even if since my PR last week was merged it’s now possible to omit that too. I care deeply about our projects, and I would really hate to see our core principles being lost more and more (“If it didn’t happen on the list, it didn’t happen”). You would make me really happy if I could get some general approval by you folks here. Chris
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1 to making this change. It would immediately make our mailing lists more consumable and welcoming to actual humans. Coupled with a page explaining how this works (Oh! Look! There's already one at https://community.apache.org/contributors/mailing-lists.html ) this would be a great service to our communities. On Tue, 2023-08-01 at 12:16 +, Christofer Dutz wrote: > Starting a new thread as the last one sort of dried up and didn’t > quite form anything actionable. > > Being subscribed to many of our mailing-lists and most recently > looking into every project, dev-lists when reviewing board reports, I > have seen many of our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a > large percentage of the emails are: > > * Generated emails and the way they are currently generated makes > it impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of > the header that I’m interested in reading is usually not readable on > mobile phones. > * Most discussions have been moved away from the lists > (notifications@, commits@), having left over only skeletons in which > every now and then a vote is being handled. > > My proposal is to change the default settings for auto-generated > GitHub emails for all projects (not just the new ones) to be a much > more condensed version. > > With these changes, all existing lists, that haven’t manually > configured the format of the emails, instantly get readable lists > again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would > be in favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, > by specifying it in one commit for which we can even provide a > default .asf.yaml snippet. > > Some people expressed the wish to have longer prefixes, such as > “[ISSUE]”, “[PULL-REQUEST]” or “[DISCUSSION]” however do these not > add much information to the email that “[I]”, “[PR]” and “[D]” don’t > and the shorter version allows displaying more of the subject on > mobile email clients. > > Here’s an example of a project list before the changes: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display > something happening on GitHub as a discussion you can also follow > nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even > if since my PR last week was merged it’s now possible to omit that > too. > > I care deeply about our projects, and I would really hate to see our > core principles being lost more and more (“If it didn’t happen on the > list, it didn’t happen”). > > You would make me really happy if I could get some general approval > by you folks here. > > > Chris > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
I can't tell the difference between https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 and https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 They both use "[PR]". What am I missing? Gary On Tue, Aug 1, 2023, 8:17 AM Christofer Dutz wrote: > Starting a new thread as the last one sort of dried up and didn’t quite > form anything actionable. > > Being subscribed to many of our mailing-lists and most recently looking > into every project, dev-lists when reviewing board reports, I have seen > many of our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a large > percentage of the emails are: > > * Generated emails and the way they are currently generated makes it > impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of the > header that I’m interested in reading is usually not readable on mobile > phones. > * Most discussions have been moved away from the lists (notifications@, > commits@), having left over only skeletons in which every now and then a > vote is being handled. > > My proposal is to change the default settings for auto-generated GitHub > emails for all projects (not just the new ones) to be a much more condensed > version. > > With these changes, all existing lists, that haven’t manually configured > the format of the emails, instantly get readable lists again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would be in > favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, by > specifying it in one commit for which we can even provide a default > .asf.yaml snippet. > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much > information to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter > version allows displaying more of the subject on mobile email clients. > > Here’s an example of a project list before the changes: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display something > happening on GitHub as a discussion you can also follow nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even if > since my PR last week was merged it’s now possible to omit that too. > > I care deeply about our projects, and I would really hate to see our core > principles being lost more and more (“If it didn’t happen on the list, it > didn’t happen”). > > You would make me really happy if I could get some general approval by you > folks here. > > > Chris > > >
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
Hi. Le mar. 1 août 2023 à 14:17, Christofer Dutz a écrit : > > Starting a new thread as the last one sort of dried up and didn’t quite form > anything actionable. > > Being subscribed to many of our mailing-lists and most recently looking into > every project, dev-lists when reviewing board reports, I have seen many of > our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a large > percentage of the emails are: > > * Generated emails and the way they are currently generated makes it > impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of the > header that I’m interested in reading is usually not readable on mobile > phones. > * Most discussions have been moved away from the lists (notifications@, > commits@), having left over only skeletons in which every now and then a vote > is being handled. > > My proposal is to change the default settings for auto-generated GitHub > emails for all projects (not just the new ones) to be a much more condensed > version. > > With these changes, all existing lists, that haven’t manually configured the > format of the emails, instantly get readable lists again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would be in > favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, by > specifying it in one commit for which we can even provide a default .asf.yaml > snippet. > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much information > to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter version > allows displaying more of the subject on mobile email clients. > > Here’s an example of a project list before the changes: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display something > happening on GitHub as a discussion you can also follow nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even if > since my PR last week was merged it’s now possible to omit that too. > > I care deeply about our projects, and I would really hate to see our core > principles being lost more and more (“If it didn’t happen on the list, it > didn’t happen”). > > You would make me really happy if I could get some general approval by you > folks here. +1 But it's only part of the issue that MLs (made for human-consumption) are more and more colonized with auto-generated content that is next to useless (if just because there is so much of it). Such "content" keeps piling up. In my case, after having reached the point where I needed to delete-click on at least 10 times more such bot-generated messages than "legitimate" ones, it led to establishing a filter where they would go directly to the trash (with the risk of missing the one important message among the hundreds that should not, IMHO, end up there in the first place). Best regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1 for making this change, it will make the mailinglists a lot more readable for humans. @Gary: For example you have multiple mails around a single PR that are not consolidated into a single thread because the username of who commented is in the subject. Cheers, Hans On 1 Aug 2023 at 15:06 +0200, dev@community.apache.org, wrote: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15
AW: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
Try this: https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-1|dto=2023-1-15: Not sure why it didn’t work … if it doesn’t again, just select the date range on that list from 01.01.2023 to 15.01.2023 Chris Von: Gary Gregory Datum: Dienstag, 1. August 2023 um 14:55 An: dev@community.apache.org Betreff: Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs? I can't tell the difference between https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 and https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 They both use "[PR]". What am I missing? Gary On Tue, Aug 1, 2023, 8:17 AM Christofer Dutz wrote: > Starting a new thread as the last one sort of dried up and didn’t quite > form anything actionable. > > Being subscribed to many of our mailing-lists and most recently looking > into every project, dev-lists when reviewing board reports, I have seen > many of our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a large > percentage of the emails are: > > * Generated emails and the way they are currently generated makes it > impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of the > header that I’m interested in reading is usually not readable on mobile > phones. > * Most discussions have been moved away from the lists (notifications@, > commits@), having left over only skeletons in which every now and then a > vote is being handled. > > My proposal is to change the default settings for auto-generated GitHub > emails for all projects (not just the new ones) to be a much more condensed > version. > > With these changes, all existing lists, that haven’t manually configured > the format of the emails, instantly get readable lists again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would be in > favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, by > specifying it in one commit for which we can even provide a default > .asf.yaml snippet. > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much > information to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter > version allows displaying more of the subject on mobile email clients. > > Here’s an example of a project list before the changes: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display something > happening on GitHub as a discussion you can also follow nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even if > since my PR last week was merged it’s now possible to omit that too. > > I care deeply about our projects, and I would really hate to see our core > principles being lost more and more (“If it didn’t happen on the list, it > didn’t happen”). > > You would make me really happy if I could get some general approval by you > folks here. > > > Chris > > >
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1 @Christofer, thanks for taking care of this. The improvement is undeniable. @Gary, see the date range in the URLs. You might need to manually perform an empty search in those ranges. On Tue, Aug 1, 2023 at 2:16 PM Christofer Dutz wrote: > Starting a new thread as the last one sort of dried up and didn’t quite > form anything actionable. > > Being subscribed to many of our mailing-lists and most recently looking > into every project, dev-lists when reviewing board reports, I have seen > many of our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a large > percentage of the emails are: > > * Generated emails and the way they are currently generated makes it > impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of the > header that I’m interested in reading is usually not readable on mobile > phones. > * Most discussions have been moved away from the lists (notifications@, > commits@), having left over only skeletons in which every now and then a > vote is being handled. > > My proposal is to change the default settings for auto-generated GitHub > emails for all projects (not just the new ones) to be a much more condensed > version. > > With these changes, all existing lists, that haven’t manually configured > the format of the emails, instantly get readable lists again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would be in > favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, by > specifying it in one commit for which we can even provide a default > .asf.yaml snippet. > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much > information to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter > version allows displaying more of the subject on mobile email clients. > > Here’s an example of a project list before the changes: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display something > happening on GitHub as a discussion you can also follow nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even if > since my PR last week was merged it’s now possible to omit that too. > > I care deeply about our projects, and I would really hate to see our core > principles being lost more and more (“If it didn’t happen on the list, it > didn’t happen”). > > You would make me really happy if I could get some general approval by you > folks here. > > > Chris > > >
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
On Tue, Aug 1, 2023 at 3:29 PM Volkan Yazıcı wrote: > @Gary, see the date range in the URLs. > You might need to manually perform an empty search in those ranges. It seems those date ranges in the query string are only taken into account after a refresh. Perhaps on first request, if you have no session on lists.a.o, a session is created and a cookie is set, and the query string is somehow ignored. -- Johan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1, Looks Good!!! -Ayush On Tue, 1 Aug 2023 at 19:08, Johan Corveleyn wrote: > > On Tue, Aug 1, 2023 at 3:29 PM Volkan Yazıcı wrote: > > @Gary, see the date range in the URLs. > > You might need to manually perform an empty search in those ranges. > > It seems those date ranges in the query string are only taken into > account after a refresh. > Perhaps on first request, if you have no session on lists.a.o, a > session is created and a cookie is set, and the query string is > somehow ignored. > > -- > Johan > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
Hi Christofer, As long as projects with their own settings can continue to use them, I'm +1 to change the defaults for all projects. If the projects don't like being able to use their lists again, they can always go back to what they had before. Thanks, Craig > On Aug 1, 2023, at 05:16, Christofer Dutz wrote: > > Starting a new thread as the last one sort of dried up and didn’t quite form > anything actionable. > > Being subscribed to many of our mailing-lists and most recently looking into > every project, dev-lists when reviewing board reports, I have seen many of > our lists literally being rendered useless. > > Useless, because it’s almost impossible to follow these lists, as a large > percentage of the emails are: > > * Generated emails and the way they are currently generated makes it > impossible for email clients to correctly display them as threads. > * Contain so much redundant information, that the actual start of the > header that I’m interested in reading is usually not readable on mobile > phones. > * Most discussions have been moved away from the lists (notifications@, > commits@), having left over only skeletons in which every now and then a vote > is being handled. > > My proposal is to change the default settings for auto-generated GitHub > emails for all projects (not just the new ones) to be a much more condensed > version. > > With these changes, all existing lists, that haven’t manually configured the > format of the emails, instantly get readable lists again. > > Some would argue that there might be projects that could object these > changes, but I would on the other hand bet that more projects would be in > favor of such a change than not. > Those who don’t want a change, can simply go back to the old format, by > specifying it in one commit for which we can even provide a default .asf.yaml > snippet. > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much information > to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter version > allows displaying more of the subject on mobile email clients. > > Here’s an example of a project list before the changes: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > Here’s an example of the same list after using the other defaults: > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > Here’s an example on how even ponymail is now able to display something > happening on GitHub as a discussion you can also follow nicely via email: > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > I would propose to keep the repository as part of the templates, even if > since my PR last week was merged it’s now possible to omit that too. > > I care deeply about our projects, and I would really hate to see our core > principles being lost more and more (“If it didn’t happen on the list, it > didn’t happen”). > > You would make me really happy if I could get some general approval by you > folks here. > > > Chris > > Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1 On Wed, Aug 2, 2023 at 2:15 AM Craig Russell wrote: > > Hi Christofer, > > As long as projects with their own settings can continue to use them, I'm > > +1 > > to change the defaults for all projects. If the projects don't like being > able to use their lists again, they can always go back to what they had > before. > > Thanks, > Craig > > > On Aug 1, 2023, at 05:16, Christofer Dutz wrote: > > > > Starting a new thread as the last one sort of dried up and didn’t quite > > form anything actionable. > > > > Being subscribed to many of our mailing-lists and most recently looking > > into every project, dev-lists when reviewing board reports, I have seen > > many of our lists literally being rendered useless. > > > > Useless, because it’s almost impossible to follow these lists, as a large > > percentage of the emails are: > > > > * Generated emails and the way they are currently generated makes it > > impossible for email clients to correctly display them as threads. > > * Contain so much redundant information, that the actual start of the > > header that I’m interested in reading is usually not readable on mobile > > phones. > > * Most discussions have been moved away from the lists (notifications@, > > commits@), having left over only skeletons in which every now and then a > > vote is being handled. > > > > My proposal is to change the default settings for auto-generated GitHub > > emails for all projects (not just the new ones) to be a much more condensed > > version. > > > > With these changes, all existing lists, that haven’t manually configured > > the format of the emails, instantly get readable lists again. > > > > Some would argue that there might be projects that could object these > > changes, but I would on the other hand bet that more projects would be in > > favor of such a change than not. > > Those who don’t want a change, can simply go back to the old format, by > > specifying it in one commit for which we can even provide a default > > .asf.yaml snippet. > > > > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, > > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much > > information to the email that “[I]”, “[PR]” and “[D]” don’t and the shorter > > version allows displaying more of the subject on mobile email clients. > > > > Here’s an example of a project list before the changes: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 > > Here’s an example of the same list after using the other defaults: > > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 > > > > Here’s an example on how even ponymail is now able to display something > > happening on GitHub as a discussion you can also follow nicely via email: > > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc > > > > I would propose to keep the repository as part of the templates, even if > > since my PR last week was merged it’s now possible to omit that too. > > > > I care deeply about our projects, and I would really hate to see our core > > principles being lost more and more (“If it didn’t happen on the list, it > > didn’t happen”). > > > > You would make me really happy if I could get some general approval by you > > folks here. > > > > > > Chris > > > > > > Craig L Russell > c...@apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
+1 Am 2. August 2023 07:47:25 MESZ schrieb Jarek Potiuk : >+1 > >On Wed, Aug 2, 2023 at 2:15 AM Craig Russell wrote: >> >> Hi Christofer, >> >> As long as projects with their own settings can continue to use them, I'm >> >> +1 >> >> to change the defaults for all projects. If the projects don't like being >> able to use their lists again, they can always go back to what they had >> before. >> >> Thanks, >> Craig >> >> > On Aug 1, 2023, at 05:16, Christofer Dutz >> > wrote: >> > >> > Starting a new thread as the last one sort of dried up and didn’t quite >> > form anything actionable. >> > >> > Being subscribed to many of our mailing-lists and most recently looking >> > into every project, dev-lists when reviewing board reports, I have seen >> > many of our lists literally being rendered useless. >> > >> > Useless, because it’s almost impossible to follow these lists, as a large >> > percentage of the emails are: >> > >> > * Generated emails and the way they are currently generated makes it >> > impossible for email clients to correctly display them as threads. >> > * Contain so much redundant information, that the actual start of the >> > header that I’m interested in reading is usually not readable on mobile >> > phones. >> > * Most discussions have been moved away from the lists (notifications@, >> > commits@), having left over only skeletons in which every now and then a >> > vote is being handled. >> > >> > My proposal is to change the default settings for auto-generated GitHub >> > emails for all projects (not just the new ones) to be a much more >> > condensed version. >> > >> > With these changes, all existing lists, that haven’t manually configured >> > the format of the emails, instantly get readable lists again. >> > >> > Some would argue that there might be projects that could object these >> > changes, but I would on the other hand bet that more projects would be in >> > favor of such a change than not. >> > Those who don’t want a change, can simply go back to the old format, by >> > specifying it in one commit for which we can even provide a default >> > .asf.yaml snippet. >> > >> > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, >> > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much >> > information to the email that “[I]”, “[PR]” and “[D]” don’t and the >> > shorter version allows displaying more of the subject on mobile email >> > clients. >> > >> > Here’s an example of a project list before the changes: >> > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 >> > Here’s an example of the same list after using the other defaults: >> > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 >> > >> > Here’s an example on how even ponymail is now able to display something >> > happening on GitHub as a discussion you can also follow nicely via email: >> > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc >> > >> > I would propose to keep the repository as part of the templates, even if >> > since my PR last week was merged it’s now possible to omit that too. >> > >> > I care deeply about our projects, and I would really hate to see our core >> > principles being lost more and more (“If it didn’t happen on the list, it >> > didn’t happen”). >> > >> > You would make me really happy if I could get some general approval by you >> > folks here. >> > >> > >> > Chris >> > >> > >> >> Craig L Russell >> c...@apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > >- >To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >For additional commands, e-mail: dev-h...@community.apache.org >
AW: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?
Well, stating the obvious, I’ll add my +1 ;-) And yes Craig, I said the defaults … if you have explicitly configured your .asf.yaml subjects, they are left unchanged. Chris Von: Richard Zowalla Datum: Mittwoch, 2. August 2023 um 08:10 An: dev@community.apache.org Betreff: Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs? +1 Am 2. August 2023 07:47:25 MESZ schrieb Jarek Potiuk : >+1 > >On Wed, Aug 2, 2023 at 2:15 AM Craig Russell wrote: >> >> Hi Christofer, >> >> As long as projects with their own settings can continue to use them, I'm >> >> +1 >> >> to change the defaults for all projects. If the projects don't like being >> able to use their lists again, they can always go back to what they had >> before. >> >> Thanks, >> Craig >> >> > On Aug 1, 2023, at 05:16, Christofer Dutz >> > wrote: >> > >> > Starting a new thread as the last one sort of dried up and didn’t quite >> > form anything actionable. >> > >> > Being subscribed to many of our mailing-lists and most recently looking >> > into every project, dev-lists when reviewing board reports, I have seen >> > many of our lists literally being rendered useless. >> > >> > Useless, because it’s almost impossible to follow these lists, as a large >> > percentage of the emails are: >> > >> > * Generated emails and the way they are currently generated makes it >> > impossible for email clients to correctly display them as threads. >> > * Contain so much redundant information, that the actual start of the >> > header that I’m interested in reading is usually not readable on mobile >> > phones. >> > * Most discussions have been moved away from the lists (notifications@, >> > commits@), having left over only skeletons in which every now and then a >> > vote is being handled. >> > >> > My proposal is to change the default settings for auto-generated GitHub >> > emails for all projects (not just the new ones) to be a much more >> > condensed version. >> > >> > With these changes, all existing lists, that haven’t manually configured >> > the format of the emails, instantly get readable lists again. >> > >> > Some would argue that there might be projects that could object these >> > changes, but I would on the other hand bet that more projects would be in >> > favor of such a change than not. >> > Those who don’t want a change, can simply go back to the old format, by >> > specifying it in one commit for which we can even provide a default >> > .asf.yaml snippet. >> > >> > Some people expressed the wish to have longer prefixes, such as “[ISSUE]”, >> > “[PULL-REQUEST]” or “[DISCUSSION]” however do these not add much >> > information to the email that “[I]”, “[PR]” and “[D]” don’t and the >> > shorter version allows displaying more of the subject on mobile email >> > clients. >> > >> > Here’s an example of a project list before the changes: >> > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-1-9|dto=2023-1-15 >> > Here’s an example of the same list after using the other defaults: >> > https://lists.apache.org/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18 >> > >> > Here’s an example on how even ponymail is now able to display something >> > happening on GitHub as a discussion you can also follow nicely via email: >> > https://lists.apache.org/thread/rnr9tjx9rsnqc7b5nwcf68qnp5bkr9hc >> > >> > I would propose to keep the repository as part of the templates, even if >> > since my PR last week was merged it’s now possible to omit that too. >> > >> > I care deeply about our projects, and I would really hate to see our core >> > principles being lost more and more (“If it didn’t happen on the list, it >> > didn’t happen”). >> > >> > You would make me really happy if I could get some general approval by you >> > folks here. >> > >> > >> > Chris >> > >> > >> >> Craig L Russell >> c...@apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > >- >To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >For additional commands, e-mail: dev-h...@community.apache.org >
