-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
Also requires ToC input. To facilitate, consider adding an Exec Summary |
Update: finished proposal and sent over to 2U for comment. Putting in "blocked" until they come back with a response. |
@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. |
@kdmccormick heh just seeing this... yeah as we discussed in grooming today, that is an upcoming priority |
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 |
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. |
task breakdown
Scoping Access
Core Contributors
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.
The text was updated successfully, but these errors were encountered: