During our last meeting, a discussion topic regarding Forum V2 was brought to BTR’s attention:
Forum v2 integration is pending merging of this PR. There is fear that we are too long in the testing phase to merge it. I would like to argue in favor of adding this feature to the release.
Because of the impact of backporting new features in the middle of testing a new release, we’d like to have an additional meeting to decide and discuss our next steps. Join us if you’re interested in discussing Forum V2 inclusion in the Sumac release!
Here’s today’s transcript so you have full insight into the discussion (starting from min 20):
Additional Context
To better understand Forum V2 and its improvements, please refer to these documents:
BTR Forum Sumac Backport Discussion
Wednesday, November 13 · 3:00 – 4:00pm UTC
Google Meet joining info
Video call link: https://meet.google.com/rjj-tvjg-pcc
@regis, feel free to add additional context if needed!
These key points from today’s discussion will be revisited in the next meeting, where we’ll make a final decision on Forum V2. Info from MIT, 2U and other folks will help us ensure all stability and compatibility needs are addressed.
Forum V2 Migration Overview
Migrates the forum from Ruby to Python and from MongoDB to MySQL.
Aims to streamline codebase and enable easier future development.
Forum V2 includes a migration command to transfer forum data from MongoDB to MySQL. This process is non-destructive, retaining MongoDB data while adding to MySQL.
Merge PR 35671 Concerns
PR #35671 is ready for merging, but timing is a concern.
High confidence in stability, though merging now increases release risks.
Testing Challenges
Integration requires testing for both MySQL and MongoDB configurations.
Developers of Forum V2 (edly) offered to take on critical testing responsibilities, easing the burden on testers.
Backporting Implications
Backporting Forum V2 adds release complexity and risks, especially under tight timelines.
Options include toggling Forum V2 off by default or offering it as an experimental feature.
Default Behavior Proposal
Plan to enable Forum V2 in the Sumac sandbox for testing.
Default inclusion will depend on test results, fallback to optional if issues arise.
Please, review the transcript for more details. Or ask here if you have any questions!
I’m sorry I was unable to attend the meeeting today (11/13) or find someone to replace me.
Were there any decisions made?
Our plan at MIT Open Learning is to deploy the new forum service alongside the old one, so we can test it. If it isn’t backported to Sumac, testing will be limited to our deployment that follows edx-platform master.
We will share our testing results. If there is a testing plan for the forum code, we will follow it – although we don’t use Tutor.
Forum v2 support will be merged in edx-platform in Sumac.
Platforms not running Tutor will keep running forum v1 by default.
Platform running Tutor will run forum v2, but with different data backends:
Existing platforms will keep using MongoDB: instructions to migrate will be printed on tutor ... launch and be available in the tutor-forum README.
New platforms will default to the MySQL backend.
Platforms running Tutor and which need to stick to forum v1 will have to create their own Tutor plugin, likely based on top of this version.
Legacy forum v1-related code will be removed from edx-platform before Teak.
Legacy MongoDB related code will be removed from forum v2 before Teak, with the exception of the migration script, which will remain available in Teak.
if you have any questions!