[
https://issues.apache.org/jira/browse/COMDEV-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Bowen resolved COMDEV-541.
---
Resolution: Resolved
This was for an event that is now past.
> Need an apache.org email address
Claude Warren created COMDEV-541:
Summary: Need an apache.org email address for a content producer
Key: COMDEV-541
URL: https://issues.apache.org/jira/browse/COMDEV-541
Project: Community Development
Hi,
On Tue, Oct 10, 2023 at 12:52 PM Kashif Khan wrote:
> ...I have been working on the Tika parser to parse a few text files and it has
> been working fine until I have come to an issue...
this list is for general community-related discussions, for Tika
you'll have to ask on their own list, see
Hi team,
I have been working on the Tika parser to parse a few text files and it has
been working fine until I have come to an issue where it is not able to
parse the text file if it contains 'email/message contents'.
This means if the text file contains any of the terms like 'From
ges have been merged … now let’s see ;-)
>>
>> Chris
>>
>> Von: Christofer Dutz
>> Datum: Samstag, 30. September 2023 um 08:39
>> An: dev@community.apache.org
>> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
>> generate GitHub integr
n: dev@community.apache.org
> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
> generate GitHub integration email subjecs?
> Well it wouldn't be you, who's getting the beer... You would need ask sebb to
> share that beer with you ;-)
>
> Chris
>
Ok … changes have been merged … now let’s see ;-)
Chris
Von: Christofer Dutz
Datum: Samstag, 30. September 2023 um 08:39
An: dev@community.apache.org
Betreff: Re: [POLL] Should we ask Infra to change the defaults used to generate
GitHub integration email subjecs?
Well it wouldn't b
Dev
Subject: Re: [POLL] Should we ask Infra to change the defaults used to generate
GitHub integration email subjecs?
Loophole question: can we start a campaign to complain just to get free
beer?
On Fri, Sep 29, 2023, 15:25 Craig Russell wrote:
> I thought that a few folks responded to sebb ea
r?
> >
> > Chris
> >
> >
> >
> > Von: sebb
> > Datum: Freitag, 4. August 2023 um 11:21
> > An: dev@community.apache.org
> > Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
> generate GitHub integration email subjecs?
> >
ned than are expressing to be happy with them, I’ll
> invite you to a beer?
>
> Chris
>
>
>
> Von: sebb
> Datum: Freitag, 4. August 2023 um 11:21
> An: dev@community.apache.org
> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
> generate Gi
the defaults used to generate
GitHub integration email subjecs?
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,
>
>
bdelacretaz commented on PR #128:
URL: https://github.com/apache/comdev-site/pull/128#issuecomment-1711411156
Looks good to me, thank you!
I'd just add tags to the decision making page, suggest
tags: ["pmc","governance","voting"]
--
This is an automated message from the A
rbowen merged PR #128:
URL: https://github.com/apache/comdev-site/pull/128
--
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: dev-unsubscr...@community.apa
rbowen opened a new pull request, #128:
URL: https://github.com/apache/comdev-site/pull/128
As per email on 2023-05-30, subject line "Proposal: Consolidate the various
pages about voting/deciding", which was agreed to by consensus. Proceeding
based on that agreement.
Adds
Ok …
So, off the email goes … let’s see what’s gonna happen to my inbox now 😲
I stuck with the Oct. 1st as I didn’t get any other feedback on selecting
another date.
Chris
Von: Christofer Dutz
Datum: Dienstag, 15. August 2023 um 11:20
An: dev@community.apache.org
Betreff: AW: AW: [DRAFT
So …
As I haven’t heard any other opinions, my plan is the following:
* Chose the date of Oct. 1st for making the change active.
* Apply my PR with the updated mailing-list.md.
* Send out the email to all dev-lists.
Any objections?
The content of the email will be as follows
So here some updates to the mailing-list page:
https://github.com/apache/comdev-site/pull/127
Chris
Von: Christofer Dutz
Datum: Sonntag, 13. August 2023 um 20:26
An: dev@community.apache.org
Betreff: AW: AW: [DRAFT] Email to all PMCs or Committers
Hi Jarek,
I was told there’s a direct way to
Hi Jarek,
I was told there’s a direct way to send to all dev-lists.
That’s one email going out for me … but thanks for that tip.
Could come in handy some time.
Chris
Von: Jarek Potiuk
Datum: Sonntag, 13. August 2023 um 19:54
An: dev@community.apache.org
Betreff: Re: AW: [DRAFT] Email to all
sheet
into a pipeline and send "mass email campaign" to all the projects with
customized variables from the spreadsheet. The nice thing about it is that
it actually sends those emails from your gmail UI - so it is not super
fast, but it also by-passess all the tools that detect mass mailing a
: [DRAFT] Email to all PMCs or Committers
Hi all,
So, as I’m back from my holidays … I am planning on doing the following:
* Go through the repos of the projects we have and compile a list of the
ones affected by changed defaults.
* Send an email to each of the dev-lists (or whatever qualifies
Hi all,
So, as I’m back from my holidays … I am planning on doing the following:
* Go through the repos of the projects we have and compile a list of the
ones affected by changed defaults.
* Send an email to each of the dev-lists (or whatever qualifies as dev-list)
Gonna be a hell of
Well... I'll go for it as soon as I'm back from my short holiday.
Chris
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
From: sebb
Sent: Tuesday, August 8, 2023 12:16:42 AM
To: dev@community.apache.org
Subject: Re: AW: [DRAFT] Emai
On Mon, 7 Aug 2023 at 13:50, wrote:
>
> On Sat, 2023-08-05 at 15:37 +, Christofer Dutz wrote:
> > Hi all,
> >
> > So, I think we should stay with Rich’s version of the email.
> > Now to the next question … which list should we post this to?
>
> I think
On Sat, 2023-08-05 at 15:37 +, Christofer Dutz wrote:
> Hi all,
>
> So, I think we should stay with Rich’s version of the email.
> Now to the next question … which list should we post this to?
I think this should go to all dev@ lists, as those are the people
affected.
>
Hi all,
So, I think we should stay with Rich’s version of the email.
Now to the next question … which list should we post this to?
And what do you think should we define as a date when we’ll switch?
As far as I understood things, Infa merges PRs like mine on Thursdays.
How much time to we want to
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
> > &g
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 mys
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 wer
s
> > (or even months) time
> > - provide instructions for what projects need to do before then to
> > keep
> > the existing format
>
> Include in the message the actual current defaults that can be
> copy/pasted into the projects' asf.yaml for project who prefer t
ithub.com/apache/infrastructure-github-discussions-notifier/pull/2
>>> However, have I marked them as DRAFT so they aren’t executed today.
>>>
>>> I think it would make sense to send out an email first, notifying projects
>>> about the coming changes and to
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
; Chris
>
>
> Von: Peter Hunsberger
> Datum: Freitag, 4. August 2023 um 15:06
> An: dev@community.apache.org
> Betreff: Re: [DRAFT] Email to all PMCs or Committers
> On Fri, Aug 4, 2023 at 7:45 AM wrote:
>
> > Ok, I propose this alternative approach - more on the "here
] Email to all PMCs or Committers
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:
>
> -
ailing list threading improvements
> To: dev@
>
> Dear Apache project developers,
>
> TL;DR: We’re updating how auto-generated email from Github will be
> threaded on your mailing lists. If you want to keep the old defaults,
> details are below.
>
> We’re pleased to let y
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
Note: Draft lives here: https://hackmd.io/OLN1OC9UTIuk5seu5S8ZcQ - and
I've made a few small corrections/tweaks.
>
>
>
>
> Subject: Mailing list threading improvements
> To: dev@
>
> Dear Apache project developers,
>
> TL;DR: We’re updating how auto-generated email from
TL;DR: We’re updating how auto-generated email from Github will be
threaded on your mailing lists. If you want to keep the old defaults,
details are below.
We’re pleased to let you know that we’re tweaking the way that auto-
generated email from Github will appear on your mailing lists. This
wi
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
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, e
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.
>
1:13 AM Gilles Sadowski wrote:
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 choos
ee 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, (p)pmcs?
> >
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.
> A
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
t; https://github.com/apache/infrastructure-github-event-notifier/pull/12
> > https://github.com/apache/infrastructure-github-discussions-notifier/pull/2
> > However, have I marked them as DRAFT so they aren’t executed today.
> >
> > I think it would make sense to send out an
ithub-discussions-notifier/pull/2
However, have I marked them as DRAFT so they aren’t executed today.
I think it would make sense to send out an email first, notifying projects
about the coming changes and to define a date to which the changes will be
applied.
I’d be happy to prepare the email and
tps://github.com/apache/infrastructure-github-event-notifier/pull/12
> https://github.com/apache/infrastructure-github-discussions-notifier/pull/2
> However, have I marked them as DRAFT so they aren’t executed today.
>
> I think it would make sense to send out an email first, notifying projects
o 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,
> >>
> >&g
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 choos
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 kno
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
they aren’t executed today.
I think it would make sense to send out an email first, notifying projects
about the coming changes and to define a date to which the changes will be
applied.
I’d be happy to prepare the email and send it out (once the 72h for this POLL
are over).
Chris
Von
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
en 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
ow 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 act
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 fo
+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 str
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 s
t’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, tha
@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/l
+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 +
en 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 i
> 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 co
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 gen
.
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
Christofer Dutz wrote :
>
> ... Infra has been giving me quite some pushback on these changes...
I think backing your request by a comdev pmc vote can help, as it's then a
group representing multiple projects that makes the request, instead of
just you.
Bertrand
te” first and then “do a
>vote” next.
>
>Chris
>
>
>Von: hans.van.akel...@gmail.com
>Datum: Freitag, 28. Juli 2023 um 16:17
>An: dev@community.apache.org
>Betreff: Re: AW: AW: Changing the defaults for GitHub generated email titles?
>Does this really need a vote?
>
have to sort of find out “where to vote” first and then “do a
vote” next.
Chris
Von: hans.van.akel...@gmail.com
Datum: Freitag, 28. Juli 2023 um 16:17
An: dev@community.apache.org
Betreff: Re: AW: AW: Changing the defaults for GitHub generated email titles?
Does this really need a vote?
If
t; An: dev@community.apache.org
> Betreff: Re: AW: Changing the defaults for GitHub generated email titles?
> On Thu, 2023-07-27 at 19:46 +, Christofer Dutz wrote:
> > Ok,
> >
> > so after the discussion didn’t come up with any objections. I
> > prepared a PR and that
: Changing the defaults for GitHub generated email titles?
On Thu, 2023-07-27 at 19:46 +, Christofer Dutz wrote:
> Ok,
>
> so after the discussion didn’t come up with any objections. I
> prepared a PR and that was merged today.
> Now the templates no longer have to have a mandat
On Thu, 2023-07-27 at 16:11 -0400, Kelly Oglesbee wrote:
> exactly what emails are you changing, because I'm experiencing
> problems
> with my emails on my device?
Can you elaborate? What problems are you experiencing? How can the
situation be improved?
--
On Thu, 2023-07-27 at 19:46 +, Christofer Dutz wrote:
> Ok,
>
> so after the discussion didn’t come up with any objections. I
> prepared a PR and that was merged today.
> Now the templates no longer have to have a mandatory “repository”
> variable ;-)
>
> I updated the PLC4X settings and it s
Yu mid showing me the steps involve in this because Im a new comitter
On Thu, Jul 27, 2023, 4:35 PM Christofer Dutz
wrote:
> Hi Kelly,
>
> Well, I’m proposing to change the defaults for email automatically sent
> from GitHub for PRs, Issues and Discussions.
> I’m not changing any
Hi Kelly,
Well, I’m proposing to change the defaults for email automatically sent from
GitHub for PRs, Issues and Discussions.
I’m not changing anything right now … I just had one check removed that
validates the custom patterns a project has in its .asf.yaml
So technically this change
gt; What’s your thoughts? Should I simply start a vote?
> >
> > Chris
> >
> >
> >
> > Von: Christofer Dutz
> > Datum: Mittwoch, 19. Juli 2023 um 14:35
> > An: dev@community.apache.org
> > Betreff: AW: Changing the defaults for GitHub generated
the repository).
>
> What’s your thoughts? Should I simply start a vote?
>
> Chris
>
>
>
> Von: Christofer Dutz
> Datum: Mittwoch, 19. Juli 2023 um 14:35
> An: dev@community.apache.org
> Betreff: AW: Changing the defaults for GitHub generated email titles?
> Hi
generated email titles?
Hi all,
So, I’ve tracked down the requirement to the test, that requires the
“repository” variable,
But it doesn’t really explain why it’s required. I was told that it’s for some
20 year old reason, however that simply can’t apply to the custom email
templates for GitHub
Hi all,
So, I’ve tracked down the requirement to the test, that requires the
“repository” variable,
But it doesn’t really explain why it’s required. I was told that it’s for some
20 year old reason, however that simply can’t apply to the custom email
templates for GitHub ;-)
So, I opened a
defaults for GitHub generated email titles?
Why id this necessary?
On Tue, Jul 11, 2023, 8:56 AM Christofer Dutz
wrote:
> Hi Phil,
>
> Well, you can somewhat reduce it to whatever you like … however there
> seems to be one limitation, which I can’t quite explain.
> For some reason you n
it takes me something round half a second to know that it’s a PR,
> Issue or Discussion.
> Generally, I could even live without them all together as it doesn’t
> really matter, if a discussion is about a PR, Issue or just a
> general-purpose discussion.
> In an all-email workflow,
them all together as it doesn’t really
matter, if a discussion is about a PR, Issue or just a general-purpose
discussion.
In an all-email workflow, we never had these prefixes before … everything was
just a discussion.
But if you ask me .. I’d keep the minimal prefixes, but be in favor of the
ach project's mailing list page.
>
> Gary
>
> On Mon, Jul 3, 2023 at 8:12 AM Christofer Dutz
> wrote:
> >
> > Hi all,
> >
> > So here’s an example of one week’s email traffic on one project before
> and after the config changes:
> >
> > (Sorry for
means Fail, that kinda mapping. I'm not sure where the mapping would
be best documented, perhaps on each project's mailing list page.
Gary
On Mon, Jul 3, 2023 at 8:12 AM Christofer Dutz
wrote:
>
> Hi all,
>
> So here’s an example of one week’s email traffic on one project b
Hi all,
So here’s an example of one week’s email traffic on one project before and
after the config changes:
(Sorry for putting the Spotlight on you streampipes folks, but this is the best
positive example I know)
Before the change:
https://lists.apache.org/list?d
nce.
Thinking ahead, I'd be happy voting to send out PMCs email saying "the
default notifications are going to change on date X; email here to
opt-out". Keep track of opt-outs, and then change defaults for all
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 th
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 paying
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 Prefixes
etaz
> Datum: Freitag, 30. Juni 2023 um 11:11
> An: dev@community.apache.org
> Betreff: Re: Changing the defaults for GitHub generated email titles?
> Hi,
>
>> On Fri, Jun 30, 2023 at 9:50 AM Christofer Dutz
>> wrote:
>> ...I had many discussions with folks at
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 th
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 what
: Re: Changing the defaults for GitHub generated email titles?
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
the format as I am just 100% sure the
current default is harmful.
Chris
Von: sebb
Datum: Freitag, 30. Juni 2023 um 10:36
An: 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
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
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 if
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 see
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
peopl
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
rbowen merged PR #119:
URL: https://github.com/apache/comdev-site/pull/119
--
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: dev-unsubscr...@community.apa
rbowen opened a new pull request, #119:
URL: https://github.com/apache/comdev-site/pull/119
Shamelessly stolen from the PLC4x repo, where it was crafted by @chrisdutz
This makes auto-generated email from GitHub more readable, especially on
narrow (ie, phone) email clients, by
1 - 100 of 179 matches
Mail list logo
