publiclab/mapknitter

[Welcoming] Suggest new changes & Report Bugs

Open

#312 opened on Jan 27, 2019

View on GitHubContributor guide
 (0 comments) (3 reactions) (0 assignees)Ruby (203 forks)auto 404
help wantedoutreach

Repository metrics

Stars
 (274 stars)
PR merge metrics
 (PR metrics pending)

Description

(Work in progress! Please help!)

As part of our ongoing work to welcome newcomers, we need people to tell about bugs and suggestion, and troubleshoot the issues they encounter. This will help newcomers get started in a codebase they may not be familiar with!

Find a bug or a suggestion

Whether it is on publiclab.org main website, or in it's editor or any other repository create an issue for it in the respective repository. The issues can be related to

  • Testing
  • Coding bugs
  • Outreach
  • Suggest a design
  • Suggest a new feature
  • Documentation suggestions
  • Documentation errors

Find suitable code links and add them

Add code links to the issues/suggestions if possible See #311 for more detailed stuff.

Contributor guide

Research direction
Explore the repository and identify bugs or suggestions. Check the codebase and existing issues for areas needing improvement.
Tech stack
None
Domain
None
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75