2022-02-23 DevEnv Meeting notes

Date

Feb 23, 2022

Participants

@Rebecca Graber (Deactivated)
@Connor Haugh (Deactivated)
@Diana Huang
@Ben Holt (Deactivated)
@John Nagro (Deactivated)
@Ned Batchelder (Deactivated)
@Jeremy Bowman (Deactivated)
@Chris Deery (Deactivated)
@Zach Hancock (Deactivated)

Goals

Determine how we will receive issues from tCRIL into our pipeline
Report on current progress
Determine and assign next tasks

Discussion topics

Time	Item	Presenter	Notes

Time	Item	Notes
5	How to get things from tCRIL	Proposal: create a new (issue? JIRA?) and have tCRIL add in the same way we will eventually expect edX internal engineers to report issues. Should probably have a `tCRIL request` tag. Ownership? Tutor is still owned by Overhang We would write our own plugins into Tutor and control that. There are proprietary extensions We could fork it at any time. We have a vested interest in using what the rest of the Open edX ecosystem uses, and we’re hoping that the investment in getting this to work well for 2U/edX benefits the rest of the community as well.
	Tutor Discussion	The documentation is very geared for deployment. Difficult to find where the code is to modify for development. No test data available No test data in devstack either arch-bom was working on a possible solution for this, but we didn’t get far enough into it. OEP-37: Dev Data — Open edX Proposals 1.0 documentation OEP-37(Dev Data) implementation Got blocked on availability of a team to partner with in trying out the implementation Quokkas enterprise team is interested in helping out. Feedback from 3 folks: Local development doc: [Archive] Using Tutor for local development Mostly getting it up and running, not doing development yet. Concerns about using remotes for development
	Current progress	M1 Macs have not reached the team yet. Requests with AWS Playground to get access to the M1 hardware How to doing devstack testing on different hardware? Talk to Tim McCormick, Adam Blackwell about thoughts about this. Tutor installed and running with ecommerce and mfe plugins. Haven’t managed to test ecommerce yet with a test purchase yet. frontend-app-learning is going to be on by default for Nutmeg.
20	New Issues	What is the biggest pain point? Documentation seems like an obvious one. Steps to get to editing code are manual right now. Update the docs to make it obvious about how to mount volumes; currently hidden in https://docs.tutor.overhang.io/dev.html#manual-bind-mount-to-any-directory MFE development is definitely a concern Running unit tests? How do we attach a debugger? We can ask Regis about this in Open edX Slack. Which tools do people use? Pycharm, Webstorm, SublimeText Docker Desktop questions We could look into alternatives? Rancher desktop seems like a good one. We(2U) is planning on paying the fees.
10	Assign tasks	If you have Tutor set up, try developing on an MFE. If you haven’t set up Tutor yet, set up Tutor. Try running some tests and seeing what breaks. Reaching out to Overhang about Tutor questions What are the concerns around unit tests currently? Open edX development — Tutor documentation There’s a few discussion threads already in progress: Unit tests improvements for Tutor Running Unit Tests in tutor Has anyone tried running Tutor with a debugger or with an IDE like PyCharm? Interaction between mounting your own volume and running tests? There seems to be a custom test settings file for running tests. Where do we get this? End goal: Matrix of services/MFEs and what works/doesn’t work in Tutor (tests, code modification, etc) Sharing a page

Action items

@Chris Deery (Deactivated) to reach out to Overhang about debuggers and IDEs with Tutor.

@John Nagro (Deactivated) to do some discovery on getting enterprise working in Tutor.

@all Everyone try to run Tutor for the service/code you modify most often. Track any issues in: [Archive] Using Tutor for local development

@Rebecca Graber (Deactivated) to set up the initial table for keeping track of services/MFE (might want to use Django 3.2 Upgrade List of IDAsarchived as a template, would need to add MFEs and refactor the columns)

Decisions

If we need to get something from tCRIL, create a ticket in the 2U adoption project. Let them triage it. If a ticket is assigned to us, we can ask tCRIL to come to our meetings.
Internal requests from 2U engineers can be reported in Slack, and then triaged by the working group.
We are going to continue to use Docker Desktop for Macs for now and are planning on paying for it.