he.org
Subject: [EXTERNAL] FW: Re: Flink technical debt. Chi meeting
Hello all,
We had our 3rd Community Health Initiative meeting today. We triaged 30 PRs!
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=332499620
fyi When you see PR comments like
“Reviewed by Chi on …”
This means th
regards, David.
From: David Radley
Date: Friday, 29 November 2024 at 12:07
To: dev@flink.apache.org , Tom Cooper
, Robert Metzger
Subject: FW: [EXTERNAL] Re: Flink technical debt.
Hi all,
We had the 2nd 30 minute working meeting of the Community Health Initiative
(CHI) yesterday for Western
y, 15 November 2024 at 08:13
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical debt.
Thanks David for the summary of the first call.
Could you (or another volunteer) setup a wiki page for this initiative,
where we collect meeting notes and the link to the invite etc.
Here is a si
: FW: Re: Flink technical debt.
Hi David,
thanks for driving this
I would bring several ideas here
1. I noticed you started to comment on some issues like
>Reviewed by Chi on ...
I wonder if it might be more helpful to use kind of labels or something
like that instead of comments
since it is h
like low hanging
> fruit for committers to merge. WDYT?
>
> I will then look at any new PRs prior to the next meeting and the next
> latest ones in the list.
> Any feedback on the approach and focus welcome.
>
> Kind regards, David.
>
>
>
> From: Robert Metzg
4 at 08:13
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical debt.
Thanks David for the summary of the first call.
Could you (or another volunteer) setup a wiki page for this initiative,
where we collect meeting notes and the link to the invite etc.
Here is a similar page:
https://cwiki.apa
, 19 November 2024 at 15:48
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: FW: RE: Flink technical debt.
Hi David,
Thanks for setting up meetings which are more convenient for the Western
timezones. That first one happens to be on US Thanksgiving.
Did you get sorted with ASF Confluence access
regards, David.
>
>
> From: David Radley
> Date: Friday, 15 November 2024 at 11:59
> To: dev@flink.apache.org
> Subject: [EXTERNAL] RE: Flink technical debt.
> Hi Robert,
> Good idea - yes I put this and subsequent meeting content on the wiki –
> user name davidradl wou
024 at 11:59
To: dev@flink.apache.org
Subject: [EXTERNAL] RE: Flink technical debt.
Hi Robert,
Good idea - yes I put this and subsequent meeting content on the wiki – user
name davidradl would be great, kind regards, David.
From: Robert Metzger
Date: Friday, 15 November 2024 at 08:13
T
Hi Robert,
Good idea - yes I put this and subsequent meeting content on the wiki – user
name davidradl would be great, kind regards, David.
From: Robert Metzger
Date: Friday, 15 November 2024 at 08:13
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical debt.
Thanks David for
;
> From: David Radley mailto:david_rad...@uk.ibm.com
> >>
> Date: Wednesday, 13 November 2024 at 10:48
> To: dev@flink.apache.org<mailto:dev@flink.apache.org> <
> dev@flink.apache.org<mailto:dev@flink.apache.org>>
> Subject: FW: [EXTERNAL] Re: Flink technic
gt;>
Date: Wednesday, 13 November 2024 at 10:48
To: dev@flink.apache.org<mailto:dev@flink.apache.org>
mailto:dev@flink.apache.org>>
Subject: FW: [EXTERNAL] Re: Flink technical debt.
Hi all,
Yes Jim – 11:30 AM GMT.
Sorry this is not very US friendly, I am trying to accommodate a few In
Kind regards, David.
>
> From: Nic Townsend
> Date: Thursday, 7 November 2024 at 17:26
> To: dev@flink.apache.org
> Subject: [EXTERNAL] RE: Flink technical debt.
> Hi Robert, David
>
> I am very much interested in a backlog review call – personally for two
> reasons:
&g
>
> From: Nic Townsend
> Date: Thursday, 7 November 2024 at 17:26
> To: dev@flink.apache.org
> Subject: [EXTERNAL] RE: Flink technical debt.
> Hi Robert, David
>
> I am very much interested in a backlog review call – personally for two
> reasons:
>
>
> 1. Learning a b
email.
I hope this works for everyone / most people, let me know if there are any
issues,
Kind regards, David.
From: Nic Townsend
Date: Thursday, 7 November 2024 at 17:26
To: dev@flink.apache.org
Subject: [EXTERNAL] RE: Flink technical debt.
Hi Robert, David
I am very much interested in a
can help, it’s often easier
for me hearing people describe the problem
--
Nic Townsend
IBM Event Processing
Senior Engineer / Technical Lead
Slack: @nictownsend
From: Robert Metzger
Date: Wednesday, 6 November 2024 at 15:22
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical
Hi David,
Thanks for this initiative. It looks really helpful and please count me in.
Regards,
Ammu Parvathy
On 2024/11/07 10:35:43 Hong Liang wrote:
> Hi David,
>
> Thanks for this proposal. I agree that this is something we can strive to
> do better in the Flink community, and I would be keen
Hi David,
Thanks for this proposal. I agree that this is something we can strive to
do better in the Flink community, and I would be keen to help out here.
+1 to the suggestion for a recurring working group meeting to triage and
assign PRs.
I think the suggestions we have on the thread are great
Hello David,
I believe this is a valuable initiative that will significantly enhance the
codebase as well. I would also like to join this group and contribute to
the community.
Regards,
Anu K T
On Mon, Nov 4, 2024 at 8:36 PM David Radley wrote:
> Hello,
> I have been looking at the Flink Jira
Hi David, Proposal looks useful and valuable. I would like to join the
group and contribute, It would be great to have a meeting to outline the
goals and what group members can do to meet the goals. Thank you
Regards
Lajith K
On Thu, Nov 7, 2024 at 1:50 AM Shalini wrote:
> Hi David,
>
> I agree
Hi David,
I agree that this is a very valuable initiative, and I would like to join
this working group as an opportunity to contribute to the community.
Thanks,
Shalini M
On Thu, Nov 7, 2024 at 12:11 AM Ferenc Csaky
wrote:
> Hi,
>
> Thank you David for initiating this discussion. I think it wo
Hi David,
Thank you for this initiative. You can count me in. I think that will help to
prioritize and focus on what mater the most to the community.
I did a quick search on Jira to help narrow down the list of Blocker and
Critical issues based on the issue type:
=> 195 are not Closed, Done or
Hi,
Thank you David for initiating this discussion. I think it would
definitely worth some attention from the community to try to focus
a bit more on these problems.
I would be happy to participate in the calls, and help out with
reviewing/merging PRs.
Best,
Ferenc
On Wednesday, November 6t
Hi David, Tom,
Regarding bots, I've seen that there is some JIRA bot which moves priority
down over time. See https://issues.apache.org/jira/browse/FLINK-12173 as
an example.
I recently hit an issue where a new-to-Flink contributor had filed a ticket
and put up a PR around six months ago and no
Hi Tom,
Welcome 😊
Does anyone in the community know if we have considered running bots as Tom
suggests,
Kind regards, David.
From: Tom Cooper
Date: Wednesday, 6 November 2024 at 15:34
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical debt.
Hey David,
As a newcomer to
off meeting to agree goals and
metrics and ongoing meeting structure – I like your proposal.
Kind regards, David.
From: Robert Metzger
Date: Wednesday, 6 November 2024 at 15:22
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink technical debt.
Hey David,
Thanks a lot for this initiative
Hey David,
As a newcomer to the community myself, the number of open PRs and JIRA issues
is a bit daunting. So thanks for starting this initiative.
I like the idea of tackling the mountain by triaging the PRs / JIRA Issues and
I would be very happy to join the effort. However, I wonder if it w
Hey David,
Thanks a lot for this initiative.
What do you think about setting up a call weekly or every second week, open
to the public, where we collaboratively review a backlog of Jira tickets
and triage them into:
- Closing,
- following up,
- assigning a committer owner?
The purpose of the call
28 matches
Mail list logo
