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
>
laining about
> the change after it happened 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:
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
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
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 instruction
vote
>>> on).
>>> So my plan is to show this thread to Infra to show that there’s general
>>> support for the proposal.
>>>
>>> I really hope they won’t let me jump another hoop, asking me to bring this
>>> to a vote on Members@.
>>>
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
) as we usually do
> > things.
> > But yeah … I guess as soon as that time is over, I’ll create an infra
> > ticket.
> >
> > Chris
> >
> >
> > Von: Volkan Yazıcı
> > Datum: Mittwoch, 2. August 2023 um 09:39
> > An: Christof
t unchanged.
Chris
Von: Richard Zowalla mailto:rich...@zowalla.com>>
Datum: Mittwoch, 2. August 2023 um 08:10
An: dev@community.apache.org<mailto:dev@community.apache.org>
mailto:dev@community.apache.org>>
Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
ticket.
>
> Chris
>
>
> Von: Volkan Yazıcı
> Datum: Mittwoch, 2. August 2023 um 09:39
> An: Christofer Dutz
> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
> generate GitHub integration email subjecs?
> Check. Is there (or will there be) an INF
aig, I said the defaults … if you have explicitly configured your
> .asf.yaml subjects, they are left unchanged.
>
> Chris
>
>
> Von: Richard Zowalla
> Datum: Mittwoch, 2. August 2023 um 08:10
> An: dev@community.apache.org
> Betreff: Re: [POLL] Should we ask Infra t
+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 own settings can continue to use them, I'm
>>
>> +1
>>
>> to change the defaults for all projects. If the projects don't l
+1
On Wed, Aug 2, 2023 at 2:15 AM Craig Russell wrote:
>
> Hi Christofer,
>
> As long as projects with their own settings can continue to use them, I'm
>
> +1
>
> to change the defaults for all projects. If the projects don't like being
> able to use their lists again, they can always go back to
Hi Christofer,
As long as projects with their own settings can continue to use them, I'm
+1
to change the defaults for all projects. If the projects don't like being able
to use their lists again, they can always go back to what they had before.
Thanks,
Craig
> On Aug 1, 2023, at 05:16, Chris
+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
+1
@Christofer, thanks for taking care of this.
The improvement is undeniable.
@Gary, see the date range in the URLs.
You might need to manually perform an empty search in those ranges.
On Tue, Aug 1, 2023 at 2:16 PM Christofer Dutz
wrote:
> Starting a new thread as the last one sort of dried
+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 +
Hi.
Le mar. 1 août 2023 à 14:17, Christofer Dutz
a écrit :
>
> Starting a new thread as the last one sort of dried up and didn’t quite form
> anything actionable.
>
> Being subscribed to many of our mailing-lists and most recently looking into
> every project, dev-lists when reviewing board rep
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/list?d...@streampipes.apache.org:dfr=2023-6-12|dto=2023-6-18
They both use "[PR]". What am I missing?
Gary
On Tue, Aug 1, 2023, 8:17 AM Christofe
+1 to making this change. It would immediately make our mailing lists
more consumable and welcoming to actual humans.
Coupled with a page explaining how this works (Oh! Look! There's
already one at
https://community.apache.org/contributors/mailing-lists.html ) this
would be a great service to our
23 matches
Mail list logo
