Identifying "good first bugs"

In order to make it easier for newcomers to the Fluid Community to contribute code to Infusion, we'd like to label some of our JIRA issues as "good first bugs." We need to review existing open JIRAs and decide which ones would make a good first bug. We've drafted the criteria outlined below.

JIRA label text: good_first_bug

Criteria

• easy to fix
• substance to result i.e. it makes a difference
• not blockers or critical (because we shouldn’t wait for a newcomer to pick it up)
• not renderer, not deprecated things (waste of time to learn)

Examples

• updating code to use best practices, such as:
  • convert free functions to invokers
  • attaching listeners properly
  • converting things to use listeners
• styling fixes (things that look broken)
• broken demos
• documentation (intermediate?)
• creating new examples (intermediate?)
• removing deprecated stuff if the time is right (e.g. lightbox)
• enhancements to build scripts 

Reviewing and labelling issues

To ensure that we don't waste time with multiple people reviewing the same JIRAs, we need a way to identify what has been reviewed already.

JIRA filters

good first bugs:

 

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due

Loading...

Refresh

All current open issues: