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

DOC: update contribution guidelines #3813

Merged
merged 2 commits into from
Mar 30, 2022

Conversation

neutrinoceros
Copy link
Member

PR Summary

This is aimed at fixing #2554
what's missing still is a link to the document where we define the number of reviews needed for all kinds of PRs, because I couldn't find it back.
Keeping this as a draft until then

@neutrinoceros
Copy link
Member Author

found the document I had in mind: https://github.com/yt-project/governance/blob/7e8793735f067f2681966ea0e848d542a813b1aa/source/voting.rst
However, I didn't find where this was being deployed outside Github. On second thought I'm not convinced that the number of reviews required for PRs is really something the target audience (new contributors) needs to care about, so I think I'll just avoid bloating the docs with it.

@neutrinoceros neutrinoceros marked this pull request as ready for review February 16, 2022 21:55
@neutrinoceros neutrinoceros linked an issue Feb 16, 2022 that may be closed by this pull request
@matthewturk
Copy link
Member

This is good but to be honest, I sometimes worry that the terseness of our language is off-putting.

matthewturk
matthewturk previously approved these changes Feb 17, 2022
CONTRIBUTING.rst Outdated Show resolved Hide resolved
Co-authored-by: Matthew Turk <matthewturk@gmail.com>
@matthewturk matthewturk merged commit 38cdc31 into yt-project:main Mar 30, 2022
@neutrinoceros neutrinoceros deleted the update_contribution_guide branch March 30, 2022 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ensure release and development directions are consistent
2 participants