Standup Meetings Discussions

[Caleb-Cohen]

We will keep a running log of our meetups so people can reference it.

First Meeting (11/17)

• Add event form is almost done. It should be completed by 11/19, and then we can merge.
• We're removing monthly recurring from the form. I will assess if we need to re-add it later.
• Rick, Joe, and Winston created a JSON server to feed fake data back to the front end for testing
  • to run CD frontend and execute NPM run dev
• After add-event-form merge, we will refractor the layout of the repo and then finish the MVP
  • Separation of concerns with frontend and backend use this template
  • Removing BuB remnants
  • Reducing deprecated dependencies from Package.JSON
• Git Hub management overhaul
  • Create a development branch and have the main be solely for production. It will be done right after MVP.
  • Make Together more approachable for outsiders to join better documentation
  • Investigate MVP milestones
  • Investigate Github actions
    • eslint check
  • Investigate Wiki
  • Investigate Github flow
  • Create an Issue template/Bug template
  • Post beginner-friendly issues to catch-up-crew
• General/Misc
  • Please give beginners a chance to solve beginner-level issues
  • Use issues for specific and concise problems. Use discussions for abstract goals that require problem-solving.
  • Standup time changes to 6:30 EST every Tuesday & Thursday, right after standup.

Second Meeting (11/22)

• Refractor Feedback
  • Refractor looks good. Works on Windows, Mac, and Linux.
  • Create an issue for build folder needing to be moved back to client folder.
• Demonstrated startup commands and potential issues regarding the refractor branch
  • commands are npm install, npm run dev-concurrent to start.
  • command npm run build is used to compile the frontend, but will not execute unless npm run lint is not returning any eslint errors. Running npm run formant will auto-fix most lint errors, you will have to manually fix the rest. Lint is used to standardize the code base.
  • If you prefer dual terminal you can npm run dev which starts the server and then npm run start-client which starts the client.
  • Your .ENV folder must be contained in the server/config folder
  • Update readme & wiki to contain these details
• Discuss post-refractor merge features, and assign tasks.
  • Visualizing event objects into the calendar will be led by Joe, Rick, and Caleb
  • Securing the add event form behind Authentication will be led by Winston
  • Grabbing the username from auth instead of being user-entered will be led by Winston
  • Assessing event model to streamline date & time will be led by Eric
    • Noted Date-fns as a potential package manager for the all the date issues
  • Add end-date will be led by Caleb
  • Event details page extendable views will be led by TBD
• Discussed wiki and readme is being updated
• Misc feedback and questions
  • Are we set on react-router? Yes.
  • Timeline for project into the wiki? Will consider it!
  • Communicate that dummyJson is purely testing and not meant to be used for production. Let's change the name to test Json server.
  • Explain github management in wiki and add necessary branches

Third Meeting (11/29)

• Displayed Together and gave a rough overview of what we're doing and trying to accomplish.
• Showed off Eric's awesome Contributing.md
  • Explained to please give us feedback for Contributing.md so that we can improve
• Current Features & Updates
  • No update on Visualizing event objects into the calendar will be led by Joe, Rick, and Caleb
  • Joe's preferred time is Monday, Saturday or Sunday at 6pm EST
  • No update Securing the add event form behind Authentication will be led by Winston
  • No update Grabbing the username from auth instead of being user-entered will be lead by Winston
  • No update Assessing the event model to streamline date & time will be led by Eric
  • React Router setup led by MattB
    • Almost done ready for PR will open new issues
    • We will not be using React Router at this time as we do not have a need
    • Matt explained that React Router is a library for routing React pages
  • Completed Add end-date will be led by Caleb Completed
  • noDevBuild led by Winston'
    • PR has been started. There will need to be some changes to check if it's production or Dev.
• I need more help! Organizing, managing, beginner tasks, expert tasks, we need it all!
• Additional feedback
  • Design does not have a nav bar
  • Nav essential for react-router
    • Landing page, logout, add event form
  • Add back end issue for event modal

Fourth Meeting (12/1)

• Displayed Together and gave a rough overview of what we're doing and trying to accomplish.
• Showed the new features wiki page explaining the JSON test server and setup
• Features
  • Visualizing Event Objects into calendar. Some bug fixes that Caleb noticed. We need a discrete id. Caleb will add that to the template.
  • Assessing event model (Date FNS and storing future dates into event object itself) Helper functions for Date FNS starts with UTC. X copies of events within an array when submitting.
  • Securing add event form behind authentication. Matt, just assigned.
  • Grabbing the username from auth instead of requesting the user to enter. Assigned to Caleb.
  • noDevBuild assigned to Joseph, we had some comments addressed by Rascal.
  • Ceating a Modal for event views assigned to Chanel. Working on the front end won't connect just yet.
  • Front end landing page assigned to Jason/Honda
• Additional feedback
  • Event addition limits and security
  • prefer username in the nav bar

[Caleb-Cohen]

Reserved