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

Graduate from incubator #4

Closed
1 of 6 tasks
ConnorDoyle opened this issue Aug 31, 2016 · 5 comments
Closed
1 of 6 tasks

Graduate from incubator #4

ConnorDoyle opened this issue Aug 31, 2016 · 5 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@ConnorDoyle
Copy link
Contributor

ConnorDoyle commented Aug 31, 2016

Criteria for graduating from the incubator.

Incubation date: 29 August 2016
Incubation deadline: 29 August 2017

When the OWNERS of the Incubator project determine they have met the criteria to graduate they should contact their Champion and Sponsor to discuss. If both the Sponsor and Champion agree that the above criteria have been met the project can graduate to become a Kubernetes Community Project and exit the Kubernetes Incubator.

TODO: Link sub-issues to gather evidence for each topic below.

  • Documented users: the project tracks evidence from downloads, mailing lists, Twitter, blogs, GitHub issues, etc that the project has gained a user base.
  • Regular releases: the project is making releases at least once every 3 months; although release should happen more often.
  • Incubation time: a minimum of 6 months has passed since incubation (March 2017)
  • Healthy community: a healthy number of users, contributors, and/or OWNERS outside of your own company have participated in the project. The Sponsor and Champion can make this call.
  • Roadmap: A roadmap for the next release is maintained; this can be in the form of a doc, GitHub milestones, or any other tool but it must be documented in the README.
  • An announcement of graduation must be sent to the kubernetes-dev@googlegroups.com mailing list by the Champion.
@ConnorDoyle ConnorDoyle added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 29, 2016
@ConnorDoyle
Copy link
Contributor Author

#40 first tagged release

@ConnorDoyle
Copy link
Contributor Author

self-identified users on the project wiki

@ConnorDoyle
Copy link
Contributor Author

Milestones are used for roadmap tracking, noted in the README.

@taylorm10
Copy link

Index of blog posts on the project wiki

@marquiz
Copy link
Contributor

marquiz commented Nov 28, 2018

NFD was migrated to kubernetes-sigs organization. We're not aiming for kubernetes core, anymore. Closing this issue now.

@marquiz marquiz closed this as completed Nov 28, 2018
ArangoGutierrez pushed a commit to ArangoGutierrez/node-feature-discovery that referenced this issue Nov 18, 2020
…tion

source/cpu: Add CPU support for IBM Power LE & Z
cynepco3hahue pushed a commit to cynepco3hahue/node-feature-discovery that referenced this issue Nov 24, 2020
e0ne added a commit to adrianchiris/node-feature-discovery that referenced this issue Feb 3, 2021
e0ne added a commit to adrianchiris/node-feature-discovery that referenced this issue Feb 3, 2021
Signed-off-by: Ivan Kolodyazhny <ikolodiazhny@nvidia.com>
e0ne added a commit to adrianchiris/node-feature-discovery that referenced this issue Feb 5, 2021
Signed-off-by: Ivan Kolodyazhny <ikolodiazhny@nvidia.com>
swatisehgal referenced this issue in k8stopologyawareschedwg/node-feature-discovery May 13, 2021
Get Topology Manager policy from configz-endpoint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

3 participants