-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
docs: Split, update, improve the contributing guide for reviewers and committers #27085
Conversation
4b2161d
to
bafdf45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this @qmonnet ❤️! This looks great! There are a couple of places that I think need some more background information to help users, but other than that I just have a bunch of nits on sentence structure, word choice, and voice. Also, IMO I think we should try to avoid using parentheses when possible, and there are a lot of parentheses used in these changes, so I made some suggestions on rephrasing things to remove them.
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with regards to rotations and structure. I did a quick read of the whole text and didn't find any issues to highlight.
bafdf45
to
d3dc717
Compare
352d5d5
to
16d9a7d
Compare
16d9a7d
to
f5083d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome looks great! Thank you!
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
f5083d4
to
b4bac5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@qmonnet Thank you so much for this! I have some wording suggestions and another plea to use sentence casing for headings. 🙏🏻
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
b4bac5b
to
ff7bf63
Compare
Silly me, I forgot to Cc @joestringer, who of course has been taking good care of documentation as well 🙀. Apologies, Joe! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, couple of minor nits and one potential content change that should maybe be handled separately to avoid stacking a subtle process change into this PR which is otherwise general improvements.
Documentation/contributing/development/reviewers_committers/review_process.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/duties.rst
Outdated
Show resolved
Hide resolved
Documentation/contributing/development/reviewers_committers/review_docs.rst
Show resolved
Hide resolved
ff7bf63
to
261155b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates, @qmonnet!
/test |
As discussed by some documentation reviewers, update the style guide to instruct contributors to use sentence case rather than title case on headings in documentation. We don't update the whole documentation, which has never been consistent in that regard. However, we do update the guidance for writing documentation itself, as these pages should set an example for the rest of the docs, and should follow the guidance they set themselves. Suggested-by: Sarah Corleissen <sarah.corleissen@isovalent.com> Signed-off-by: Quentin Monnet <quentin@isovalent.com>
The Contributing guide is long. Big. Huge. Let's make it easier to read by splitting it into three parts: - Guidance for community contributors (remaining on the same page) - Guidance for reviewers and committers, for the review process - Guidance for reviewers and committers, for weekly duties Reference the new pages from the existing one. Apart for title formatting and new reference target, the contents in the new page are unchanged at this stage. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
Minor formatting improvements: avoiding inline link URLs, and re-wrapping the paragraphs, to improve readability of the source for the document. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
Before this commit, the page on weekly duties would contain: - A description of the PR review process duty, which describes much of the PR review process, and should really be in the page dedicated to this process - An outdated description of the other rotations (backporter, janitor). Let's try to improve and update this. First, we move everything related to the review process to the dedicated page. Doing so, we update the contents to remove any reference to a weekly duty, and to keep only the practical aspects of the process. Then, we rewrite the description of the weekly duties: we currently have release manager, backporter, triager, and CI health manager. The description for these roles is rather succinct, because I don't think they are publicly documented anywhere at the moment, but we can improve this in the future. We're also missing a way to identify who are the assignees at this time. As Joe observed, some of these duties do not rotate on a weekly basis; so we also rename the page into "Periodic duties", and update the description accordingly. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
261155b
to
5b4c2a1
Compare
I updated the last paragraph about ready-to-merge docs PRs, in the docs-structure document, now that we can and should run /test |
Add a new document, among the guidance for reviewers/committers, to detail the particularities and expectations for reviewing Pull Requests as a member of the cilium/docs-structure team. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
5b4c2a1
to
534ca1b
Compare
/test |
Easier to review per commit.
Cc @aanm @margamanterola (Contributing guide & weekly duties update)
Cc @learnitall @lambdanis (docs-structure review guide)