edx / open-source-process-wg

Issues and tasks for the Open Source Process working group
2 stars 0 forks source link

How do we keep engineers up-to-date with what Axim/decoupling are doing? #13

Open nedbat opened 2 years ago

hurtstotouchfire commented 2 years ago

I think there are some ways we're already supposed to be doing this through manager report-back chains, which is not my favorite method of getting info out on the ground, but it's arguably a hard problem to solve. Could we establish a shared (within OSP-WG and tCRIL and some selection of fancy manager types within 2U) understanding of the points of contact between our organizations? I think I will make a separate issue for that.

feanil commented 2 years ago

FYI, all the work that the tCRIL eng team is actively working on or will be working on soon can be found on this board: https://github.com/orgs/openedx/projects/8

As we mature, that will become more and more accurate. There's also the #openedx-transition channel: https://openedx.slack.com/archives/C02M89BSV9A as announced here: https://discuss.openedx.org/t/open-edx-codebase/6170

sarina commented 2 years ago

Additionally we're starting on a roadmap: https://github.com/orgs/openedx/projects/4

The board Feanil links to has multiple views that you can access in the top tabs, there is a Decoupling tab

We're in Slack and available for questions anytime - #openedx-transition is a great place to start.

Our PM, Jenna, is starting work with your Product Team to get roadmap alignment.

Note our team is 5 engineers, so what we're working on will remain a fairly small subset of things.

jristau1984 commented 1 year ago

@nedbat I think this issue can be closed now. Can you confirm?