-
Notifications
You must be signed in to change notification settings - Fork 302
Define what approving a PR means #2327
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
Conversation
|
The only thing that's really missing is a bit more reviewers. Cubester, PPPUD, DNin01 specifically are typically busy with personal projects. Don't take this as a call out to remove them, not at all, but they make up a decent chunk of reviewers. |
|
Dm me if you want some decent candidates |
|
Send me some names |
|
|
yeah i would like to do extension reviewing |
|
I'd be down for reviewing extensions! |
CubesterYT
left a comment
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.
Looks great! I agree with SharkPool, some more reviewers wouldn't hurt.
I can confirm this. I agree that we need more reviewers, preferably people who are available during the school year. |
|
@S4IL21 You seem like an interesting person, and this could be a learning opportunity. Maybe you might like to try being a reviewer? You don't have to, but I think that it would be really helpful if you joined. |
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.
These seem like good guidelines for what's generally acceptable.
I do think that for extension reviewers you should provide more detail as to the standard of testing you had to reduce glance-and-approve reviews.
I also tend to agree that the PR library is piling up and we do need more reviewers
I would also like to say that while I'm committed to being a part of Turbowarp for the foreseeable future, I cannot guarantee I'll be chronically online or will not leave the repository in the distant future when bigger commitments override my time for Turbowarp. In the past few weeks I haven't been as active here but I aim to be increasing my time spent on Turbowarp as my outside life gets less busy. I love how you're trying to make Turbowarp less GarboMuffin dependent so it can still run even when you're gone.
DNin01
left a comment
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.
This seems good. One more thing, it might be good to determine the value of a change or feature when reviewing it. For example, if a small, easily reviewable but obscure feature that not many people are interested in (e.g., no reactions on its corresponding issue), we might not want to approve it, just for the sake of not wasting time on/or adding too many features and instead focusing on what matters.
|
Also might want to mention security. |
|
@GarboMuffin If an extension passes the review criteria but has some obvious failure not listed in |
|
If we add more active reviewers, can we increase the minimum approval count to 3? People are quick to approve things and it only takes two people who aren't thinking clearly to cause an issue for everybody. |
I think that depends on the amount of reviewers |
Co-authored-by: DNin01 <106490990+DNin01@users.noreply.github.com>
|
@GarboMuffin Will you still review existing and new PRs that require more critical attention? E.g, the bigger extensions, concerning security issues, sketchy extensions that "work" but achieve functionality in an uncertain/odd manner, etc.? |
6538f37 to
3ca66cb
Compare
Invited. Will consider other mentioned people if they ask.
It's supposed to be covered by "I verified that the extension follows all acceptance criteria and guidelines in CONTRIBUTING.md". I went and put something in there about nothing too niche
I'll mention it
Of course. You can add more beyond just the copied and pasted checklist.
If people actually go through the checklist then hopefully they won't be that quick to approve
Maybe If the block design is odd then don't check the box "I reviewed the block list and believe they are well-designed and intuitive". If you mean that the code is odd then don't check the box "I reviewed the code and believe it is well-written and easy to maintain or extend in the future, even without help from the original author" |
|
2 reviewers also does effectively already mean 3 people since you can't approve your own pr |
|
yolo merge |
|
Helro i was suggested as an ext reviewer yes yes yes also if you got a notif from another account please ignore it im begging you |
Sure |
The people who are not still in their years of academics likely have a job, so really whoever you get is going to be busy some way or another. The way to make more activity and progress is to have all the reviewers turn into full-time Turbowarp volunteers (which is impractical to ask) or just add more reviewers (which is the more realistic solution). |
|
I think it's okay to have people go in and out of being reviewers, so if one person starts working full-time on something else, another can replace them (as long as each member is committed for a little while, like several months or more). |
|
We are NOT adding genix as a reviewer |
What's wrong with them? |
|
@GarboMuffin Your review process says to ping you early and often; should we do this for every extension, only extensions with severe issues, or some other group? |
It says that for things other than listed above in Review Process. The point I implied is that for most things the reviewers should be able to handle it on their own, but for specific niche issues that require Garbo's attention be sure to get his attention respectfully without spamming |
Why not |
I don't really have the time or (more importantly) motivation to review extensions these days.
I've gotten the feedback that reviewers don't merge pull requests because there is no guidance when things are okay to be merged. So I'm trying to define that here.
Here's my idea. We define passing the automated tests + getting two approvals as fully sufficient to be merged. Now just have to define criteria for an approval, so I've written some guidelines and a couple templates to copy and paste into the review comment box. Check all the boxes, then you can approve it. Get two of those, then any reviewer can merge it.
Read the new document. It's not long. Give feedback to refine it. You'll be the ones following it after all