Hi all, well, I removed the issue numbers, as I thought that they only bring very limited value to the reader and the title itself gives way more context. Of course, could we add them, but then I would recommend to add them at the end (just like the repository name).
And the reason I chose the “I”, “PR” and “D” was that I am subscribed to many lists and if I’m travelling, I read a lot of them on my phone (as I know others do too). I just wanted to keep the static stuff as short as possible to allow displaying more of the subject on small screens. But I’m totally open to discussing the format as I am just 100% sure the current default is harmful. Chris Von: sebb <seb...@gmail.com> Datum: Freitag, 30. Juni 2023 um 10:36 An: dev@community.apache.org <dev@community.apache.org> Betreff: Re: Changing the defaults for GitHub generated email titles? 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
