Services and Requests
- GitHub requests
- Communication platform and services
NOTE: If you are an existing member of the kubernetes org, you are not required to apply for org membership in another Kubernetes org, such as kubernetes-sigs. Instead, open a pull request to the kubernetes/org repo adding yourself a member of the other org.
GitHub team membership changes should be made by directly opening a pull request against the kubernetes/org repo, updating the desired team.
Repo requests require approval from the owning SIG leads, or in some instances, community members that are granted permission to request repos on behalf of a subproject.
Donated repos, or repos that were originally created outside the project have some additional requirements that must be satisfied before they can be transferred to a Kubernetes project owned GitHub organization.
For more information, see the Kubernetes GitHub Repository Guidelines.
Communication platform and services
Contributor communication requests, such as tweets ([@k8contributors]), blog posts, editorial support, promotion requests, or announcements can be made by filling out the Contributor Comms Request form in the kubernetes/community repo.
Mailing lists are largely intended for community groups, but are available for subprojects if the need arises. These groups should be made following the community mailing list creation procedure. With the subproject’s entry in sigs.yaml, being updated with the new mailing list.
Public Slack channels and user groups may be requested by opening a pull request updating the slack-config in the kubernetes/community repo. Slack channels must adhere to some common-criteria to be added. As an example, project focused channels must be for an Open Source project and not a private commercial one.
For more information, see the Slack Guidelines.
The Kubernetes project has access to the CNCF SurveyMonkey account for creating community surveys, and SIG-Contributor Experience includes people who can give advice on improving the quality of surveys, as well as promote them. Requests can be made using the Community Survey Request form in the kubernetes/community repo.
For additional information, on survey services, see the community Survey request guidelines.
For more information, see the YouTube guidelines.
Zoom meetings requests should be made to the owning community group leads. They are responsible for the creation and posting of the meeting to the group’s mailing list.
For more information, see the Kubernetes Zoom guidelines.
Official Kubernetes subprojects can request a domain and site hosting for their project specific documentation. The Kubernetes community has standardized on Netlify for this purpose.
Requesting a site requires three things:
- Configuring a site and it’s corresponding config within the repo.
- Opening a Netlify Site Request in the kubernetes/org repo.
- Opening a corresponding pull request or issue adding the domain in the kubernetes/k8s.io repo.
There are some specific formats and guidelines around some of these items, they can be be reviewed in the Netlify subproject site guidelines.
Items that are covered fall largely into one of four categories:
- Infrastructure: testing infra, video conferencing, mailing lists, domains, etc
- Events: SIG face-to-face meetings, developer summits, etc
- Consulting services: docs writers, security auditors, etc
- Community Gifts: swag codes, thank you cards, etc
For more information on funding requests, see the Project Funding page.
Was this page helpful?