2025 - 1 - 28

 Date

Jan 14, 2025

 Participants

• @Ali Hugo

• @Ty Hob

• @Dave Ormsbee (Axim)

• @Edward Byun

• @Esteban Etcheverry

• @Felipe Montoya

• Gabriel Carvajal

• @Jenna Makowski

• @Maria Fernanda Magallanes Z

• Mahnoor Sarwat

• @Sam Daitzman

• @Sarina Canelake

• @Santiago Suarez

 Goals

• Review the Open edX Roadmap.

 Discussion topics

 Action items

Meeting Notes

• MVP questions

  • Is the override of policies part of MVP?

    • If all roles are positive allow, it’s easier. Deny lists and overrides, particularly disallow as policies, it becomes more complicated.

  • Composing a bunch of new roles may be difficult in 6 months

    • Could look at 3 underlying mechanisms that currently exist, and try to replace them one at a time. MVP could be to replace the first one, then build on that [to do: find the documentation]

    • If all access controls go through this new framework, migth make more sense to start with roles that already exist and start wrapping permissions for one of the curerntly existing roles

    • One approach - start with one relatively small role with a narrow scope on the platform and create the permissions and scope for that single role. Could start with 1-2 discussion roles

      • If we go this route, will need to tempprarily retrofit the UI and can keep it behind a flag until we have enough roles converted

      • It would also help iron out hte product / UX implications of where you set those roles and who can do that etc, which is one of the broader experience questions I have for this still

    • [work 2U started to document where permissions are currently stored: https://github.com/openedx/edx-platform/pull/34250 ]

    • technical requirements - will need to better understand what the expectations are in terms of extensiblity

      • currently everythign is centrally defined

      • we may want to move toward having individual applications set their own permissions [to do: needs further speccing]

      • currently edx platform is the keeper of all the permissions, do we need another repo that makes it easier for plugins to do queries against

      • performance considerations

      • migration considerations

      • spin off a separate tech requirements doc, need input from plugin side

      • not a big barrier if we start developing now in edx platform, but should consider from the beginning where it should live makes sense

    • not clear from the PRD - pathways for configuring platofrm level roles vs course level roles, and which products expose these views

      • possible approach - think about this incrementally as well, with role by role

    • another need - gettinv very specific in language, defining the concepts in the PRD

      • extending the flowchart to include definitions

    • another to do - transfer all documentation into wiki

 Decisions

meeting-notes