summaryrefslogtreecommitdiff
path: root/community-membership.md
AgeCommit message (Collapse)Author
2022-08-19Fixed 2 TyposgtWalker98
Pull Request changed to 2 words Capitalized Hub in GitHub
2022-01-11Update github org membership requirementsBob Killen
Membership across orgs is now equivalent. When joining a Kubernetes GitHub Org, you are now joining the Kubernetes project and have implicit membership in the other active orgs. ref: https://github.com/kubernetes/org/issues/966
2022-01-04Changed all instances of k-dev@ and kubernetes-dev@ to dev@kubernetes.io (#6311)Ayushman
* Changed all instancesof k-dev@ and kubernetes-dev@ to dev@kubernetes.io Changes Removed From archive updated the link changes made csv undo changed links * Fix last two instances of googlegroups.com * Revert changes to election docs for past elections Co-authored-by: Christoph Blecker <admin@toph.ca>
2021-10-05Add membership requirement for merged PRElana Hashman
If PRs are provided as part of a membership application, at least one PR should be merged. Open PRs are not sufficient.
2021-08-09opening issue points to right template, fix template linkNoah Ispas (iamNoah1)
2021-03-03Grammatically updated Community Membership doc (#5479)Mark Paget
* Grammatically updated Community Membership doc * Update community-membership.md Thanks Bob Co-authored-by: Bob Killen <killen.bob@gmail.com> * Update community-membership.md Co-authored-by: Bob Killen <killen.bob@gmail.com>
2020-07-15Update community-membership.mdモハメド
a minor typo
2020-07-13Fix grammar error in community membership guidelinesBob Killen
principal -> principle
2020-07-10Merge pull request #4924 from mrbobbytables/inactive-membersKubernetes Prow Robot
Add section on inactive members to community membership guidelines
2020-07-07Add section on inactive members to community membership guidelinesBob Killen
2020-07-05Update docs to suggest creating PRs in k/org for kubernetes membersNikhita Raghunath
We've had many issues opened in k/org where existing `kubernetes` org members request membership to `kubernetes-sigs`. Under our current policy, all members of `kubernetes` are implicitly eligible for membership to `kubernetes-sigs` and don't require sponsorship. In such cases, we usually ask them to create a PR directly or we create one ourselves and let the requester lgtm it. To ease the often unneccessary two step process, this commit updates community membership guidelines to suggest creating PRs directly if they are existing `kubernetes` members.
2020-06-16Remove outdated collaboration docBob Killen
The contents of collab.md are out of date and the intent of the document is better captured in some of the other docs such as expectations.md[1], pull-requests.md[2] and review-guidelines.md[3]. [1] https://git.k8s.io/community/contributors/guide/expectations.md [2] https://git.k8s.io/community/contributors/guide/pull-requests.md [3] https://git.k8s.io/community/contributors/guide/review-guidelines.md
2019-07-29Update URL to just "expectations" so the URL reads right in the contribJorge O. Castro
guide
2019-02-15Add examples for member sponsorship requirementsNikhita Raghunath
2019-02-14github-management: clarify sponsorship criteriaNikhita Raghunath
An approver/reviewer in @kubernetes, may sponsor someone for the kubernetes org or any of the related organizations (kubernetes-sigs, kubernetes-csi etc); as long as it's a project they're involved with. However, this does not work the other way around. A sponsor that is only an approver/reviewer in kubernetes-sigs cannot sponsor someone for membership in the kubernetes org. They are scoped just to the org they're associated with.
2019-01-15Created tombstone file for /devel/collab.md - updated URL in other fileseduartua
2018-11-02Clarify membership requirements for members of related Kubernetes orgsNikhita Raghunath
2018-09-08Add clarification to requesting Kubernetes org membershipStephen Augustus
* Who approves membership requests * How long membership requests take to process Signed-off-by: Stephen Augustus <foo@agst.us>
2018-08-13Wrap doc at 80 charsChristoph Blecker
2018-08-13Update community membership procedureChristoph Blecker
2018-07-19Clarify membership requirements for related k8s github orgsguineveresaenger
2018-06-29GitHub handle is required at the request bodyIhor Dvoretskyi
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
2018-05-25fixed link to owners in the maintainer sectionteague
2018-04-03fix grammar mistakemahuihuang
2018-03-14Fix broken linksbin liu
2018-03-05Merge pull request #1861 from pwittrock/remove-maintainersk8s-ci-robot
Simplify membership ladder
2018-03-04FixesEllen Körbes
2018-03-04Added privileges to Responsibilities and privileges sectionEllen Körbes
2018-03-01Add section to owners about holistic health of projectPhillip Wittrock
2018-02-28Address PR comments - add context around how to become an OWNERPhillip Wittrock
2018-02-27Remove *maintainer* role and merge into *owner*Phillip Wittrock
2018-02-18changed new contributor linkVaibhav Singh
2018-01-31Remove references to outside collaboratorsChristoph Blecker
2018-01-26fixed links to community expectationsguineveresaenger
2017-12-21Use git.k8s.io for linksChristoph Blecker
2017-11-21members must have sponsors that span organizationsDerek Carr
2017-11-06spell checkwangxinxu
2017-07-27Fix minor typoKiran Ranganath
2017-06-21Update membership sponsor requirements to be from different companies.Phillip Wittrock
2017-06-15Add email template for community-membership requests.Phillip Wittrock
- Also have users confirm they have joined kubernetes-dev@googelgroups.com
2017-06-13Add requirements for outside collaborators. Make membership require ↵Phillip Wittrock
sponsorship from reviewers instead of members.
2017-06-12Change Kubernetes membership to include GitHub org membershipPhillip Wittrock
- Membership includes GH org membership - Requirements and expectations increased due to increased privs - More explanation of sponsorship
2017-05-29Fix "Stack Overflow" across docs.Christoph Blecker
2017-05-26Flesh out community membership roles.Phillip Wittrock
- Reduce bar for org membership - Summarize and provide additional descriptions for roles - Refactor membership doc to explicitly define requirements vs responsibilities and make wording consistent - Delete a bit of the New contributor role that overlaps with org membership
2017-05-12Split governance.md into separate docs.Phillip Wittrock