[DEPR] tutor-ecommerce deprecation

[DawoudSheraz]

Open edX will archive the following ecommerce repositories on September 9, 2024.

• ecommerce
• ecommerce-worker
• frontend-app-payment
• frontend-app-ecommerce
• ecommerce-scripts

This implies we will be archiving tutor-ecommerce as this plugin is meant for setting up e-commerce and would no longer serve the purpose once upstream has been deprecated. One last release for tutor-ecommerce may be done before the archive. After that, no new release will be done for this plugin. Officially, it will no longer be maintained.

• https://discuss.openedx.org/t/oscar-based-ecommerce-stack-deprecation/13760
• https://github.com/openedx/public-engineering/issues/22

Action Items

• [ ] Release a new version
• [ ] Add a note about deprecation at the top of the README
• [ ] Mark the repository as read-only
• [ ] Update https://discuss.openedx.org/t/tutor-maintainers/7287
• [ ] Make sure that newer versions are not advertised in the TPI (nightly/sumac) https://github.com/overhangio/tpi
• [ ] Remove the plugin from tutor[full] (in nightly).

[OAburub]

I think there should be another tutor plugin that implements some or all of the replacements mentioned in the original deprecation post. I agree with the deprecation, but the existing replacements take a lot of work and effort to implement into a tutor installation.

[DawoudSheraz]

I think there should be another tutor plugin that implements some or all of the replacements mentioned in the original deprecation post. I agree with the deprecation, but the existing replacements take a lot of work and effort to implement into a tutor installation.

Hi. You can look into https://github.com/openedx/openedx-wordpress-ecommerce as a potential replacement. It does not have a Tutor plugin but it is simple enough to be configured with an existing platform.

[OAburub]

I think my problem was not clearly communicated. While I know solutions exist that communicate with the openedx API, instead of doing a one-command install of that that sets up the frontend, the backend, and integrates it in an MFE, and then manually configuring them and customizing them, the official solution becomes to install another site, configure it separately, build the frontend, configure how it links with the back end etc. It's less efficient, and consumes more resources. A tutor plugin that automates some of those steps and enables customization after installation will be majorly helpful.

Adding to this that processes like restarting the entire platform through commands will become disconnected with the addition of a separate marketing page

[OAburub]

this openedx/openedx-wordpress-ecommerce#84 achieves a part of what I'm asking to be done