Some budget to be allocated for future milestones not yet in Jira that need additional definition work + partner input.
* Moderator email notifications / digest for flagged content or content in need of moderation * Learner email notifications / digest for updates “My Posts” content
Platform Cleanup and Health (redistributed to other milestones)
Improved Role & Permission Configuration for Discussions Apps
Support External Development for Medium + Full Support Integrations
Support Import / Export Persists Discussions Configuration
Import / Export Support to enable Github Authoring Workflow still persisting Discussions configuration
TBD --> v1.N Refactor from Ruby to Python (Cs-Comments-Service)
v1.1 Discussions Provider Selection UI & Piazza LTI Config within Studio (edx-admin)
Goal: Shift away from Django Admin configuration for third party forums, the initial implementation of Support level and feature matrix
Scenario:
An edX Developer can go to frontend-app-course-authoring in production to see “Pages & Resources” view with Discussions card.
Clicking the discussions configuration action pulls up modal with provider selection (hard coded list from code), and you can pick legacy edX or Piazza to start. (legacy edX option has no config options)
From this provider selection, the next button then pulls up modal with LTI configuration details for Piazza.
This release has basic hardcoded feature table needed for educator rollout of which features are supported.
Next Step: TNL task for tickets / stories to be ready for grooming - @David Joy (Deactivated)
Runbook: TBD
Details
“hard coded list” of discussions apps says name and also has a capabilities list. Piazza would have no capabilities by default, just LTI. edX Forums would have all capabilities. This informs the feature matrix and the configuration UI.
v 1.2 Legacy edX Discussions Provider Selection UI (edx-admin)
Goal: Enable configuration of legacy edX discussions from new discussions configuration / selection area.
Scenario:
An edX Developer can now configure the legacy edX discussion provider option and see the supported configuration settings are for legacy edX discussions.
v1.3: Yellowdig Discussions Plugin and Conversion
Goal: Enable Yellowdig Plugin to switch more courses over to new model
v1.4: New Pages & Resources View
Goal: New Pages & Resources View Live on Production, enabling easier configuration of course tools (Discussions only to start, to establish a pattern)
Questions: What tiles will we include in this milestone? A: for this milestone, just focus on Discussions. We don’t need this view to be available for course teams, so it doesn’t have to fully make sense.
Q: Existing API PRs?
Use Cases: edX admins can use this new page to configure discussions, rather than using django admin.
Runbook:
v1.5: Full Rollout of Pages & Resources View
Goal: Shift educators from old Pages view to new Page & Resources view in production
Use Cases: whatever isn’t in v1.2 that would let us deprecate the existing Pages view
v1.6+: Educator Preview of New edX Discussion Experience
Goal: PilotEducators enrolled in course with new discussions experience for ongoing feedback + comments
Next Step: How feasible to land / test / break up into more milestones?