/
[12/10/23] what's happening with the cms?

[12/10/23] what's happening with the cms?

Participants

  • @Hanyuan Li @Laura Wen @James Teng @Brian Zhang @Brian Wang @Varun Sethu @Thomas Qu @Derek Tran @Josh Ramos @Emily Lu @Thomas Liang @Winnie Tan

Apologies

Discussion topics

Topic

Context and Discussion Points

Action Items and Decisions

Topic

Context and Discussion Points

Action Items and Decisions

General updates

Website

MVP is built, everything in the design is done

  • Basically waiting on feedback from new exec and what content we missed

  • Had to register for business account for FB API

    • Come up with different design to incorporate events

 

CMS FE

Blocked a little bit, trying to get as much working as we can

  • Made most progress in previous terms

  • Need to do auth, translate operations

 

CMS BE

Long-standing PRs got merged, incremental progress on image support ticket and DB support

  • Current issue has workaround

 

CMS status

What does the team want to do with the CMS?

https://csesoc.atlassian.net/wiki/spaces/WM2/pages/2499837961

WHAT NEEDS TO BE DONE BY END OF YEAR

  • Split Website and CMS into separate repositories

    • Once that’s done, notify @Jared Lohtaja

  • FE: login page

  • Control flow:

    • FE gets Slate commands from user

    • Converts to CMS commands

    • Sends CMS commands to backend

    • BE sends CMS commands to FE

    • FE translates back into Slate commands

  • BE: proper DB migration

  • Multiple cursors (stretch goal)

@Thomas Liang @Laura Wen - there is progress made, but doesn’t look like it’s feasible to complete at the end of year

  • We barely have a bugfix for what frontend is facing

  • Still has to translation of operations

@Varun Sethu tasks aren’t complicated per se, but the backend team is too small to get these done within half a term

 

Plans for rest of term/year?

@Varun Sethu most of backend and frontend would be graduating

  • Recruiting will be very difficult - value add doesn’t correlate to the amount of effort required

  • @Laura Wen agrees

Try to finish off as much as we can with the CMS

Pivot the team to some other project

Do nothing

@James Teng if we had a lot of manpower, there’s a lot of work we could do in the website to polish the website?

  • Could put a lot more effort into making it really nice

  • Kinda worried if we combine two teams together, coordination would be tricky

    • If it’s just FE, we need to find something to do

    • We can keep ourselves busy with CSESoc website until end of year

What would BE do?

  • @Westley Lo wanted to transfer into the FE team? → Transfer into FE

@Varun Sethu if there’s going to be a projects showcase, isn’t it good to just polish what we have and work on having something to present?

  • If Culture needs extra people on hands the team could help?

@Laura Wen if CMS backend team is not continuing then FE will just transfer to website

@Thomas Liang BE can decide what to do on an individual basis?

  • Westley is busy, Thomas L is busy

  • Thomas Q doesn’t feel invested

  • Brian is OK with leaving it as it is

  • Varun is all good, Emily is same with all of them

  1. No more CMS
    - Backend will keep themselves busy in some way
    - Frontend will transition to CSESoc website development until EOY

CATEGORY

 

 

 

 

 

 

BUSINESS WITHOUT NOTICE

 

 

 

Useful links

Related content

UNSW CSESoc