ladder: add amaanx86 as an org member#416
Conversation
joestringer
left a comment
joestringer
left a comment
There was a problem hiding this comment.
Hi, it's great to see this interest 🎉 Typically we would expect a bit more regular contribution to the project before adding you as a member, so at this time it's a bit premature. But cloud-specific integrations is an area of the project we often lack contributors for, so please do continue to engage :)
|
Thanks for the response @joestringer. I understand the concern, and I'm committed to continuing to contribute. The immediate motivation for requesting membership was my open PR cilium/cilium#46116 - a documentation guide for running Cilium in CNI chaining mode on Oracle Kubernetes Engine (OKE) with VCN-Native Pod Networking. It's been open for nearly a month without a review, and I thought org membership might help me better engage with the process (ping reviewers, triage, etc.) and add value in the OCI/cloud integrations space where you mentioned there's a gap. That said, I'll keep contributing and come back to this when the track record speaks for itself. Happy to close this for now if that's preferred. |
I appreciate the thought here. Have you also tried reaching out in the #development Slack channel? That said, I think there's mainly two reviewers who have relevant interest in this specific area. Those folks were pinged in the last week. I'm not sure there's something concrete that member status would provide in this regard. For all I know those folks may be on summer break, or perhaps they are busy with other tasks so they haven't had a chance to review your PR yet. If I follow that area in particular, I think the hope is that OKE platform support should just be a matter of plugging in the right config options into Cilium without chaining or any native changes. So hopefully the ongoing maintenance burden should be relatively low. We'd still welcome your involvement in helping to ensure a good experience for users such as yourself for this target platform (for instance keeping the docs accurate as OKE changes). All that said, yeah maybe we close this for now and feel free to revisit again if you find that you are frequently interacting with issues and PRs (for instance, multiple per week). |
|
@joestringer Thanks for the context, that makes sense. The doc was actually a business requirement on my end. I'm promoting Cilium (and eventually Tetragon) within a semi-governmental organization, so having accurate documentation for OKE chaining mode was important to get right. That was the main driver behind the PR. I did post in #development on Slack as well but didn't get a response there either. The assigned reviewer eventually pinged the relevant folks, so I'll just wait it out. Totally understandable if they're busy or on vacation. One thing worth mentioning - if the PR does get merged, it would actually help me a lot with internal approvals for a large-scale Cilium rollout. (Talking about the chaining doc) Enterprise stakeholders and production sign-offs in organizations like ours typically need concrete references from official docs or upstream sources. We can test and validate things in UAT, but when it comes to production the decision makers need to see that the platform is formally supported, not just something that works via a fallback path. Having it documented upstream would carry a lot of weight in that conversation. Either way, I genuinely enjoy working with Cilium and eBPF in general, so I'll keep contributing where I can. Both personally and organizationally I benefit a lot from open source, so giving back is something I care about. I'll revisit the membership request once I'm more regularly involved across issues and PRs. Happy to help on AWS-related things too since that's a big part of my day-to-day. Appreciate you taking the time to respond. |
3 participants
Moving up the Contributor Ladder
My Relevant Contributions to the Cilium Ecosystem
Additional Notes
Reading design-cfps#78 on the native OCI integration direction is what got me thinking about longer term involvement. I want to see that work happen and I have the OCI production context to help push it forward, not just the docs side.
My day job is cloud infra - working across AWS and OCI for enterprise clients. Outside Cilium I have contributed upstream to projects I actually use at work: Oracle OCI Native Ingress Controller (health probes and resource limits fix, PR #139), HashiCorp Terraform AWS Provider (CloudWatch Logs S3 Tables resources, PR #48190), GoHarbor (ECR China region domain fix, PR #23326), and GitLab (Vue.js PDF download for markdown blob view, MR !238594).
The OCI doc PR is what got me looking more seriously at Cilium contribution. It kept stalling because there is nobody with OCI context in the reviewer pool. I want to be that person - help review OCI-related PRs, flag things that break on Oracle Cloud, and make the cloud provider coverage better. Org membership is the first step.
/cc @xmulligan