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

Meeting Notes March 6, 2021

Jim Ciallella edited this page Jul 1, 2022 · 9 revisions

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

In Attendance

Current Status

freeCodeCamp Updates

Project Updates

  • Fran said the admin CRUD functionality is relatively far along.
  • The front-end, client side only has a few basic pages, no forms, and these pages need the most immediate attention to move along the MVP user stories.
  • Fran suggested we are looking at at least the 3-4 months for a usable MVP and more likely 6 months to get it in the hands of others. This assumes a return to the previous pace, as-needed meetings to keep up the momentum, and avoiding scope creep with new features.
  • Fran is busy for the next 2-3 weeks, but plans to be available in 3 weeks.
  • Quincy suggested we work on outlining a "golden path" for a video demo to highlight the features / user stories of the MVP as a way to get other developers and eventual owners excited about the direction and progress.
  • Fran talked about breaking the user stories into smaller tasks.
  • Jim suggested we stick with the user stories and Github MVP Project for the broader MVP goals, but add a task list to the top of the user stories with a more fine-grained checklist with links to specific issues and conversations. #360 is an example of this pattern.
  • Patrick has more time available to take on the authentication and other tasks.
  • The authentication package will use a Passport.js flavor to send login emails. Patrick expects to reuse much of the code written for the previous / abandoned Google Authentication Auth direction.
  • Jonathan has an open #428 pull request for fixing an email resolver issue and doing input validation. This needs review. Jim added Fran as a reviewer.
  • Jonathan likes using Node Mailer App, which provides a local mail server with SMTP, as an alternative to "fake / dummy" 3rd party SMTP testing services, like Ethereal or Mailtrap.
  • Jonathan offered to create a lo-fi wireframe to supplement the existing visuals. Quincy suggested roughing things out in HTML instead of building an new visual representation. Quincy didn't think sharing a newer Figma-style document with devs or users would be as effective in promoting the progress through a video and / or a roughly working demo application.
  • Jonathan and Tom are having an issue rendering the front end, which seems related to Node 13 vs Node 14. Fran shared a likely fix in Discord, which involved removing "engines": { "node": ">=14.15.0", "npm": ">=6.14.8" } from the package.json
  • Tom suggested moving to Node 14.
  • Tom had a working example on Heroku's free-tier, but it was crashing a lot. He restarted it and shared the GraphQL page as an example.
  • Fran said we can host a development back-end on a cheap host, like Digital Ocean or Vultr, and have it public so developers can use a back-end URL instead of needing to run their own full back-end.
  • Fran suggested a MailTrap account for the shared development back-end server. We'll need to look into the terms of service and security implications of sharing an account.
  • We are still planning to suggest Heroku as the default instance hosting for MVP. Owners will have the ability to host the MVP application on own server and tweak .env files manually, but the initial documentation will focus on Heroku deployment.
  • Tom is interested in smaller, as-needed, meetings to get familiar with other areas of the application, like the Auth side.
  • Matthew would like to put his experience toward the front-end development. He'll work with Jim and Jonathan to find a place to get involved, such as #444 and homepage / navigation elements of #349
  • Jim asked Tom for help with updating the Docker docs since some developers use Docker only for Postgres, others aren't using it and are running local services, while others are using Docker on different operating systems. Tom won't be available until the following weekend.

Chat

  • freeCodeCamp now has a self-hosted community chat server. (UPDATE: This was later switched back to Discord in mid-2022)
  • Quincy asked for a vote on moving away from Discord and everyone who voted was in favor.
  • Quincy will create the new channel on chat.freecodecamp.org later today (March 6th). (UPDATE: This was later switched back to Discord in mid-2022)
  • Quincy will pin a message to Discord directing everyone to the new chat tool.
  • The old Discord will not be deleted.

Next Meeting

Quincy will share an invite on the Chapter chat channel for the next meeting at the same time once we establish another meeting is warranted. (UPDATE: This was later switched back to Discord in mid-2022)