a guest Jun 27th, 2019 61 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ## Prerequisites
  3. - Be familiar with,, git workflow, code of conduct, and review process (i.e., read this document)
  4. - Be familiar with or willing to learn about the part of the project related to the PR you're reviewing
  5. - Have previously participated in PR review discussions, and/or have previous PR review experience
  6. - Good communication skills and lots of patience :)
  8. ## Overview
  10. The major tasks for a reviewer are:
  12. 1. Determine whether a PR has merit, and if so, determine what steps are needed to merge it. This may require reading code, running tests, and requesting information or action from the PR author.
  14. 2. Communicate clearly about task (1) with PR authors and other collaborators. This includes effectively using labels, milestones, and projects, triaging spin-off discussions that may result from a PR review, and giving PR authors accurate and direct instructions when needed.
  16. 3. Make SuperCollider an enjoyable project to contribute to. This includes being friendly and respectful toward PR authors and other collaborators, being transparent about project rules and procedures, and making sure PRs you review are merged or closed in a timely manner.
  18. ## Quick checklist
  20. This is meant as a reference checklist of the bare minimum of things to check before approving or merging a PR.
  22. - Is CI (continuous integration) passing? If not, why? If a build failure is the PR author's fault, inform them; otherwise, restart the job or ask another project member for advice.
  24. - Review the changes. Do they reflect the stated intent of the PR? Review the quality of the code including comments, style, naming, correctness, and general code cleanliness. If needed, build the branch yourself and thoroughly test it. For a complicated or subtle change, don't hesitate to ask the PR author to explain how they tested their branch (and be skeptical if they haven't).
  26. - Check the commits. It's not uncommon for a simple change to end up being split across several commits due to the review process. Request that the PR author squash their commits, or use the "Squash merge" option instead of "Create merge commit" option when merging the PR.
  28. - Check the branches. Is the PR being made to the right branch? Let the PR author know they shouldn't be submitting PRs from their fork's release or develop branches. Request a rebase or add the PR to the "PRs to Cherry-Pick" project if necessary.
  30. - Does the PR need documentation?
  32. - Does the PR need tests? Are any new tests thorough enough, and do they follow our guidelines [link]? Unfortunately, tests written in SC don't currently run in CI, so those need to be checked manually by at least one reviewer. Talk to Brian H (@brianlheim) if you want to help fix this!
  34. ## How to get started as a reviewer
  36. 1. Make sure you meet all the prerequisites listed above. We won't quiz you, but it's important that we're all on the same page to avoid unnecessary misunderstandings or disagreements during reviews.
  38. 2. Reach out to an active project maintainer. Brian H (@brianlheim) and Nathan H (@snappizz) are two such people who are usually reachable via email or Slack. You can also reach out to the general developer community on a more public forum, such as the sc-dev mailing list.
  40. 3. We'll give you permissions so that you can review and merge PRs.
  42. 4. Find a PR that interests you and start reviewing!
  44. ## Various instructions/guidelines
  46. ### Using labels, milestones and projects
  48. (Is this already documented somewhere/do we have any real procedures for this?)
  50. ### Guideline: Ask questions
  52. If you don't know how to review a PR, or have a question about reviewing, ask a more experienced contributor! These are opportunities to improve our process and identity additional project issues or feature ideas.
  54. ### Guideline: It's OK to make mistakes
  56. Pressing the "Merge" button can be pretty stressful the first few times you do it, but don't worry about making mistakes. The main branches of the SuperCollider project are heavily protected against truly disastrous errors, and everything else is easily reversible.
  58. ### Guideline: Reviewer time is valuable
  60. This project is fortunate enough to suffer from too many interested contributors. Naturally, there are only so many hours in the day, and therefore only so many PRs that can be reviewed and merged. Whenever possible, request that the PR author themselves take any actions necessary to improve their PR to a mergeable state. If the author indicates they can't or don't know how to perform a task, only then is it appropriate for you or another project member to give them further help or to perform the task for them. One exception is that for first-time or inexperienced contributors who may be unfamiliar with our processes, it's a nice idea to offer additional advice or assistance so that contributing doesn't appear quite so overwhelming.
  62. ### Guideline: Assume good faith
  64. Given no evidence to the contrary, assume that a PR author is acting out of a genuine interest to improve this project. English may not be their first language, and so they may have difficulty understanding technical language or providing all the information we normally like to see in a PR. Be patient and communicate transparently with PR authors; even if it's obvious from the start that the PR will not be merged.
  66. ### Guideline: Stay on topic
  68. In the course of a PR, auxiliary discussions may arise about newly discovered issues, desired features, or even procedural (meta-review) topics. It is crucial that such discussions don't get in the way of reviewing the PR at hand. Any discussion not related to the PR should be respectfully but rapidly relocated to a more appropriate venue; this may be a new PR, an issue ticket, or a discussion thread on some other forum.
  70. ---
  72. thoughts
  74. - reviewers should be a separate team with write access (but not admin)
  75. - should really clean up/clarify teams
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand