Big +1 on that one. There were cases in the past that some "breaking" changes in GitHub integration were introduced already for various reasons. Given some warnings and explanations why we are doing it (basically to better fulfill our mission) it's a change that is pretty easily actionable for the PMCs and individuals who subscribe to those messages (Mostly it's reconfiguring bots and mailing filtering rules that one would set up to filter the messages).
It's a change, for sure, and people will complain (this is a given and expected), but overall I think the example with StreamPipes really shows the reason why it's worth doing it. I think one way to make it simple for the PMCs to accept such a change is to have an explanation and simple instruction on how to go back to the previous settings. Then the answer to complaints might be "Adapt your bots/rules (best) or follow <these instructions> to bring back the old setting". BTW. I also agree having longer than single-letter [TOPICS] and always prepend it with [GH] would be a more reasonable default. J. On Fri, Jun 30, 2023 at 10:36 AM sebb <seb...@gmail.com> wrote: > Mostly agree, though I wonder why the numbers have been dropped from > the shorter titles. > > [D] could be [DISCUSS] or [RFC] perhaps. > > On Fri, 30 Jun 2023 at 09:20, Christopher <ctubb...@apache.org> wrote: > > > > I think this would be really great. I'm not a big fan of the [I] and [D] > > topics, though. I think I'd rather see [ISSUE] and [DISCUSSION], but > either > > way, the ability to group emails is a big improvement. I'd also prefer to > > always include [GH] as a topic tag, so for example, [GH][ISSUE], so if > > people don't redirect them to another list, I can filter them out more > > easily. The reason for that is that I will still prefer to manage my > > notification subscriptions directly with GitHub, and prefer to suppress > > those on the lists by default. > > > > On Fri, Jun 30, 2023, 03:50 Christofer Dutz <christofer.d...@c-ware.de> > > wrote: > > > > > Hi all, > > > > > > So, we have made it possible to “integrate” GitHub PRs, Issues and now > > > even Discussions by having infra auto-generate emails. > > > However, is the default setting for these just completely useless (in > my > > > opinion). > > > > > > Without taking action currently there are only the following options: > > > > > > * A project just redirects the emails to another lists (commits@ > or > > > notifications@ or whatever) > > > * A project gets a totally human-unreadable dev-list. > > > > > > As I see my role as a director in actually having a look at all of our > > > mailinglists this has become more and more painful over time. > > > But it got me thinking: If I’m having problems being able to see what a > > > project is up to – so will others. > > > > > > Some of the projects will have received many comments from me over the > > > past few months, as I’m trying to make dev-lists usable again. > > > Infra did add the ability to customize the default templates for the > > > subjects of auto-generated emails. And last month a PR of mine got > merged, > > > that also allowed the customization of GitHub Discussions. > > > > https://community.apache.org/contributors/mailing-lists.html#configuring-the-subject-lines-of-the-emails-being-sent > > > > > > I had many discussions with folks at infra about changing the defaults, > > > but generally met opposition. The general argument was, that there > would be > > > bots that automatically consume these emails and these would be > confused if > > > we changed the defaults. > > > > > > However, I think at the ASF we should be optimizing for people and not > for > > > bots. Right now we have many projects where following the list is very > > > difficult and therefore we’re losing a big part of our transparency. > > > > > > I’m bringing this here as I think Comdev is where such discussions > should > > > be had. > > > > > > So in general, I would like to change the defaults used by the GitHub > > > tooling to the ones I proposed in > > > > https://community.apache.org/contributors/mailing-lists.html#configuring-the-subject-lines-of-the-emails-being-sent > > > . Quite a number of projects have adopted these settings: > > > Like StreamPipes: > > > https://lists.apache.org/list?d...@streampipes.apache.org:lte=4M > > > > > > What do you folks think? > > > > > > Chris > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
