/
Term 1 Week 3

Term 1 Week 3

Retro

Reflect on the previous time period

 

Notes

Actionables

 

Notes

Actionables

What was completed?

  • Part of list view

  • Drafted API’s with routes

  • Drafted ERD’s

  • Drafted SQL Table schema

  • Set up v2 repo with ci pipeline

  • Starter code for backend + db

 

What was done well?

  • Planning for the backend design started off strong

 

What could have been done better?

  • Bit disorganised with meetings

  • More coding

 

Find weekly time for Frontend meetings

Planning

Update plans for the future

 

Notes

Actionables

 

Notes

Actionables

Short term goals

(achieve by next retro)

 

Finish off listview + clean up divs @Sean Wibisono (Unlicensed)@Damjan Stevanoski (Unlicensed)
“See more” button for long reviews (80-100+ words) @Sean Wibisono (Unlicensed)@Damjan Stevanoski (Unlicensed)
Adding prompt in review model
Finalise diagrams
Start developing backend
Align components in skimmer
Design figma ui @Joel Huang (Unlicensed)@Vivian Wang (Unlicensed)@Victoria Vu (Unlicensed)
New repo for v2.0
Fix filter issue on homepage @Damjan Stevanoski (Unlicensed)@Sean Wibisono (Unlicensed)

Medium term goals

(review at next retro)

  • New repo for 2.0 or just in new branch?

    • New repo → easier to see updates

Starting on frontend
Smoother transitions
Notify admin for flag reports

Timeline

(ETA until release, etc)

 

 Redeploy old version next meeting (list view + other short term goals)

Misc

Random stuff

 Walk through DB and backend routes

  • (Diagram on Confluence)

    • v2 stores users, pk is zid

      • stores their reviews, bookmarked courses/reviews

      • is_admin can simply be accessed through endpoint

  • Swagger API

    • auth problems? → ask abiram

 Anyone interested in designing new frontend UI

  • Joel

 

 

Useful links

Related content