You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like for tCRIL to create a group for the proper maintenance and stewardship of the openedx-k8s-harmony project.
This group should have maintain permission on the openedx-k8s-harmony repo. The group members would be @bradenmacdonald and me (@felipemontoya). Both of us are core contributors so this should not have problems from the legal standpoint. When the times comes we will use the process of oep-54 to extend permissions to other members.
Reasoning
This project used to be called tutor-contrib-multi but that was a temporal name and now the definitive one is in place.
However it looks like we tried adding people that were not core commiters and this further complicated everything. It should not be the case this time around.
Thanks a bunch
The text was updated successfully, but these errors were encountered:
Thank you for your report! @openedx/tcril-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer.
Firm Name
eduNEXT
Urgency
Medium (< 2 weeks)
Requested Change
I would like for tCRIL to create a group for the proper maintenance and stewardship of the
openedx-k8s-harmony
project.This group should have
maintain
permission on theopenedx-k8s-harmony
repo. The group members would be @bradenmacdonald and me (@felipemontoya). Both of us are core contributors so this should not have problems from the legal standpoint. When the times comes we will use the process of oep-54 to extend permissions to other members.Reasoning
This project used to be called
tutor-contrib-multi
but that was a temporal name and now the definitive one is in place.Previously this was discussed at:
#577
And more recently:
openedx/openedx-k8s-harmony#9
However it looks like we tried adding people that were not core commiters and this further complicated everything. It should not be the case this time around.
Thanks a bunch
The text was updated successfully, but these errors were encountered: