Skip to content

Meeting minutes (backend team only)

Adam Ross edited this page Apr 5, 2022 · 3 revisions

πŸ—“οΈ Friday 11th March Backend meeting

When: 12:00pm Absent:

πŸ“ƒ Agenda

  • Go over and approve created issues
  • Go through current setup
  • Decide on database
  • H2 (memory, no consistency)
  • mySQL docker (consistent data)
  • Setup swagger?
  • 3rd party Auth, self-created Auth
  • Start creating any new issues

πŸ–‹οΈ Notes

  • All the current issues reviewed:

    • Created README #16
    • Add Code Owners #15
    • Decide on database implementations to use #13
    • Add meeting minutes to the wiki #11
  • Went through the current github repo

  • Decided to stick with h2 for now and start developing the backend, at a later point change the database to be mysql

  • Authentication:

    • Will give thought about 3rd party or self created in the coming meetings
  • Endpoint prefixes for the team it is for

  • Swagger would be useful if we can use it, seems to only need annotations for endpoints to be visible, unsure about the exact requirements to get it implemented and running, this will need to be investigated

  • Issues to create

    • Setup database/persistance manager - Flynn
    • Low priority change database to mySQL
    • Investigate implementing swagger - Eric
  • OWNERS

    • Will it cause trouble when the teams migrate and a new team comes on
    • Documentation would be needed to clarify this process if we have specific teams and if it is not clear which team the certain subdirectory belongs to
    • Going ahead with option 2 (specific subdirectories with owner files related to teams) + a bit of option 3 for shared directories

πŸ’» Action Points

  • Test repo/server works
  • Have team meetings decide issues
  • Issues assigned to go off and be done

πŸ—“οΈ Tuesday 29th March Backend meeting

When: 12:00pm

Present: Kimsong, Dave, Minxing, Adam, Jiayang, Ethan

πŸ“ƒ Agenda

  • Discuss the project
  • Demonstrate and help with the project setup
  • Decide which backend issues to work on for the second assignment

πŸ’» Action Points

  • Create backend issues for existing listed future tasks
  • Assign to, and start development on backend issues