-
Notifications
You must be signed in to change notification settings - Fork 0
Existing Issues Refinement #18
Copy link
Copy link
Open
Labels
Complexity: SmallLow to no complexity, low to no riskLow to no complexity, low to no riskEffort: 3Moderate familiarity with content, multiple clear solutionsModerate familiarity with content, multiple clear solutionsHelp Wanted 🆘Extra attention is neededExtra attention is neededPriority: High ⚠️Requires immediate attentionRequires immediate attentionStack: DevExThis relates to developer experienceThis relates to developer experienceState: ApprovedType: Chore 🧼A more menial taskA more menial task
Milestone
Metadata
Metadata
Assignees
Labels
Complexity: SmallLow to no complexity, low to no riskLow to no complexity, low to no riskEffort: 3Moderate familiarity with content, multiple clear solutionsModerate familiarity with content, multiple clear solutionsHelp Wanted 🆘Extra attention is neededExtra attention is neededPriority: High ⚠️Requires immediate attentionRequires immediate attentionStack: DevExThis relates to developer experienceThis relates to developer experienceState: ApprovedType: Chore 🧼A more menial taskA more menial task
We (primarily @ameliagoodman) need to go through the existing Issues and provide as much context as possible.
This will allow for a lower barrier to entry for anyone looking to contribute.
Backlog refinement should not seek to fill every single section in existing tickets, but rather focus on what context would be useful for someone less familiar with the code. Use the existing sections in each Issue as an optional prompt.