openedx / open-edx-proposals

Proposals for Open edX architecture, best practices and processes
http://open-edx-proposals.readthedocs.io/
Other
44 stars 31 forks source link

OEP-64 Mobile Application Codebase Modernization #496

Closed marcotuts closed 1 year ago

marcotuts commented 1 year ago

Opening this OEP draft for community review and input.

Abstract As part of the discovery effort done for a funded contribution (FC-0011) we are recommending that the Open edX platform adopt newly built iOS and Android applications as the new default mobile applications for the platform moving forward, starting with the next named release. These new applications are rebuilt with MVVM architectural patterns and are fully rebuilt in Swift and Kotlin respectively. These new code bases should facilitate faster development cycles, improved pluggability and community contribution rates. Currently not all functionality is 100% identical to the existing mobile applications, but efforts are underway to improve pluggability and close common community requirements for the mobile experience.

The new mobile repositories are maintained by Raccoon Gang and can be accessed here:

The existing mobile repositories are maintained by edX / 2U and can be accessed here:

FYi @colinbrash, @e0d

openedx-webhooks commented 1 year ago

Thanks for the pull request, @marcotuts! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

sarina commented 1 year ago

@marcotuts Redwood!

e0d commented 1 year ago

I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

scottrish commented 1 year ago

@marcotuts As the mobile apps are distributed as binaries via the respective app stores, I don't believe AGPL is the appropriate license to apply. Can we adopt GPL-V3 instead?

e0d commented 1 year ago

@marcotuts As the mobile apps are distributed as binaries via the respective app stores, I don't believe AGPL is the appropriate license to apply. Can we adopt GPL-V3 instead?

Apache2 has been the license under which our mobile applications have been offered historically. It's a project approved license and appropriate for this case. My recommendation is that we re-license these applications to Apache2.

openedx-webhooks commented 1 year ago

@marcotuts 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.