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 |
---|---|---|---|
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 Ownership?
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 |
|
|
| Current progress |
|
|
20 | New Issues |
| |
10 | Assign tasks |
|
|
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.