Labels and Milestones - hackforla/website GitHub Wiki
Labels
Each issue will have
- 1 or more stakeholders that need that feature
- 1 or more feature the issue pertains to
Complexity
Frequency
convention is frequency: [OCCURRENCE]
frequency: monthly
frequency: weekly
Misc
Missing
convention is missing: [LABLE TYPE]
missing: feature
missing: milestone
missing: role
missing: size
missing: stakeholder
PII
convention is PII: [TRUE OR FALSE]
PII: FALSE
- Table or function does not have or use Personally Identifiable Information (PII)PII: TRUE
- Table or function has or uses Personally Identifiable Information (PII)
Role
convention is role: [JOB ROLE]
role: back end
role: db architect
role: design
role: dev lead
role: devops
role: product
role: repo
role: technical writing
Size
convention is size: [HOURS TO COMPLETE]
size: 0.25pt
- Can be done in 0.5-1.5 hourssize: 0.5pt
- Can be done in 3 hours or lesssize: 1pt
- Can be done in 4-6 hourssize: 2pt
- Can be done in 7-12 hourssize: 3pt
- Can be done in 13-18 hourssize: 5pt
- Can be done in 19-30 hourssize: 8pt
- Can be done in 31-48 hourssize: 13+pt
- Must be broken down into smaller issues
Work type
Stakeholders
convention is s: [PROJECT NAME]
s: CTJ
- Civic Tech Jobss: hackforla.org
- hackforla.org websites: VRMS
- Volunteer Relationship Management System (VRMS)s: PD team
- People Depot Team
Product Features
convention is p-feature: [NAME OF FEATURE]
p-feature: user
p-feature: events
p-feature: projects
p-feature: program areas
Milestones(Current)
- v0.01 - initial setup
- 1 - Compliance
- 2 - Security
- 3 - Project Mgmt
- 4 - Roadmaps & Planning
- 5 - Team Workflow
- All tables added
- v0.02 tables for VRMS existing functions
- v0.03 tables for CTJ functions
- v0.04 tables for hackforla.org website existing functions
- z - ignore