...
- Where should we implement the feature?
- Option 1: IDA
- This doesn't seem like an appropriate solution since discussions should be tightly integrated into the LMS
- Note: the comment service will continue to live in its own repo (even if ported to Python: Comment Service Python Port)
- Option 2: pip-installed feature from separate repo
- Model on the ORA2 repo: https://github.com/edx/edx-ora2
- It will make it very easy for the Open Source community to choose not to install the feature
- Same challenges as ORA2 (see Managing multiple repo development)
- How do we do integration testing?
- How do we integrate static assets into the pipeline?
- It won't be possible to share code with edx-platform
- If the old UI remains then some portion will be duplicated into the new repo too
- Could live in the same repo with the new Python port
- 3 3: new Django app in LMS
- This has worked well for teams: https://github.com/edx/edx-platform/tree/master/lms/djangoapps/teams
- This is probably the most efficient option to go with
- Option 4: modify the existing UI in place
- The current code is sprinkled throughout the LMS which makes it hard to manage
- Changing the UI in place could complicate concurrently supporting the old UI
- Option 1: IDA
...