2022-02-08 DevEnv Meeting notes

Date

Feb 8, 2022

Participants

@Rebecca Graber (Deactivated)
@Diana Huang
@Jeremy Bowman (Deactivated)
@Ned Batchelder (Deactivated)
@Kyle McCormick
@Mat Carter (Deactivated)
@Connor Haugh (Deactivated)
@Ben Holt (Deactivated)
@Chris Deery (Deactivated)
@Zach Hancock (Deactivated)
@Jansen Kantor

Goals

Establish a working cadence for the DevEnv group
Begin outlining the specific tasks for upcoming work

Discussion topics

Time	Item	Notes

Time	Item	Notes
5m	Intro	Introductions Why are we here?
10m	Where will we keep tasks?	Jira board vs GH issues GH Issues Which org? edx vs openedx Will it matter where we do work around enterprise repos? we can create private Jira tickets if necessary Tutor is not under openedx governance We don’t want to conflate the TCRIL work with our work Suggestion: new open repo in the edx org
10m	How will our priorities be determined?	Our initial tasks come from On High, but following that, how will we identify and prioritize devenv issues? Feanil’s doc has some guidelines on work to be done with Tutor Feanil’s doc has been pulled into this board, along with other issues: https://github.com/orgs/openedx/projects/10/views/1 One big board for all employee requests? Use a rubric to triage might need to break it out into separate smaller issues if we get overwhelmed security has the SEC board with the security reports, then a separate board for improvements to process Note: tutor has a troubleshooting page Troubleshooting — Tutor documentation things can go wrong in our plugins, or in the core core problems should go first to the Tutor maintainer team, who have their own process
10m	How will work be assigned?	How will work flow between TCRIL and us? How will work be distributed within the WG? On call rotation? Adhoc? What should our meeting cadence be?
20m	First tasks	Kyle - introduction to Tutor project and what support TCRIL hopes for The French government uses openedx to run their state education! Overhang.io created Tutor to help custom installations of openedx in prod and development plugins instead of core modifications Our goal is to make Tutor work for us Overall Tutor initiative Archive: Tutor DevEnv Adoption First things first: try Tutor Medium to long-term: edX to take ownership for Tutor plugins that are specific to edX, eg enterprise-catalog Take notes on what happens when you try Tutor What was unclear? What went well? What could have been better?
	Actual first tasks	determine and document limits of devstack on M1s
	Notes	At some point need to make a deliberate decision on how much to involve the community and when

Action items

@Diana Huang to create new open repository under the edX org

@Ben Holt (Deactivated) and @Connor Haugh (Deactivated) to compile a list of issues/concerns with devstack on M1s in whatever format they see fit (tickets to be put on our board, PRs for updated documentation, confluence, etc)

Everyone else to try Tutor and take notes about what they can and cannot do

@Rebecca Graber (Deactivated) to schedule the next meeting

Decisions

We will use GitHub issues to keep track of our tasks
We will create a new public repo in the edx GitHub org to hold our issues
The project board will be org-level, to allow linking to issues in other repos later
Employees who wish to bring issues about development environment work will file a ticket on a issue specifically meant to be triaged, and from there the WG will decide whether to punt the ticket to a squad, work on it ourselves, or follow the Tutor process for errors in Tutor core