community
community copied to clipboard
tektoncd
Owning a new Resource in catalog requires that contributor to be part of org
As of now whenever there is a contributor in catalog who wants to own a particular resource, they need to be a part of Tekton org first and then only their OWNERS file is validated. Here is the sample PR https://github.com/tektoncd/catalog/pull/967#issuecomment-1096455206 with such situation. This process basically violates the requirements laid down to be a part of joining the org.
Question: Should we update the requirements for joining the org to include the OWNERS who want to maintain a particular resource? OR Should we change the way of setting up resource OWNERS in catalog? (Basically do some modifications in prow such that it doesn't validate the sub-tree OWNERS file?
/kind question /cc @tektoncd/governing-board
Should we change the way of setting up resource OWNERS in catalog? (Basically do some modifications in prow such that it doesn't validate the sub-tree OWNERS file?
This cannot really work very well. Prow and all automation are enforcing this (for being able to assign or put people as reviewers, …).
Should we update the requirements for joining the org to include the OWNERS who want to maintain a particular resource?
Definitely yes 👼🏼 Because it is in the org, I don't think that's we add people to the org for this. Long term, if/when the Hub allows to register external tekton resources, we could update this process and make sure Tasks in the catalog are maintained by an active group of people, making other resources searchable through the Hub, but maintain by someone else.
Should we change the way of setting up resource OWNERS in catalog? (Basically do some modifications in prow such that it doesn't validate the sub-tree OWNERS file?
This cannot really work very well. Prow and all automation are enforcing this (for being able to assign or put people as reviewers, …).
Should we update the requirements for joining the org to include the OWNERS who want to maintain a particular resource?
Definitely yes 👼🏼 Because it is in the org, I don't think that's we add people to the org for this. Long term, if/when the Hub allows to register external tekton resources, we could update this process and make sure Tasks in the catalog are maintained by an active group of people, making other resources searchable through the Hub, but maintain by someone else.
okay. Will create one to address this.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.