parse-community / parse-community/parse-server

Introduce PR review policy

Open
#7,171 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:meta
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

New Feature / Enhancement Checklist
Current Limitation

Active contributors are the heart beat of any open source project. As such, their contributions and investments of time deserve timely feedback.

Currently there is no guideline regarding PR reviews that determines the time frame in which PRs are reviewed and feedback is given. This leads to:

  • Additional work for PR author to resolve merge conflicts due to regular PRs, e.g. Snyk.
  • Contributors may become demotivated by not getting a review within reasonable amount of time; a review takes maybe 5-15 minutes while a PR often takes hours of work.
  • Improvements of product, docs and frameworks are unnecessarily delayed.
  • PRs are more likely to be abandoned due to low feedback frequency.

It is also not clear who to tag for review, as there are multiple members in each repo group, some of which do not seem to be active anymore.

Feature / Enhancement Description
  • Introduce a review policy that aims to provide feedback on PRs within a defined amount of time.
  • Actively recruit and onboard new repo team members to increase review capacity.
  • Update team members of repo group, e.g. @ parse-community/server and set a guideline to tag the server group instead of individual members, so that review load is better distributed among reviewers.
Example Use Case

(none)

Alternatives / Workarounds

(none)

3rd Party References

(none)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's contribution and security guidance, including SECURITY.md and the linked support guidance, then examine how the @parse-community/server repo group is maintained. Define the review response timeframe, reviewer-tagging guidance, and team-member onboarding expectations, and document the policy where contributors can find it.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.