Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up Project Board/Issues #704

Open
12 of 18 tasks
lasryariel opened this issue May 31, 2024 · 0 comments
Open
12 of 18 tasks

Clean up Project Board/Issues #704

lasryariel opened this issue May 31, 2024 · 0 comments
Labels
Feature: Administrative Administrative chores, etc... points: 3 Can be done in 13-18 hours Role: PM
Milestone

Comments

@lasryariel
Copy link
Member

lasryariel commented May 31, 2024

Overview

We need to clean up our Project Board and Issues for clarity on what is being worked on and to prepare for the Github Projects Migration

Action Items

Issues

  • Check that all issues are formatted properly
    • If an Issue is not properly formatted, label should be "Draft".
    • Proper Format should use "Blank Issue" template
  • Recruitment Issues: should be similar to On/Offboarding: need documentation for how to manage, here is a link to an example I think: Recruit: data analyst internship#154

Milestones

  • Add a Milestone for Legal Compliance - completed by Ariel 5/31
  • Move anything that is not for MVP to Post-MVP
  • Document Milestone Use in Wiki

Labels

  • Create the following labels "Ready for [Product, Research Lead, Design Lead, Development Lead]" completed by Ariel 5/31
    • start Using these labels for any issues that needs to be cleaned up before it is ready to be put into prioritized backlog
    • For any issues that are using "ready for" labels that have questions, move to "Blocked" column
      • completed by Ariel 5/31. Note that we are using "For Review/Feedback Needed" instead of "Blocked" column
  • Add Complexity label based on github.com//hackforla/website/labels?q=complexity
  • Use these points labels as well as a guide: https://github.com/hackforla/website/labels?q=size
  • If an Issue is not properly formatted, label should be "Draft".
  • Document Label Use in Wiki
Roles
  • Create 2 new roles - 1 for design and 1 for research - completed by Ariel 5/31
    • Split out UI/UX between those 2 roles Issues
  • There should only be one role on any given issue
  • Document Roles Use in Wiki

Columns

  • Document Columns Use in Wiki
Icebox:
  • All issues in icebox should have a dependency issue that is a blocker to let us know when the issue will come out of the icebox
  • Icebox Issues should not have an assignee - Completed by Ariel 5/31

Resources/Instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Administrative Administrative chores, etc... points: 3 Can be done in 13-18 hours Role: PM
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

1 participant