-
Notifications
You must be signed in to change notification settings - Fork 984
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
Added PR Review Policy #16280
Added PR Review Policy #16280
Conversation
Jenkins BuildsClick to see older builds (16)
|
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.
👍 👍
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.
All looks good to me.
Just one thing, if it is possible to make the "policy" part a bit more concise would be better I think. (there are in total 18 main and sub-points -- people may skip reading them)
@OmarBasem That is a good point, I'll make a change to highlight the main 3 points of the policy. Something like: Main points
Fully policy
|
doc/pr-review-policy.md
Outdated
|
||
The two principles of demand and supply control are underpinned by an honour system and are useless without honest action. | ||
If a team member does not honestly manage their review bandwidth this action seriously damages the collective balance of | ||
PR preview load. Because of this potential damage a breach of the honour system is considered a deeply shameful act. |
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.
PR preview? is this a typo?
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.
Ah, thank you. That is a tpyo. I will amend
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.
Well documented 🫡
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.
Wow, such a nice and well written doc in the spirit of a true open-source project. Thank you @Samyoul
327d782
to
379a835
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 taking this initiative @Samyoul !
7d46c90
to
33986cf
Compare
33986cf
to
325d0a8
Compare
* Added PR Review Policy * Reformat of Policy section to headline with policy fundementals * Renaming code owner to requester
* Added PR Review Policy * Reformat of Policy section to headline with policy fundementals * Renaming code owner to requester
What's changed
I've written up a policy document following from the great Council and Mauve Council of Deadwater.
The contents of this policy document is the product of 2 councils of the Status Mobile team, the below documents summarise the topics and outcomes of the councils:
The aims of the council were to allow developers that are relied on heavily for reviews to better balance their time
between reviews and other responsibilities. Equally, the council aimed to give other team members better opportunity and
understanding that giving PR reviews is a requirement and will help the team generally if more review burden is shared.
Human readable version is here
Why Change
So that we have a PR review policy that brings balance