community
community copied to clipboard
kubevirt
Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.
One of the items on the CNCF Graduation checklist. @davidvossel @vladikr @rmohr @fabiand @stu-gott @vasiliy-ul @rthallisey I think github handle is fine for 'contact information' but we are missing 'domain of responsibility' for you all. Can you please note it here and we can update the maintainer file with a single PR.
@aburdenthehand do you have an example of how other projects scope the responbsibilities?
Envoy, OPA and Argo list them under each person. Conversely, Vitess and Harbor list each person against the area of responsibility.
Keep in mind that this particular checklist is new - I don't think any project has yet been accepted using it, and we'd be one of the first submitting using the checklist from the get-go, though I could be mistaken.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
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-sigs/prow repository.
https://github.com/kubevirt/community/pull/413/files Adds the responsibilities for all maintainers