16 Nov, 2021
Question: Ref to PR https://github.com/edx/edx-platform/pull/29262 , why is the tab reordering needed?
...
3. “It will not result in any data loss, but will just change how the topic structure is presented.”
...
28 Dec 2021
Question v1.6: We would prefer to review the UI and features of new discussions MFE on stage. What work needs to be done in to achieve this?
...
Anchor | ||||
---|---|---|---|---|
|
Question v1.6: As per current implementation, once we enabled new MFE (v1.6) for a course, new UI will be visible in Discussions tab. However, the discussion xblocks in the content will use the legacy UI. Are we ok with that? If no, what do we need to do?
Resolution: Marco: “If the work for having new UI within the content is a lot, then we can skip it. It not, then we can rollout the educator preview and afterwards, make the necessary improvements to have the new UI within content”. FYI:Kshitij Sobti
...
Question v1.6: Do we need to depreciate “/” before enabling the new MFE on stage?
Resolution: No. The new MFE uses same API as mobile app, which is already agnostic to “/”.
...
Question v1.6: Post deletion workflow is not specified in mockups.
...
Agreed
Pending …
We can design it like the “Close post” dialog box in Figma mockups.
...
Question v1.6 v1.7: In reference to the waffle flags and toggle buttons for the new MFE (v1.6) and in-context discussions/new topic structure (v1.7), how do the two options co-exist?
...
Waffle flags | v1.7 - Disabled | v1.7 - Enabled |
---|---|---|
v1.6 - Disabled | No change | Remove possibility for this to happen. How? |
v1.6 - Enabled |
|
|
Resolution: Pending …
...
Question v1.7: We need to figure out the mapping scheme between courses using legacy backend that want to switch to v1.7.
...
Resolution: Pending …
...
Comment v1.9 v.10: It’ll be really helpful to connect someone in edx who is proficient in ruby, for reviews on PRs for to cs_comment_service
repo.
...
Info v1.9 v.10: Management command for creating stats for past user actions has been deferred until the use case calls for it. For now, potential use cases include:
...
Comment: Aamir: We need to figure out the qualification criteria for automated migration of courses.
...
18 Jan, 2022
Discuss: v1.6 How about deletion dialog boxes as seen below. OC can take a look at the paragon details.
...
Update: https://www.figma.com/file/LVFnO9oRHYiamoicZuXDAC/Discussion-page?node-id=4066%3A368050
...
Discuss: v1.6, v1.7, v1.9, v1.10, v1.11, v1.12 Rollout sequence
Step | Feature | Audience | Additional details |
---|---|---|---|
1 | New MFE (v1.6) | Educators |
|
2 | Learners area (v1.9, v1.10) as part of new MFE | Educators |
|
3 | Content edit/close reasons (v1.11, v1.12) as part of new MFE | Educators |
|
4 | New MFE with learners area and reasons (v1.6, v1.9, 1.10, v1.11, v1.12) | All |
|
5 | In-context discussions (v1.7) for new courses | All |
|
6 | In-context discussions (v1.7) for existing courses | Educators |
|
...
How many courses in past 6 months have been created?
How many of those can benefit from v1.7?
How many have 0 discussion xblocks? Real easy conversion.
How many have one discussion referenced in several xblocks.
???
...
Question: v1.6 Will the new MFE be automatically enabled for Teams?
Resolution: No information about Teams at the moment. Will need to explore in future.
...
Question: v1.6 Can we enable the new MFE on stage now?
...
Good to enable on stage.
Default URL has been changed. This may require updating paths elsewhere.
Flags that need to be enabled: No flags need to be enabled to get it working. We can visit MFE URL for any existing course.
...
Question: v1.9 v.10: What UI when stats don’t exist for a learner in a course?
Resolution: Pending …
...
25 Jan, 2022
Discuss: v1.9 v.10: Users are facing problems on production when editing a post, comment or response (as seen below and in CR-4472 and CR-4474). We think this maybe due to PRhttps://github.com/openedx/cs_comments_service/pull/356 deployed on production on 18th Jan. Two potential solutions are:
...
Resolution: Kshitij Sobti will assign tickets, intended to be picked up by OC, to himself and mark them as prioritised. Asad Azam Aamir Ayub will assign tickets, intended to be picked up by Infinity, to themselves and mark them as prioritised.
...
28 Feb, 2022
Discussion: v1.7 Stages of new topic structure rollout is as follows:
At present: Only legacy topic structure is available.
Status colour Green title DONE Transition period: This is a period where we would prefer limited number of NEW courses to try out the new topic structure and provide feedback.
We don’t want all course teams to see 2 edX discussion providers (legacy and new topic structure).
We want to have legacy topic structure as the default topic structure
Status colour Green title Done We want to have some mechanism to enable the new topic structure on NEW courses offered by interested partners.
Status colour Purple title need grooming
Future: The new topic structure will be default for NEW courses. Legacy topic structure will be supported for running courses.
Status colour Purple title need grooming Migration: A running course wants to transition to the new topic structure. This is only possible under certain conditions.
Status colour Purple title need grooming
...
We keep the 2 edX providers on frontend named:
edX
(legacy topic structure)edX-new
(new topic structure)
Only the global staff will be able to see
edX-new
provider.In our partner portal post, we’ll ask partners to contact their respective edX support teams to get the new topic structure configured.
Once a partner support team receives the request, they’ll ask infinity to configure the new topic structure.
Infinity team will configure the
edX-new
provider for the course(s).Once
edX-new
provider has been configured on a course, it will be visible to the course team (Can we easily implement this? Asad Azam ). Course team can then make necessary changes in configurations.Once
edX-new
provider has been configured, can they easily go back to the legacy topic structure (with help from edX staff)? Kshitij Sobti
...
1 Mar, 2022
Question: v1.6 discussions MFE UI looks zoomed out than the original designs available in Figma
Discussion /solution: the default sizes in paragon are larger than the Figma we may have to apply class “small“ to match designs with Figma.
...
9 Mar, 2022
Discussion: v1.7 Orphaned posts
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Preference is to decouple the clean-up work and maybe groom and implement in future.
...
Discussion: v1.7 How course-reruns will opt-in to new topic structure?
Resolution: ADR coming up. Will be helpful to other people as well.
...
28 Mar, 2022
Discuss: v1.6
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Discuss: https://2u-internal.atlassian.net/browse/INF-220 Discuss
Resolution: https://2u-internal.atlassian.net/browse/INF-210
Topics: All topics are already loaded and can be searched on the frontend, similar to legacy experience.
Users: Usernames are present in platform and cs_comment_service both. However, its better to fetch users from cs_comment_service because user stats are returned too. Kshitij Sobti will explore how much of an effort it will be to search partial usernames.
Discuss: https://2u-internal.atlassian.net/browse/INF-210
Resolution:
abuse_flagged_count
property of a post keeps count of any responses or comments that have been reported. Infinity to explore this further.
Discuss: Learner area new UI
Resolution: Kshitij pointed out that this new UI may not require modifications in cs_comment_service except for fetching threads that a particular user has interacted with. For threads, there are two options that Asad Azam will explore further, in the order below:
Use legacy API (which may need modification to make it compatible with REST framework)
Modify the newly created cs_comment_service API to fetch threads