Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Repository is missing contributor docs #7

Open
usrbinkat opened this issue Nov 25, 2021 · 6 comments
Open

[DOCS] Repository is missing contributor docs #7

usrbinkat opened this issue Nov 25, 2021 · 6 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@usrbinkat
Copy link

Problem: goals, non-goals, image publishing minimum standardized requirements, and outcomes are un-disclosed blocking community contribution confidence

Proposal:

  1. Establish documentation describing repository purpose and over arching outcome objectives
  2. Establish criteria for new image contribution acceptance
  3. Document contributor guidelines
@rmohr
Copy link
Member

rmohr commented Nov 26, 2021

@usrbinkat here a first draft on what I would see as required to onboard containerdisks. I also try to outline some future development there: https://github.com/kubevirt/containerdisks/pull/8/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

Happy to get your feedback.

@usrbinkat
Copy link
Author

@rmohr you guys have accelerated down that path insanely fast. bravo. My golang skills arent up to par yet. Once that is merged in I'll give it a run and then PR docs enhancement where I can.

@rmohr
Copy link
Member

rmohr commented Nov 30, 2021

@rmohr you guys have accelerated down that path insanely fast. bravo. My golang skills arent up to par yet. Once that is merged in I'll give it a run and then PR docs enhancement where I can.

PR is in. Looking forward to your work :)

@kubevirt-bot
Copy link
Contributor

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

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2022
@kubevirt-bot
Copy link
Contributor

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

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 30, 2022
@rmohr
Copy link
Member

rmohr commented Mar 31, 2022

/remove-lifecycle rotten
/lifecycle frozen

@kubevirt-bot kubevirt-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants