List meeting participants using their @ mention names
List goals for this meeting (e.g., Set design priorities for FY19)
Catch up
Looking forward
Time | Item | Presenter | Notes |
---|---|---|---|
Updates | all | Becca - Just got back to doing Tutor things. Tutor is still slow and temperamental on my machine Jeremy:
Zach - PTO and ill Kyle - Just finished adding pluggable jobs to Tutor. Allows adding commands that will run in containers so one command will run several commands in different containers, eg provision_developer_data job might run commands across lots of services. set-theme, import-demo-course, create-user, init have already been moved Carlos and Maria also working on smaller tasks to reach devstack parity. Devstack parity is main focus. devstack parity epic can be viewed here (scroll down):https://github.com/orgs/overhangio/projects/3/views/1 | |
10-15min | Joining forces? | I’m finding that there is a lot of overlap between the bi-weekly Tutor planning meetings and this bi-weekly meeting. What do you all think about turning this into a “proper” Open edX working group and combining it into one bi-weekly meeting? I know this group talks about non-Tutor stuff, some of which is 2U-internal. For what it’s worth I think it’d be healthy for an Open edX DevEnv WG to keep alternatives in mind and not assume Tutor is the only way forward, even if we do talk about Tutor a lot. There could also be a portion before or after the meeting for 2U-internal stuff. Curious to hear what everyone thinks! Result: DevExp Working Group | |
5 min | Vision doc updated | https://docs.google.com/document/d/1DH780mleWGEksGc18LwNLkp_oFmeUiOEyppw-USsbjQ/edit# has been somewhat updated, please review and give feedback |
Add action items to close the loop on open questions or discussion topics:
Type /decision to record the decisions you make in this meeting: