Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Meeting Notes November 30, 2019

Jim Ciallella edited this page Dec 9, 2019 · 4 revisions

Before you dive into the notes, please make sure you have read the following:

Agenda

In Attendance

Quincy confirmed the lower attendance after the initial burst is normal. Also, it’s Thanksgiving weekend in the USA.

Review of Wiki, Project, and User Stories

  • Jim shared the Wiki section and Quincy confirmed the Vision should live here.
  • Reviewed the Project page
  • There is no active work on user stories since we’re still laying groundwork on the technical side

TypeORM / Tooling

  • Fran is writing docs on migrations and models and how to convert from TypeScript to Javascript.
  • ankorGH is going to take over #162.
  • Fran is going to pick a popular style guide to work with eslint. There will be other style issues, like import.
  • Quincy suggested we fix style issues instead of trying to enforce style edge-cases if it’s going to reduce contributions.
  • Fran will add seeds.
  • Fran is controlling the critical path on tooling and Quincy will work with him to move that forward.

Review of Other Pull Requests and Issues

  • #146 on NodeMailer and #253 API schema were assigned to Vaibhav
  • #166 on Redux is going well and just needs tweaks before the two major issues are unblocked.
  • #159 We will use Materialize UI to help toward the MVP and avoid custom code.
  • #139 Serverside testing is waiting on the #146 on NodeMailer
  • #12 Documentation, Quincy asked Madalana and Jim to help move this along
  • #47 Roadmap closed in favor of the Github Project board
  • #254 DB Schema User Types Fran will break the issue into MVP user stories

Breaking Issues into Smaller, More Manageable Pieces

  • #255 Narrowing Scope of First Steps - Quincy suggested duplicating existing user stories as they related to "Documentation and Copy", API, and User Interface (UI) . He added columns to the project board to match these topic areas.
  • As an example, Quincy broke down the Documentation into more granular issues #260, #261, #262, #263
  • API documentation is created programmatically. Fran suggested a programmatic GitHub page that gets created upon git push.
  • Quincy split user story #95 into two issues, one for API work and one for #264 UI. Quincy suggested that loosely coupled issues that one person can accomplish without depending on other people is key to moving along
  • Nikhil described using epics, stories, and tasks and utilizing Git branches and sub-branches as a way to manage larger software
  • Quincy suggested we keep things simple and focus on having front-end and back-end
  • Nikhil has free-time and will take on some of the new issues created by Quincy.
  • More details about the more granular issues were shared by Quincy after the meeting.

Next Meeting