It makes a lot of sense that he continues managing the repo if he has done so in the past.
I’d like to understand why the organization change? does this tutor plugin need to be in the core of the project? We have experience maintaining tutor plugins that are widely used but are still hosted in the edunext github org.
It’s also difficult to tell from @Ivan_Niedielnitsev 's commit history whether he’s a good CC candidate yet, so I’m hesitant to support his nomination right now. I’m glad to hear you’ll be mentoring him @Maksim_Sokolskiy , but I think this nomination should wait until he’s had a bit more time to work on the openedx?
Since the codebase for the cc2olx converter is hosted by the Open edX organization, we propose moving the Tutor plugin for converting Common Cartridge to the OLX format to the same Organization. This approach aims to enhance the value of cc2olx by integrating the accompanying Tutor plugin within the Open edX organization.
But you are right and there is no technical necessity to move the plugin.
While I am grateful to RaccoonGang for being willing to contribute and maintain this code, the truth is that the openedx org just has too many repositories currently Managing permissions, workflows, and upgrades for 200+ separate repos has taken a lot of Axim’s time… time that we’d rather be spending on maintenance and development. I propose two alternate paths forward:
Keep the plugin in RG’s org. The plugin is optional in the Open edX release, so it’s not strictly necessary that the code exist in the openedx or overhangio orgs.
Move the plugin’s code into a subdirectory of the cc2olx repo. This would be a somewhat new pattern, but I think it would be a good one, because it would tie together the maintenance and Python upgrades of the package and plugin without adding another repo for us to administer.
Regarding Ivan’s nomination–from what I can tell from his contributions so far, Ivan is a strong developer and good technical communicator! I think he will fit in well as a CC, but I would also like to see some more contributions from him first. If you re-open this nomination thread after he’s had the chance to make several more high-quality contributions, I imagine that it’d be a yes from me.
Managing permissions, workflows, and upgrades for 200+ separate repos has taken a lot of Axim’s time… time that we’d rather be spending on maintenance and development. I propose two alternate paths forward: