mirror of
https://github.com/krkn-chaos/krkn.git
synced 2026-08-25 09:27:36 +00:00
adding member request information
Signed-off-by: Paige Patton <prubenda@redhat.com> Assisted By: Claude Code:
This commit is contained in:
Paige Patton
committed by
Naga Ravi Chaitanya Elluri
Naga Ravi Chaitanya Elluri
parent
eb2efa84ea
commit
66651e97ca
@@ -0,0 +1,55 @@
|
||||
---
|
||||
name: Maintainer Nomination
|
||||
about: Nominate a contributor to become a Maintainer of the Krkn project
|
||||
title: "Maintainer Nomination: <GitHub handle>"
|
||||
labels: maintainer-nomination
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## Maintainer Nomination
|
||||
|
||||
This issue must be opened by an **existing Maintainer** on behalf of the nominee. Self-nominations are not accepted — reach out to a current Maintainer via Slack or GitHub to discuss before opening this issue.
|
||||
|
||||
---
|
||||
|
||||
## Nominee
|
||||
|
||||
- **GitHub handle:**
|
||||
- **Name:**
|
||||
- **Nominating Maintainer:**
|
||||
|
||||
---
|
||||
|
||||
## Requirements Checklist
|
||||
|
||||
- [ ] Nominee has been an active **Member for at least 6 months**
|
||||
- [ ] Nominee has had **at least 3 non-trivial PRs** merged
|
||||
- [ ] Nominee has reviewed **at least 5 non-trivial PRs** from other contributors
|
||||
- [ ] Nominee has demonstrated ability to mentor contributors and provide constructive feedback
|
||||
- [ ] Nominee has shown a clear understanding of the project's technical direction and goals
|
||||
- [ ] Nominee has read and agrees to the [Code of Conduct](../../CODE_OF_CONDUCT.md)
|
||||
|
||||
---
|
||||
|
||||
## Notable Contributions
|
||||
|
||||
List at least 3 non-trivial PRs the nominee authored that have been merged:
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
## Notable Reviews
|
||||
|
||||
List at least 5 non-trivial PR reviews the nominee participated in:
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
4.
|
||||
5.
|
||||
|
||||
## Nomination Summary
|
||||
|
||||
Explain why this contributor is ready for the Maintainer role:
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: Member Application
|
||||
about: Apply to become an official Member of the Krkn project
|
||||
title: "Member Application: <your GitHub handle>"
|
||||
labels: member-application
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## Member Application
|
||||
|
||||
Please fill out the sections below and check off each requirement you have met before submitting.
|
||||
|
||||
---
|
||||
|
||||
## Requirements Checklist
|
||||
|
||||
- [ ] I have been actively contributing to Krkn for **at least 3 months**
|
||||
- [ ] I have had **at least 3 non-trivial PRs** merged
|
||||
- [ ] I have reviewed **at least 5 PRs** from other contributors
|
||||
- [ ] I am familiar with the project's coding style, testing practices, and documentation standards
|
||||
- [ ] I have read and agree to the [Code of Conduct](../../CODE_OF_CONDUCT.md)
|
||||
|
||||
---
|
||||
|
||||
## Merged PRs
|
||||
|
||||
List at least 3 non-trivial PRs you authored that have been merged:
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
## PR Reviews
|
||||
|
||||
List at least 5 PR reviews you participated in:
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
4.
|
||||
5.
|
||||
|
||||
## About Your Involvement
|
||||
|
||||
Briefly describe how you have been contributing to the project and why you would like to become a Member:
|
||||
|
||||
@@ -57,6 +57,57 @@ Refer to the docs below to be able to test your own images with any changes and
|
||||
- [Contribute - Git Pointers](https://krkn-chaos.dev/docs/contribution-guidelines/git-pointers/)
|
||||
- [Testing Your Krkn-hub Changes](https://krkn-chaos.dev/docs/developers-guide/testing-changes/)
|
||||
|
||||
## Joining the Contributor Ladder
|
||||
|
||||
The following explains how to formally join the Krkn community at each level of the contributor ladder. For a description of what each role entails, see [GOVERNANCE.md](GOVERNANCE.md) and [MAINTAINERS.md](MAINTAINERS.md).
|
||||
|
||||
### Contributor
|
||||
|
||||
**Anyone who participates in the project is a contributor.** There is no application required — opening an issue, submitting a PR, reviewing someone else's work, improving documentation, or helping others in Slack all count.
|
||||
|
||||
To get started:
|
||||
1. Find something to work on in the [open issues](https://github.com/krkn-chaos/krkn/issues?q=is%3Aissue+state%3Aopen+label%3A%22good+first+issue%22), or open one of your own.
|
||||
2. Join the [#krkn channel on Kubernetes Slack](https://kubernetes.slack.com/archives/C05SFMHRWK1) to introduce yourself and ask questions.
|
||||
|
||||
### Member
|
||||
|
||||
Members are active contributors who review PRs and have demonstrated a solid understanding of the project's codebase and conventions.
|
||||
|
||||
**Requirements** — before applying, you should have:
|
||||
- Been actively contributing for **at least 3 months**
|
||||
- Submitted **at least 3 non-trivial PRs** that have been merged
|
||||
- Reviewed **at least 5 PRs** from other contributors
|
||||
- Shown familiarity with the project's coding style, testing practices, and documentation standards
|
||||
|
||||
**How to apply:**
|
||||
1. Open a [Member Application issue](https://github.com/krkn-chaos/krkn/issues/new?template=member_request.md) and complete all sections.
|
||||
2. Tag two current Maintainers to review your application.
|
||||
|
||||
Maintainers will evaluate the application and respond within **two weeks**. A simple majority vote of Maintainers is required for approval. Once approved, you will be added to [MAINTAINERS.md](MAINTAINERS.md) and granted the appropriate repository permissions.
|
||||
|
||||
### Maintainer
|
||||
|
||||
Maintainers are responsible for the overall health and direction of the project. They have write access to the repository and can merge pull requests.
|
||||
|
||||
**Requirements** — before applying, you should have:
|
||||
- Been an active **Member for at least 6 months**
|
||||
- Performed reviews for **at least 5 non-trivial pull requests**
|
||||
- Contributed **at least 3 non-trivial pull requests** that have been merged
|
||||
- Demonstrated the ability to mentor contributors and provide constructive, timely feedback
|
||||
- Shown a clear understanding of the project's technical direction and goals
|
||||
|
||||
**How to apply:**
|
||||
|
||||
Maintainer nominations are peer-driven — an existing Maintainer must sponsor your application.
|
||||
|
||||
1. Reach out to an existing Maintainer (via Slack or a GitHub issue) and ask them to nominate you.
|
||||
2. The sponsoring Maintainer opens a [Maintainer Nomination issue](https://github.com/krkn-chaos/krkn/issues/new?template=maintainer_request.md) and completes all sections.
|
||||
3. The Maintainer Council votes on the issue or at the next monthly meeting. A **simple majority** is required for approval.
|
||||
|
||||
Once approved, you will be added to [MAINTAINERS.md](MAINTAINERS.md), granted write access to the repository, and invited to the maintainer mailing list.
|
||||
|
||||
**Stepping down:** To request removal from any role, see the "Requesting Removal" section in [GOVERNANCE.md](GOVERNANCE.md).
|
||||
|
||||
## Questions?
|
||||
|
||||
Reach out to us on slack if you ever have any questions or want to know how to get started. You can join the kubernetes Slack [here](https://communityinviter.com/apps/kubernetes/community) and can join our [Krkn channel](https://kubernetes.slack.com/archives/C05SFMHRWK1)
|
||||
|
||||
+3
-1
@@ -100,7 +100,9 @@ Maintainers may also be removed for inactivity, failure to fulfill their respons
|
||||
|
||||
A Maintainer may be removed at any time by a 2/3 vote of the remaining Maintainers.
|
||||
|
||||
Depending on the reason for removal, a Maintainer may be converted to **Emeritus** status. Emeritus Maintainers will still be consulted on some project matters and can be rapidly returned to Maintainer status if their availability changes.
|
||||
### Requesting Removal
|
||||
|
||||
To request your own removal from the Maintainer role, send an email to the [maintainer mailing list](mailto:krkn.maintainers@gmail.com) or open a PR removing yourself from [MAINTAINERS.md](MAINTAINERS.md). No vote is required for a voluntary resignation — a maintainer will merge the PR on your behalf.
|
||||
|
||||
## Meetings
|
||||
|
||||
|
||||
@@ -16,6 +16,7 @@ For detailed description of the roles, see [Governance](./GOVERNANCE.md) page.
|
||||
| Paige Patton | [paigerube14](https://github.com/paigerube14) | prubenda@redhat.com | Maintainer |
|
||||
| Tullio Sebastiani | [tsebastiani](https://github.com/tsebastiani) | tsebasti@redhat.com | Maintainer |
|
||||
| Yogananth Subramanian | [yogananth-subramanian](https://github.com/yogananth-subramanian) | ysubrama@redhat.com | Maintainer |
|
||||
| Darshan Jain | [ddjain](https://github.com/ddjain) | nnd.darshan@gmail.com | Maintainer |
|
||||
| Sahil Shah | [shahsahil264](https://github.com/shahsahil264) | sahshah@redhat.com | Member |
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user