-
Notifications
You must be signed in to change notification settings - Fork 3
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: add pr-triage.md #39
base: main
Are you sure you want to change the base?
Conversation
|
||
## Objective | ||
|
||
- Lower the time required for the feedback loop to at most 1 week for the biggest PRs, and 3-4 days for the regular ones. |
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.
Your text is good, but for anyone looking but I believe it's important to emphasize that the main goal is to shorten the feedback loop, not just the merging process. Shortening the feedback loop can speed up merging, but it's crucial to maintain quality and ensure reviews by the right code owners are mandatory, especially as time goes on.
Code owners, who may not be employees, are not required to strictly adhere to this employee convention.
We can implement an incentive model in the Review DAO to shorten the feedback loop by offering bonuses based on speed.
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.
I see this proposal as an experiment that we can learn from and iterate, so let's do it now and make tweaks later.
Description