Repository navigation
Compliance: Community Extension Projects #31
Description
The Crossplane governance has recently been updated to define the lifecycle and policies for Community Extension Projects.
The steering committee requests the maintainer team of this repo to take the time to thoroughly read and understand the new policies that all community extension projects must comply with.
Then, please respond on this issue with a self-assessment of how/whether this project is in compliance with the stated policies and any plans for remediation if necessary. If for any reason this project is not able to come into compliance, then this project will be at risk of being archived.
If you have any questions, check out this discussion first, because other projects may also share your same question. if you need any help or guidance, we're here to help make this project successful. Thank you!
Activity
jbw976 commentedon Sep 8, 2025
@jtucci @jaylevin @haarchri @jastang, it looks like all of you have maintainer permissions on this repo 🤓
After an audit of this repo, it appears to not yet be in compliance with the stated policies:
The steering committee needs to see progress on this repo towards compliance soon or it is at risk of being archived.
Will the maintainer team be able to address these issues soon? Thank you! 🙇♂️
haarchri commentedon Oct 15, 2025
i was only the creator and @jastang helped with publishing - so @jtucci @jaylevin what we want todo with this provider repo ?
dzmoore commentedon Jan 22, 2026
Hi all,
I am writing to volunteer as a maintainer for this project to ensure it stays compliant and active.
Last year I authored PR #36 ("Upgrade to terraform confluent provider v2"), which addressed a need for the organization I work for, but also the community. @jaylevin merged this PR, but it seems the project has struggled with regular maintenance and release cycles recently. I noticed @haarchri had to step in yesterday (01/20) to cut the release as others were unavailable.
My background is in Java app development, but I've shifted more into cloud and infrastructure in the past couple of years. I have not been a maintainer on an open source project before, but I feel as though I could be helpful here.
I would be happy to:
Could the Steering Committee or maintainers (@haarchri, @jtucci, @jaylevin) please let me know whether this is something this project would consider and what the process might be for formalizing this? I want to make sure this repository avoids being archived and continues to serve the community.
Thanks!
bisbeb commentedon Aug 25, 2026
Hi all,
I'd like to add my name as a volunteer co-maintainer for this provider.
Background: I operate Confluent Platform and Crossplane in production and have been following this repo for a while. I opened PR #47 (IdentityPool resource) a few months ago and have not received a review, which is what brought me here. The state of this provider directly affects our production infrastructure — we are currently evaluating whether to fork and maintain it internally, but co-maintaining the upstream community repo would be the far better outcome for everyone.
I am not a Go expert, but I understand the upjet pattern well enough to add resources, review PRs from an operator's perspective, and help keep the repo in compliance. I am happy to do the unglamorous work: reviewing incoming PRs, triaging issues, and helping the repo respond to the governance requirements in this issue.
If the current maintainers (@jtucci @jaylevin) are no longer able to invest time here, I would be glad to take over or share the responsibility — whatever the Crossplane steering committee recommends as the right process.
@jbw976 — is there a formal process to request maintainer access for community extension projects like this one?
jtucci commentedon Aug 25, 2026
Chiming in as one of the listed maintainers. The team @jaylevin and I were on when this provider was built has since been dissolved. I'm still active in the Crossplane community, but I no longer have any work touching Confluent, which is why PR #47 and the issue queue have gone unreviewed. Apologies for that.
I don't think I have access to control the maintainers list so that is something @jbw976 or @haarchri would need to help out with.
jbw976 commentedon Sep 8, 2026
Awesome, thank you for the updates on this issue everyone! it would be great to have @bisbeb to step up and become a maintainer for a provider they are depending on so this provider gets some more love and maintenance. I can open a PR to add you to the maintainers list.
@jtucci do you still want to stay involved here? if not, then perhaps we can go ahead and move you and @jaylevin to emeritus status for this provider? i can do that in the same PR if that's the way you want to go. your participation in the rest of the community is still very much appreciated 😉
@dzmoore do you still have interest in helping to maintain this provider also? sorry for missing your earlier volunteering 🥲
jbw976 commentedon Sep 8, 2026
I've opened #51 with some changes to OWNERS.md so far - let's see if @jtucci @jaylevin want to stay on the maintainer team going forward or be moved to emeritus.
dzmoore commentedon Sep 8, 2026
Hey @jbw976 - no worries at all! Yes, I'd be happy to help. I manage several control planes running this provider and I've developed several compositions leveraging MRs from this provider.
bisbeb commentedon Sep 20, 2026
Hi @jbw976 - were do we stand with this PR. Ready to be merged?
jbw976 commentedon Oct 16, 2026
Alrighty, #51 has been merged and I've sent invites to @bisbeb and @dzmoore to join as collaborators on this repo with maintainer permissions.
Please let me know if you all need any support to get this repo/project compliant with the community extension project policies in https://github.com/crossplane/crossplane/blob/main/GOVERNANCE.md#policies-for-community-extension-projects.
Thank you for your service to the community! 🙇♂️
bisbeb commentedon Oct 18, 2026
Hi @jbw976, thanks for the invite and for merging #51. I accepted the maintainer role and wanted to give a short status update, since this issue has been quiet for a while.
Where we stand against the policies
crossplane/.project(maintainers.yaml) matches.xpkg.upbound.io/crossplane-contrib. We still need to add publishing toghcr.io/crossplane-contrib. I'll look into this and may need your help with the package permissions on the org side.e2e,backportandtagworkflows have been failing, because they still referenceupbound/uptest, which has since been renamed toupbound/official-providers-ci. I'll fix this first, since the tag workflow is needed for releases.What comes next
I'll post a full self-assessment on this issue once the first steps are done. Happy to hear if you see anything else we should prioritize.
bisbeb commentedon Oct 22, 2026
Status update from the new maintainer team (OWNERS.md was updated in #51).
Progress towards the audit points:
ghcr.io/crossplane-contrib, modeled on provider-keycloak.xpkg.upbound.iobecomes an optional mirror that is skipped when the Upbound credentials are not configured.CODEOWNERSfile,SECURITY.md,CONTRIBUTING.md(including DCO), and README install instructions that no longer point to the Upbound Marketplace.One blocker: my account (
bisbeb) currently only has read access on this repo, so #52 comes from my fork and I can't publish a release yet. @jbw976 could an org admin grant write access to the maintainers listed in OWNERS.md, or tell me which team or process (e.g. thecrossplane/.projectmaintainers file) will do that? Thank you!