This repository has been archived by the owner on May 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Run 2U-OCM DevEnv Working Group #42
Comments
@rgraber will be leading an internal working group to pilot Tutor at 2U. @regisb, could you give @rgraber and @dianakhuang triage access on this repo so we can assign them to issues like this? |
kdmccormick
moved this from Ungroomed
to In Progress
in Tutor DevEnv Adoption (OLD BOARD)
Feb 8, 2022
@rgraber will be making a repo/project to hold issues for this working group. When that's ready, we'll link it here and close this ticket. |
1 task
kdmccormick
added
social
Issues around the community, not the code
and removed
affects:2u-pilot
labels
Feb 16, 2022
kdmccormick
changed the title
2U-OCM DevEnv Working Group
Run 2U-OCM DevEnv Working Group
Mar 8, 2022
This is still ongoing, but I am closing it because it's being done by 2U, and not by Régis or I. For updates, follow along with this epic: openedx/axim-engineering#486 |
Repository owner
moved this from In Progress
to Closed
in Tutor DevEnv Adoption (OLD BOARD)
Jun 22, 2022
Repository owner
moved this from In Progress
to Backlog
in Tutor DevEnv Adoption
Jun 22, 2022
kdmccormick
added
the
duplicate
This issue or pull request already exists elsewhere
label
Sep 14, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Original Context
We need a small pool of volunteers at 2U-OCM (aka edX) to try out Tutor. We will want to collect feedback regularly and factor it into the project's backlog.
Pilot pool need-to-haves:
Pilot pool nice-to-haves:
New Context
2U-OCM is spinning up an internal DevEnv Working Group to tackle this, led by @rgraber.
Acceptance
Kick off first meeting for DevEnv WG, and then build new GH issues / Jira tickets based off of that.
The text was updated successfully, but these errors were encountered: