Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorporate 2U developers into CC program #32

Closed
4 tasks
sarina opened this issue Jan 5, 2022 · 6 comments
Closed
4 tasks

Incorporate 2U developers into CC program #32

sarina opened this issue Jan 5, 2022 · 6 comments
Assignees
Labels
decoupling epic Large unit of work, consisting of multiple tasks

Comments

@sarina
Copy link
Contributor

sarina commented Jan 5, 2022

task breakdown

Scoping Access

  • Phase 1: One team pilot (Q2 2022) - goals: work out the kinks, come up with framework and rules, define how teams will be represented in GH groups, figure out team vs team lead vs manager access need definitions
  • Phase 2: Expand to 4-6 teams (Q3 2022) - goals: test framework & rules from pilot, adjust as needed
  • Phase 3: Expand to full team (late Q3 2022)

Core Contributors

  • Discovery work begins during latter part of the second phase as defined above.

Description

A writeup proposal of what changes to the program should be made is here.

Please leave comments in the Google doc. At this time, the doc is going to remain private between 2U/edX and tCRIL.

@sarina sarina self-assigned this Jan 5, 2022
@jmakowski1123
Copy link

jmakowski1123 commented Jan 24, 2022

Also requires ToC input. To facilitate, consider adding an Exec Summary

@sarina
Copy link
Contributor Author

sarina commented Jan 26, 2022

Update: finished proposal and sent over to 2U for comment. Putting in "blocked" until they come back with a response.

@kdmccormick
Copy link
Member

@sarina Something I was thinking about the other day: Manually managing CC permissions seems to be working well with the current size of the program. It could get tough, though, if we added the entirety of 2U OCM to the program while using that system. We may want to tackle #773 before pursing this issue.

Ofc, you've been administering the program, so you have a better perspective on this than I do.

@sarina
Copy link
Contributor Author

sarina commented Mar 7, 2022

@kdmccormick heh just seeing this... yeah as we discussed in grooming today, that is an upcoming priority

@sarina
Copy link
Contributor Author

sarina commented Mar 10, 2022

This is a very long running ticket that will have lots of stories/subtasks. A very rough granularity TO DO list is defined in the description of this ticket. I am going to put this on the epic board (to track the effort), and track the subtasks I'm tackling in my sprint ticket each sprint.

fyi @jmakowski1123

@sarina sarina added the epic Large unit of work, consisting of multiple tasks label Mar 10, 2022
@sarina
Copy link
Contributor Author

sarina commented Sep 23, 2022

Closing this. This is more complicate than can be handled in one ticket. We've discussed strategies but ultimately 2U will have to drive this to an extent, because (per agreement terms) we cannot make 2U become CCs (at least, with my definition that to be a CC, you can't be in push-pull-all; I believe that's not a unanimous take per talking with Xavier). I think this requires more groundwork conversations, then creating actionable tickets.

@sarina sarina closed this as completed Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decoupling epic Large unit of work, consisting of multiple tasks
Projects
Development

No branches or pull requests

3 participants