-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Extract non-Core apps into Hooks-based platform plugins #36184
Comments
@kdmccormick Do the above small Django apps (located in openedx/core/djangoapps/) align with the Hook-Based Plugins initiative in Open edX? Given their size and scope, would they be suitable for conversion into hook-based plugins ? |
I am working on survey app. |
I'd like to better understand the end goal of this. Is the idea that these would be converted to being hooks-based while staying in edx-platform? Be moved out into a common repo? Separate repos? |
The primary objective is to extract them from edx-platform and migrate them to a new repository as hook base plugin. Please let me know if you have any further questions or suggestions. |
@awais786 Sorry for not getting back to you. survey seems like a great app to start with, and your approach of extracting into a separate repo sounds right to me. |
The survey app was built in edx-platform at least partially because it calls into a bunch of things that are not part of any stable APIs or plugin interfaces. I'm worried that we will lift some of these apps out with those functional dependencies in place. If we do that and we're not deprecating them, then we're just making maintenance harder because it will be more difficult to detect regressions and to maintain more repos through upgrade cycles. There are some things here that could come out easily, like geoinfo and maybe zendesk_proxy (though we should probably see if we can just DEPR Zendesk, because edX built it and I don't think they run it any longer). |
The text was updated successfully, but these errors were encountered: