garris/BackstopJS

Help wanted -- need reviewers!

Open

#375 opened on Jan 13, 2017

View on GitHub
 (23 comments) (4 reactions) (0 assignees)JavaScript (6,510 stars) (601 forks)batch import
help wanted

Description

Hey there BackstopJS devs!

BackstopJS has officially outgrown my ability to maintain it on my own!

There is currently a small backlog of excellent PR contributions in need of thoughtful 👀 . If you have a working pair of code-eyes and also have a desire to help improve BackstopJS, then please by all means comment here or contact me directly: garris@me.com.

To all the devs waiting for reviews -- I am truly grateful for your effort and also truly sorry I haven't been able to give a proper review! You deserve better. Thanks for your patience -- we'll get this log-jam sorted out as soon as possible!

Just to be clear, it's a pro-bono deal -- but hey, you'd be contributing to developer happiness all over the world -- so that's something! 😇 And also you'd of course be honorably listed as a core member on the main page.

Cheers. @garris

Contributor guide

Tech stack
javascriptnodejs
Domain
testing
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the open pull requests in the BackstopJS repository (https://github.com/garris/BackstopJS/pulls). Identify PRs that have not received reviews. For each PR, understand the changes by reading the code and description, run the tests locally, and provide feedback. If unsure about any aspect, ask questions in the PR or in this issue. Prioritize PRs that address common bugs or feature requests. Coordinate with the maintainer (@garris) to ensure coverage.