List view

• y. Excellent Level

  Will do it in the future - not highly prioritized.

  No due date
  0% complete0 open0 closed

• x. Technical Debt

  No due date
  0% complete0 open0 closed

• w. Ongoing

  For issues that: a) You keep in Ongoing or Ice Box columns when you aren't using them, OR b) Recur and don't fit into another existing milestone, OR c) Don't seem to warrant a milestone, OR d) Aren't prioritized, meaning the issue gets opened, resolved and closed all at once.

  No due date

  •5/15 issues closed
  33% complete10 open5 closed

• 03. Org Requirements

  Objective: To be responsive to Hack for LA needs. Achieved by: (website) project card updates, stakeholder meetings/feedback/updates, etc. Labels: TBA.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• v0.01.01. AWS Deployment

  No due date

  •2/3 issues closed
  66% complete1 open2 closed

• v0.05. Tables for KnowledgeBase Functions

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• z. Ignore

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• v0.04. Tables for Hack4LA Website Existing Functions

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• v0.03. Tables for CTJ Functions

  Objective: The tables required to service the functionality of future Civic Tech Jobs deployment, including: a) Member functions b) Admin functions

  No due date

  •6/8 issues closed
  75% complete2 open6 closed

• 05. Team Workflow

  Objective: To make sure the project team has the resources and processes to be effective. Achieved by: Recruitment, onboarding, team meetings, etc. Feature labels: TBC.

  No due date

  •62/95 issues closed
  65% complete33 open62 closed

• 04.01. Roadmaps & Planning

  No due date

  •8/21 issues closed
  38% complete13 open8 closed

• 04. Project Setup

  Objective: To keep the project organized and efficient. Achieved by: GitHub board maintenance, roadmapping, social media channels, etc. Feature labels: TBC.

  No due date

  •31/43 issues closed
  72% complete12 open31 closed

• 02. Security

  Objective: To keep data and resources secure. Achieved by: Passwords, tokens, etc. Feature labels: TBC.

  No due date

  •5/16 issues closed
  31% complete11 open5 closed

• 01. Compliance

  Objective: To make sure we aren't violating any licences or regulations. Achieved by: Licencing compliance (credit page for images, etc.), Privacy Policy. Feature labels: TBC.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• v0.02. Tables for VRMS Existing Functions

  Objectives: The tables required to service the functionality of the current VRMS deployment, including: a) Member functions - Account Setup - Sign in to recurring events on the day that they happen b) Admin functions - Add projects to user records - Edit all project data - Create new projects

  No due date

  •7/10 issues closed
  70% complete3 open7 closed

• v0.01. Initial Setup

  Objective: Tables for initial setup

  No due date

  •46/75 issues closed
  61% complete29 open46 closed

• v0.06. All Tables Added

  Completion of this milestone means that all the tables have been added to the backend, with basic CRUD functionality for each of the tables. It does not mean all functionality is there. Next steps: - Work with projects to assess their needs and add functionality as necessary. This could mean adding pagination to API GET requests, filtering results, etc.

  No due date

  •12/22 issues closed
  54% complete10 open12 closed