Skip to content

ladder: add immanuwell as an organization member - #428

Closed
immanuwell wants to merge 1 commit into
cilium:mainfrom
immanuwell:ladder/add-immanuwell-org-member
Closed

ladder: add immanuwell as an organization member#428
immanuwell wants to merge 1 commit into
cilium:mainfrom
immanuwell:ladder/add-immanuwell-org-member

Conversation

@immanuwell

@immanuwell immanuwell commented Jul 24, 2026

Copy link
Copy Markdown

I'd like to become Cilium org member
I'm actively contributing across the project, here are a few examples:

@dylandreimerink @mtardy @FedeDP if you think I meet the criteria, I'd appreciate an LGTM
Thanks!

@immanuwell
immanuwell requested a review from a team as a code owner July 24, 2026 07:05
@joestringer

Copy link
Copy Markdown
Member

Hey, would love to see you continue to contribute. I see the PRs mentioned in the description are across a range of different repos, is there a particular area you're focused on and would like to work with others more on? This helps existing members and reviewers to help steer you on your contribution journey. We also generally expect this is the first step towards more longer term involvement in the project.

@immanuwell

immanuwell commented Jul 24, 2026

Copy link
Copy Markdown
Author

is there a particular area you're focused on and would like to work with others more on?

@joestringer yes, I like working on tetragon ¹ ² ³ (+5 more) and pwru ¹ ² ³ (+2 more), I've already made several contributions to both and would like to get more involved there

@joestringer

Copy link
Copy Markdown
Member

cc @cilium/tetragon-reviewers @cilium/pwru

@mtardy mtardy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah thanks @immanuwell for the many fixes on the tetra CLI (see PRs here)

@FedeDP FedeDP left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the great work you are putting in! Lots of really great fixes 🚀

@joestringer joestringer added the dont-merge/maintainer-coordination This requires additional manual action from maintainers at merge time to complete the change. label Jul 28, 2026
@rgo3

rgo3 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

I really appreciate your work on pwru so far @immanuwell but I'd like to see a bit more and longer involvement in the community. Your output over the last few weeks is certainly impressive but similar to Joe, I'd suggest picking a more focused area and build your knowledge and expertise there. At the current level of involvement, I'm not sure how membership status would be beneficial.

Besides creating PRs, in times of "AI driven development" the Cilium community could really use more people to investigate and resolve open issues. And if you are interested in continuing to work on pwru don't hesitate to reach out or make feature requests.

@immanuwell

immanuwell commented Jul 29, 2026

Copy link
Copy Markdown
Author

@rgo3 got it, should I close this PR?
or do you mean I should focus primarily on tetragon, where I already did a lot of useful contributions?

@rgo3

rgo3 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

From my perspective, I think it makes sense to close this PR for now and revisit after a few more months of continued involvement.

To be clear, I’m not saying that you need to focus exclusively on Tetragon, or that your contributions there haven’t been useful. As Federico and Mahé stated, your Tetragon contributions have been valuable, and I feel the same about your contributions to pwru. My main concern is that most of this activity has taken place within the last one or two months. And to me membership status shouldn't just reflect a certain number or pace of contributions, but demonstrate a certain level of understanding and willingness to take on ownership of the respective areas over time.

Please continue to contribute in the areas that genuinely interest you. That can include PRs, investigating and debugging issues, testing or reviewing changes, and helping other contributors. This is a strong start and I don't mean to discourage you in any way.

@immanuwell

Copy link
Copy Markdown
Author

to me membership status shouldn't just reflect a certain number or pace of contributions, but demonstrate a certain level of understanding and willingness to take on ownership of the respective areas over time

@rgo3 I am 100% agree, so I'm going to close this PR

@immanuwell immanuwell closed this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dont-merge/maintainer-coordination This requires additional manual action from maintainers at merge time to complete the change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants