chore: moving to the crossplane-contrib org #3
Conversation
Signed-off-by: Theo Chatzimichos <[email protected]>
tampakrap
force-pushed
the
move_to_crossplane-contrib_org
branch
from
b16dd2b
to
dd36c5c
Compare
There was a problem hiding this comment.
awesome!! this visually looks correct to me - we can always make tweaks if publishing doesn't work successfully 😉
I have a new provider-spotify repo created in the marketplace under the crossplane-contrib org and created team/robot/perms/token in the vein of what's described in https://github.com/crossplane/function-template-go/issues/41.
Are you all good now with me overwriting the existing XPKG_ACCESS_ID and XPKG_TOKEN in this repo with their new values?
|
sure, please go ahead! One additional question from my side, do I need to add any additional/fallback owners in OWNERS or CODEOWNERS files? |
|
Secrets for this repo have been updated!
nope, you're the sole maintainer for now 😉 - if more folks get involved and you find they meet your quality bar and will be helpful to the long term sustainability of this repo, then you're welcome to add them as a maintainer then! the fairly strict process for upstream crossplane is captured in https://github.com/crossplane/crossplane/blob/master/GOVERNANCE.md#becoming-a-maintainer, which will give you an idea of the "spirit" for adding a maintainer, but the bar is much lower for community providers than that and the maintainers for each repo can act autonomously there:
|
No description provided.