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.

Sign up for GitHub

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

Jump to bottom

Project Health improvements for 2019 H1 #144

Open
7 of 11 tasks
frapposelli opened this issue Feb 15, 2019 · 3 comments
Open
7 of 11 tasks

Project Health improvements for 2019 H1 #144

frapposelli opened this issue Feb 15, 2019 · 3 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
Next

Comments

@frapposelli
Copy link
Member

frapposelli commented Feb 15, 2019 •
edited
Loading

This issue tracks improvements to the health of the vSphere Cloud Provider / CSI project. These improvements are paramount to the success of this project and to foster a healthy community of contributors.

Areas of improvements for 2019 H1:

  • Perform bi-weekly issue grooming instead of monthly.
  • Create a Developer guide to enable new contributors.
  • Work to get more PRs and participation from parties outside of VMware.
  • Make this repo the go-to choice for new Kubernetes users on vSphere.
  • Add a more complete documentation to adhere to Cloud Provider documentation KEP
  • Create a quickstart docs in the repo
  • Continue working on an easy-button deployment model for users.
  • Improve unit tests and integration tests, especially between CCM and CSI.
  • Continue to actively participate in SIG-Cloud Provider
  • Improve release model and automate the release process
  • Work on migrating the CSI project into a dedicate repo for better release process/automation and issue tracking
@fejta-bot
Copy link

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2019
@frapposelli
Copy link
Member Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 7, 2019
@davidkarlsen
Copy link
Member

Cross-linking: helm/charts#19807

@davidvonthenen davidvonthenen added this to the Next milestone Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
5 participants
@davidkarlsen @frapposelli @davidvonthenen @k8s-ci-robot @fejta-bot