Re: Short Email to committers@ highlighting our generative AI/tools guidance

2023-08-04 Thread rbowen
On Fri, 2023-08-04 at 19:01 +0300, Roman Shaposhnik wrote: > On Fri, Aug 4, 2023 at 3:53 PM wrote: > > > > On Fri, 2023-08-04 at 15:26 +0300, Roman Shaposhnik wrote: > > > Hi! > > > > > > I was contemplating sending a really short email > > > to committers@ with the $subj. Who should I talk > >

Re: Short Email to committers@ highlighting our generative AI/tools guidance

2023-08-04 Thread Roman Shaposhnik
On Fri, Aug 4, 2023 at 3:53 PM wrote: > > On Fri, 2023-08-04 at 15:26 +0300, Roman Shaposhnik wrote: > > Hi! > > > > I was contemplating sending a really short email > > to committers@ with the $subj. Who should I talk > > with to get this done (or convince myself that > > an email to a different

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Daniel Gruno
On 2023-08-04 16:02, rbo...@rcbowen.com wrote: But the current setting is objectively awful, and so far I have not heard even one person saying that it's better. I'm perplexed as to why we'd want to even suggest, much less encourage, remaining with the current setting. The current defaults

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread rbowen
On Fri, 2023-08-04 at 06:46 -0700, Craig Russell wrote: > I agree with Mark. > > > On Aug 4, 2023, at 02:36, Mark Thomas wrote: > > > > I suggest the following: > > > > - announce to projects that the default is changing in X days / > > weeks > >  (or even months) time > > - provide

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Craig Russell
I agree with Mark. > On Aug 4, 2023, at 02:36, Mark Thomas wrote: > > I suggest the following: > > - announce to projects that the default is changing in X days / weeks > (or even months) time > - provide instructions for what projects need to do before then to keep > the existing format

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread rbowen
On Fri, 2023-08-04 at 15:26 +0200, Jarek Potiuk wrote: > +1. Looks way better. Updated draft, for the sake of having it in the archive: Subject: Mailing list threading improvements Dear {Committers/members of the Apache PMCs}, TL;DR: We’re updating how auto-generated email from Github will be

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Jarek Potiuk
+1. Looks way better. On Fri, Aug 4, 2023 at 3:21 PM Christofer Dutz wrote: > > Hi all and especially Rich … > > I love your version … and yes … I really need to focus more on the “what you > get” > and less on “why where you’re at sucks” sort of narrative ;-) > > Chris > > > Von: Peter

AW: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Christofer Dutz
Hi all and especially Rich … I love your version … and yes … I really need to focus more on the “what you get” and less on “why where you’re at sucks” sort of narrative ;-) Chris Von: Peter Hunsberger Datum: Freitag, 4. August 2023 um 15:06 An: dev@community.apache.org Betreff: Re: [DRAFT]

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Peter Hunsberger
On Fri, Aug 4, 2023 at 7:45 AM wrote: > Ok, I propose this alternative approach - more on the "here's how > things are getting better" tone than the "Here's how things were awful" > tone, and half the length: > > > > > Subject: Mailing list threading improvements > To: dev@ > > Dear

Re: Short Email to committers@ highlighting our generative AI/tools guidance

2023-08-04 Thread rbowen
On Fri, 2023-08-04 at 15:26 +0300, Roman Shaposhnik wrote: > Hi! > > I was contemplating sending a really short email > to committers@ with the $subj. Who should I talk > with to get this done (or convince myself that > an email to a different ML is better ;-))? It's definitely hard to know

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread rbowen
On Fri, 2023-08-04 at 08:45 -0400, rbo...@rcbowen.com wrote: > Ok, I propose this alternative approach - more on the "here's how > things are getting better" tone than the "Here's how things were > awful" > tone, and half the length: Note: Draft lives here:

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread rbowen
Ok, I propose this alternative approach - more on the "here's how things are getting better" tone than the "Here's how things were awful" tone, and half the length: Subject: Mailing list threading improvements To: dev@ Dear Apache project developers, TL;DR: We’re updating how

AW: Short Email to committers@ highlighting our generative AI/tools guidance

2023-08-04 Thread Christofer Dutz
Hi Roman, Have you thought about asking Chat GPT where to post it? ;-) (duck and cover) Chris Von: Roman Shaposhnik Datum: Freitag, 4. August 2023 um 14:26 An: ComDev Betreff: Short Email to committers@ highlighting our generative AI/tools guidance Hi! I was contemplating sending a really

Short Email to committers@ highlighting our generative AI/tools guidance

2023-08-04 Thread Roman Shaposhnik
Hi! I was contemplating sending a really short email to committers@ with the $subj. Who should I talk with to get this done (or convince myself that an email to a different ML is better ;-))? Thanks, Roman. - To unsubscribe,

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Rich Bowen
As discussed offline, I feel like the tone of this messaging is wrong. Give me a bit to get to my desk and I will propose an alternate draft. Shosholoza, Rich On Fri, Aug 4, 2023, 04:43 Christofer Dutz wrote: > Hi, > > Here comes a draft for an email I would like to send out. > > Not quite

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Daniel Gruno
On 2023-08-04 11:52, Jarek Potiuk wrote: Few comments: * make it shorter * add TL;DR; explaining in one paragraph what it is about, what effect it will have on those who receive it * add - immediately after that - mentioning that while the change is coming by default to everyone, everyone has a

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Jarek Potiuk
Few comments: * make it shorter * add TL;DR; explaining in one paragraph what it is about, what effect it will have on those who receive it * add - immediately after that - mentioning that while the change is coming by default to everyone, everyone has a way to go back easily (and link to a doc

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Gilles Sadowski
Hi Sebb. Le ven. 4 août 2023 à 11:29, sebb a écrit : > > This was not a fair poll Sure. [But suggestions to organize a fair (thus official?) poll are usually ignored.] > - it was not open long enough. > Also it is not representative; participation on this list is not > required of projects. >

AW: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Christofer Dutz
Hi all, and thanks Mark and Jarek. I fully agree with what you said. And regarding the email: Tthat’s why I proposed in the draft email a time a few weeks in the future (but not too many) and added links to what a project would need to do to keep things the way they are. If a project deeply

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Jarek Potiuk
I personally think if it is super easy to change back, I see no problem with making the change. "Ask for forgiveness not for permission". It already happened in the past that someone in the past "forced" the projects to use previous defaults by the fact of defining it. What was the process when

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread Mark Thomas
On 04/08/2023 10:28, sebb wrote: This was not a fair poll - it was not open long enough. Also it is not representative; participation on this list is not required of projects. And people participating in the discussion are likely to be in favour. I don't think Comdev should be making decisions

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread sebb
This was not a fair poll - it was not open long enough. Also it is not representative; participation on this list is not required of projects. And people participating in the discussion are likely to be in favour. I don't think Comdev should be making decisions on behalf of other projects. Note:

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

2023-08-04 Thread sebb
NAK - I don't think the defaults should be changed; instead provide docs on how to do so Don't force projects to change if they don't want to On Wed, 2 Aug 2023 at 07:46, Christofer Dutz wrote: > > Well, > > stating the obvious, I’ll add my +1 ;-) > > And yes Craig, I said the defaults … if you

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Gilles Sadowski
Hello. Sorry to be somewhat off-topic but it relates to the message contents... See inline comment. Le ven. 4 août 2023 à 10:43, Christofer Dutz a écrit : > > Hi, > > Here comes a draft for an email I would like to send out. > > Not quite sure which audience we should choose … committers,

Re: [DRAFT] Email to all PMCs or Committers

2023-08-04 Thread sebb
On Fri, 4 Aug 2023 at 09:44, Christofer Dutz wrote: > > Hi, > > Here comes a draft for an email I would like to send out. > > Not quite sure which audience we should choose … committers, (p)pmcs? (P)PMCs, but see below. > Also, not quite sure about the timeframe? As I know Infra merges PRs on

[DRAFT] Email to all PMCs or Committers

2023-08-04 Thread Christofer Dutz
Hi, Here comes a draft for an email I would like to send out. Not quite sure which audience we should choose … committers, (p)pmcs? Also, not quite sure about the timeframe? As I know Infra merges PRs on Thursdays, I would propose the 17th of August 2023 as date for the change to be made.

Re: [PR] Update mailing-lists.md (comdev-site)

2023-08-04 Thread via GitHub
chrisdutz merged PR #126: URL: https://github.com/apache/comdev-site/pull/126 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: