Typos in contributing section
This commit is contained in:
parent
c190b160e9
commit
b5da5760a2
2 changed files with 9 additions and 9 deletions
|
@ -13,14 +13,14 @@ and firmly standing against the elitist closed approach.
|
||||||
Being part of the core team should be accessible to anyone motivated
|
Being part of the core team should be accessible to anyone motivated
|
||||||
and wants to be part of that journey!
|
and wants to be part of that journey!
|
||||||
|
|
||||||
## Onboarding process
|
## Onboarding Process
|
||||||
|
|
||||||
If you consider joining our community please drop us a line using Twitter or leave a note in the issue.
|
If you consider joining our community please drop us a line using Twitter or leave a note in the issue.
|
||||||
We will schedule a quick call to meet you and learn more about your motivation.
|
We will schedule a quick call to meet you and learn more about your motivation.
|
||||||
During the call, the team will discuss the process of becoming a maintainer.
|
During the call, the team will discuss the process of becoming a maintainer.
|
||||||
We will be happy to answer any questions and explain all your doubts.
|
We will be happy to answer any questions and explain all your doubts.
|
||||||
|
|
||||||
## Maintainers requirements
|
## Maintainer's Requirements
|
||||||
|
|
||||||
Note: you do not have to meet all the listed requirements,
|
Note: you do not have to meet all the listed requirements,
|
||||||
but must have achieved several.
|
but must have achieved several.
|
||||||
|
@ -34,7 +34,7 @@ but must have achieved several.
|
||||||
or other technical forums/boards such as K8S slack, Reddit, StackOverflow, hacker news.
|
or other technical forums/boards such as K8S slack, Reddit, StackOverflow, hacker news.
|
||||||
- Have read and accepted the contributor guidelines.
|
- Have read and accepted the contributor guidelines.
|
||||||
|
|
||||||
## Maintainers responsibilities and privileges
|
## Maintainer's Responsibilities and Privileges
|
||||||
|
|
||||||
There are lots of areas where you can contribute to the project,
|
There are lots of areas where you can contribute to the project,
|
||||||
but we can suggest you start with activities such as:
|
but we can suggest you start with activities such as:
|
||||||
|
@ -103,7 +103,7 @@ maintainers' activity and involvement will be reviewed on a regular basis.
|
||||||
non-threatening,
|
non-threatening,
|
||||||
and friendly behavior towards other people on the maintainer team and with our community?
|
and friendly behavior towards other people on the maintainer team and with our community?
|
||||||
|
|
||||||
## Additional comments for (not only) maintainers
|
## Additional Comments for (not only) Maintainers
|
||||||
|
|
||||||
- Be able to put yourself in users’ shoes.
|
- Be able to put yourself in users’ shoes.
|
||||||
- Be open-minded and respectful with other maintainers and other community members.
|
- Be open-minded and respectful with other maintainers and other community members.
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
# Maintainers
|
# Maintainers
|
||||||
|
|
||||||
## The team
|
## The Team
|
||||||
|
|
||||||
* Emile Vauge [@emilevauge](https://github.com/emilevauge)
|
* Emile Vauge [@emilevauge](https://github.com/emilevauge)
|
||||||
* Vincent Demeester [@vdemeester](https://github.com/vdemeester)
|
* Vincent Demeester [@vdemeester](https://github.com/vdemeester)
|
||||||
|
@ -20,15 +20,15 @@
|
||||||
* Kevin Pollet [@kevinpollet](https://github.com/kevinpollet)
|
* Kevin Pollet [@kevinpollet](https://github.com/kevinpollet)
|
||||||
* Harold Ozouf [@jspdown](https://github.com/jspdown)
|
* Harold Ozouf [@jspdown](https://github.com/jspdown)
|
||||||
|
|
||||||
## Maintainers guidelines
|
## Maintainer's Guidelines
|
||||||
|
|
||||||
Please read the [maintainers guidelines](maintainers-guidelines.md)
|
Please read the [maintainer's guidelines](maintainers-guidelines.md)
|
||||||
|
|
||||||
## Issue Triage
|
## Issue Triage
|
||||||
|
|
||||||
Issues and PRs are triaged daily and the process for triaging may be found under [triaging issues](https://github.com/traefik/contributors-guide/blob/master/issue_triage.md) in our [contributors guide repository](https://github.com/traefik/contributors-guide).
|
Issues and PRs are triaged daily and the process for triaging may be found under [triaging issues](https://github.com/traefik/contributors-guide/blob/master/issue_triage.md) in our [contributors guide repository](https://github.com/traefik/contributors-guide).
|
||||||
|
|
||||||
## PR review process:
|
## PR Review Process
|
||||||
|
|
||||||
The process for reviewing PRs may be found under [review guidelines](https://github.com/traefik/contributors-guide/blob/master/review_guidelines.md) in our contributors guide repository.
|
The process for reviewing PRs may be found under [review guidelines](https://github.com/traefik/contributors-guide/blob/master/review_guidelines.md) in our contributors guide repository.
|
||||||
|
|
||||||
|
@ -118,7 +118,7 @@ The `status/*` labels represent the desired state in the workflow.
|
||||||
* `priority/P2`: need to be fixed in the future.
|
* `priority/P2`: need to be fixed in the future.
|
||||||
* `priority/P3`: maybe.
|
* `priority/P3`: maybe.
|
||||||
|
|
||||||
### PR size
|
### PR Size
|
||||||
|
|
||||||
Automatically set by a bot.
|
Automatically set by a bot.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue