Notes

[NickSramcik]

Gathering space for notes on meetings, or other general project discussions that don't fit elsewhere.

[NickSramcik]

🥞 Banki Brunch Planning Meeting! 🥓

October 1st, 2024

App link: https://banki-brunch.vercel.app/ Github Repo: https://github.com/NickSramcik/banki-brunch

Tools:

Javascript, React, MongoDB, Express.js, Node.js

Priorities:

• Tagging / Sorting (Which tags should we include?)
• Question Submission
• Answer Submission? (What should this look like?)
• Separate page for studying— question feed
• Accessibility— Text to Speech etc.

Questions / Thoughts:

• What about people who can’t join stream due to timing?
• Text to speech / Recording answers?
• Only see other answers after submitting yours
• Significant willingness to add Typescript
• Pair programming!
• Developer registry (Who is who and working on what?)
• Division on how issues should be delegated - explore this more later

Roles:

• Maintainers - (Review pull requests)
  • Trillium, Rask, Git_Alpine(Joe), Bam29
• Note takers - (Take notes during standup meetings for thread use)
  • Adrian, Miguel,
• Documentation - (Someone to take charge / guide documentation work)
  • nchristene, Sana, TaraT, Aisha, ParejaOnPurpose, Sarah
• QA - (Testing, quality assurance)
  • ItsCalen, Sana, Sarah, Adrian

[adriancpm]

🥞 Banki Brunch Meeting Oct 8th! 🥓

Current Issues:

• Clean up the console.logs
• Implement a logger
• Prettier(tooling) config
  • Everyone in the group project can use
• Configure ESLint rules
  • Currently 5+ errors
• Continue Integration and merge code
  • Look at every code change and run it locally
  • Run the pipeline
  • Prevent people from merging if they don’t follow the rules
• Structure we currently have
  • Banki on Vercel - How do you replicate it locally?
  • Backend ignored
  • Docker can solve the issue
  • The same structure on deployment and locally
• Deployment
• QA
  • End-to-end testing - mimic the browser
  • Pull request preview environment
  • Separate into smaller tasks
• Organizing Tailwind
• Features
• Revisit the folder structure
  • Front-end to be a static asset
  • Avoid too many concepts for new people

Ideas:

• Tagging/Sorting questions
• Recent interview questions

Roles:

• Maintainers - (Review pull requests)
  • Trillium, Rask, Git_Alpine(Joe), Bam29
• Note takers - (Take notes during standup meetings for thread use)
  • Adrian, Miguel,
• Documentation - (Someone to take charge / guide documentation work)
  • nchristene, Sana, TaraT, Aisha, ParejaOnPurpose, Sarah, Mozart
• QA - (Testing, quality assurance)
  • ItsCalen, Sana, Sarah, Adrian, StevenMoses, Zraha

[adriancpm]

🥞 Banki Brunch Meeting Oct 15th! 🥓

Issues!

• Standardize with Prettier
• Clear up the console logs
• Question Tagging
• Implement a logger
• Configure ESLint rules
• Investigate host/server
• Organize tailwind
• Look into the folder structure
• Documentation - Non technical (Find template)
• Github issue tags
• Look into trello/kanban board integration w/ github - Joe