Relating to this post, some of these repos are deprecated, and while 2U has largely stepped away from maintaining them bit by bit over the last few months, the role of maintainer is open:
Thanks for posting @Christopher_Pappas. I know weāve had some version of this up and down for a while but for the sake of clarity. If we donāt hear anything by 2024-08-06T04:00:00Z Iāll create a DEPR for all these repos and all the corresponding code in other repos related to it.
The plan will be to:
Deprecate these once the DEPR is accepted.
Have a separate DEPR the code in other repos that will provide a longer runway (6-months) for removal so that people have time to shift away from the un-supported code.
@feanil I will check with my team and get back to you. This has been the most difficult project to either let go or maintain. It is actively used in a project Iām working on.
If a couple of days is fine, I appreciate an extension.
Hi @feanil
We appreciate your efforts in addressing the state of the e-commerce repositories. @johanv26 and I are interested in stepping up as maintainers for the ecommerce and ecommerce-worker repositories.
Could you please provide us with the necessary next steps to formalize this commitment?
That sounds good, but Iām reluctant to have the backends be maintained if there are no maintainers for the front-end that is now required for those backends to work. Is there someone who could take the front-ends and collaborate with Andrey and @johanv26 ?
Also, @Andrey and @johanv26 you are not CCs on those repos at the moment but I think you could nominate yourselves based on the work you did to help test and review the Python 3.11/3.12 upgrades in those repos. That will be a pre-requisite to becoming maintainers there so probably best to get that going.
Johan, Andrey and I are concerned on the same specific project weāre working on. So, itās only the backend weāre looking at and we think the frontends arenāt that helpful at the moment because theyāre incomplete.
Iām still discussing with the customer and @jalondonot.
One key information that could be helpful is what was the historical cost of maintaining all the ecommerce components including MFEs.
The entire engineering capacity dedicated for that project is 5 engineers including infrastructure, customer support and feature development.
I think given the complexity of work needed and the fact that all the concerns are from the same underlying project which would have its capacity split among other work as well, it doesnāt make sense to continue maintaining this particular set of commerce tools for the whole community.
Given that we havenāt gotten someone to step up to steward all of the work needed to make this stable and usable for the foreseeable future and given that the underlying django-oscar project has dropped support for MySQL our default database, I think it makes the most sense to deprecate the current commerce system and document alternatives as we have been discussing in tCRIL Funded Contribution - WooCommerce Discovery - #3 by mafermazu
Sounds good, yea, I think we need multiple options and a clear base interfaces so that people can integrate what they need. For now at least the enrollment API is pretty straightforward to integrate with, and hopefully with frontend slots, it will become easier to jump back/forth between whatever commerce system people are using and the edx-platform UIs.