Christofer Dutz wrote on 6/30/23 3:49 AM:
...snip...
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
On 2023-06-30 19:41, rbo...@rcbowen.com wrote:
On Fri, 2023-06-30 at 13:55 +, Christofer Dutz wrote:
* About breaking automation projects might have set up: I would
absolutely doubt there is even a single Apache project that has setup
automation based on these emails. I could imagine
On Fri, 2023-06-30 at 13:55 +, Christofer Dutz wrote:
> * About breaking automation projects might have set up: I would
> absolutely doubt there is even a single Apache project that has setup
> automation based on these emails. I could imagine that there is a
> hand full of companies
Hi all,
Aggregating responses to multiple emails:
* Sending an Email ahead of time with a code-snippet that allows keeping
the old defaults (If a project wants to keep the old, all they need to do is
copy that to their .asf.yaml-file and nothing will change)
* About different
Sent from my iPhone
> On Jun 30, 2023, at 2:14 AM, Christofer Dutz
> wrote:
>
> Hi Bertrand,
>
> In general, I would agree, but the problem is that we currently have a very
> large number of unreadable lists.
> This is what I’m generally trying to fix. Some projects responded with “If
>
I read a lot emails on my phone, so shorts subjects are good. If each
subject becomes [PROJECT][DISCUSSION][PR 123] then it's worse than now IMO.
Gary
On Fri, Jun 30, 2023, 04:20 Christopher wrote:
> I think this would be really great. I'm not a big fan of the [I] and [D]
> topics, though. I
Hi Chris,
On Fri, Jun 30, 2023 at 11:14 AM Christofer Dutz
wrote:
> ...In general, I would agree, but the problem is that we currently have a very
> large number of unreadable lists
Fixing this is a valid goal, but breaking automation that projects
might have setup is very bad.
I guess
Hi Bertrand,
In general, I would agree, but the problem is that we currently have a very
large number of unreadable lists.
This is what I’m generally trying to fix. Some projects responded with “If the
defaults are the ways they are, they probably are for a reason … we’ll stick
with the
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
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
Hi,
On Fri, Jun 30, 2023 at 9:50 AM Christofer Dutz
wrote:
> ...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
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 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
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
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:
*
14 matches
Mail list logo
