[BD-14] Sync 2020-08-17 and 2020-08-20

Owned by Kyle McCormick (Deactivated)
Last updated: Jan 14, 2021
4 min read

  • Demo & discussion

    • Questions/comments

      • Nimisha: Validation on organization entry? Drop down?

        • We have server-side validation, which is great for now.

      • Marco: Probably keep assets and source for debug-only.

        • Kyle: Or edx-staff-only

    • HTML, Video cannot be edited currently. Studio endpoints are 500ing.

      • Tasks exist for Studio PRs to fix some of these.

      • @Former user (Deleted) - send @Dave Ormsbee (Deactivated) and @Kyle McCormick (Deactivated) info on these issues.

    • Library Listing

      • Nimisha: Anticipate need for searching, sorting, filtering, large number of libraries

      • Dave: Keep permissions in mind too with indexing

  • Communication on UX design, decisions

  • Rollout

    • All at once? Iterative?

    • Marco: Would it be easier to roll out specific types of libraries? (video-only, problem-only, etc)

    • Adolfo:

      • Legacy libraries can be created as before, no backwards-compatibility breakage

      • Plan was to roll out Source from Library XBlock for blockstore libraries only

    • Nimisha: Keep migration separate from rollout.

    • Dave: We need not to lose sight of importance of removing old libraries before wrapping up project.

  • Review project status

    • In review:

    • 43% of hours used.

      • How do we feel about the feasibility of meeting the goals of the project within the allocated hours?

    • Let’s find a better way to share the status of project roadmap.

    • Walking through Discovery doc (Kyle’s notes)

      • Integration testing: Do not do now; edX may just handle making this framework.

      • Nimisha: Keep metrics in mind. Be able to tell how many people are using these new features. Will be its own action item, but flagging now.

      • Dave: Library types: Complex/Video/Library. Why have these different library types?

        • Complex was anticipated to be harder because of authoring UI, which would involve structure.

        • Are the different library types any different, or just a thin veneer?

          • The latter.

      • Studio author view is not suited for presentation in React for certain blocks.

      • Elasticsearch - We are going from version 1 to version 7.

        • Keep this in mind when adding indexing/searching code.

      • Optimizations for library search

        • Will likely take until September, and some future optimizations may come out of it.

        • This affects LabXChange as well.

        • Would be good to use metrics and then leveraging them via NewRelic, to become more informed about these optimizations.

      • Is Organization app installed in stage/prod?

        • Yes, but not in edge

        • We should probably use that by default

    • Walking through Discovery doc (Marco’s notes):

      • High level, taxonomy is at risk of not being done this calendar year.

      • F1 / F2 - Shifted goal to adding Blockstore to edx-platform

        • Usman may be able to join / support project as a CC here.

      • F3 Create Empty "Library Editor" React Microfrontend (MFE) w/ Feature Flag - Completed

      • F4 - Implement New Studio Homepage Header

        • Build simpler version, moved full item to Milestone 3.

      • F5 - MFE Test Suite

        • expectation is JS unit tests / component level tests.

        • Integration tests? - don't need to be retested, this is handled by frontend-platform

        • Eventually cypress e2e tests may be added, but can skip this for now.

        • Can push this to Milestone 3 for now.

      • F6 - Library Block Count Limit - Completed

      • L1 - Show Basic Library List - Mostly Done, Needs Acceptance & Wire Details

      • L2 - Library List Page: Create a new Library - Mostly Done

      • L3 - Specific Library Types (Video/Problem) - On Track for Milestone 2

        • Complex, Video, Problem, etc.

      • L4 - Library List Page: Index Libraries in ElasticSearch - Up for Review

        • This is actively in upgrade from v1 to v7.

      • L5 - Library List Page: Optimization and extra fields - Not Started

        • Index in elasticsearch and leverage this

        • (Usman may also help here as core committer)

      • L6 - Library List Page: Searching & Filtering - Backend In Review , Front end in progress

        • Organizations not enabled by default currently, but this will depend on this.

      • L7 - Library Listing Page: Sorting

      • M1 - True MVP Authoring Page - Port of Ramshackle done

        • A Milestone is a port of Ramshackle, this gets us versions of all the milestones

      • M2 - "Source From Library" XBlock - In Progress

      • C1 - Library User Access Configuration Page - Backend is done, Front end in progress

      • C2 - Library Details Page - On track for September

        • metadata outside of blockstore at the library level, relies on bridgekeeper

      • C3 - Library Content Licensing - On track for September

        • Follows course pattern - react re-implementation (Schedule & Details page - Course Licensing section)

      • U1 - Improve "Source from Library" Workflow

      • All after this won’t be in September.

      • A1 - Modernize CAPA Problem Editor

      • A2 - Modernize Video XBlock Editor

      • A3 - New Authoring Page: Video/Problem-Type Libraries

        • This represents the UX reviewed improvement to authoring, building on MVP of ramshackle port.

        • Targeted for September

      • A? - New Authoring Page: ElasticSearch Index

      • A? - New Authoring Page: Complex Libraries w/ Search & Filtering

      • A? - New Authoring Page: Sorting by Date Added

      • A? - New Authoring Page: OLX editor?

      • A? - New Authoring Page: Asset Files?

      • A? - Preview View?

      • A? - New Authoring Page: Search XBlock Content?

      • E1 - Backend API to import modulestore library export to Blockstore Library

      • New - Metric Tracking - Requirements TBD

  • Question: Edge?

  • Staging environment

  • Meta

    • Feedback?

    • Issue tracking

      • Currently:

        • OpenCraft makes action items visible via Open Action Items and Status Updates on wiki page.

        • edX makes action items visible via “Relevant Jira Stories” macro on wiki page, which really just pulls in every ticket on the BD-14 epic.

      • Is that working for everyone?

    • Meeting cadence

      • Back to once-a-month? More? Less?

      • Short answer: More often. Meeting later this week.

Action items

  • Marco Morales share wires of header patterns + library list view for L1

  • Kyle McCormick - internal edx follow up on C1 for architectural patterns

  • Kyle McCormick - Look into enabling ORGANIZATIONS_APP by-default. We will eventually need to enable it on Edge as well. https://openedx.atlassian.net/browse/TNL-7425

  • Adolfo R. Brandes - One of: Update/clone spreadsheet to include status updates, update wiki page with “high-level” project status, provide access to an OpenCraft Jira board, or something else like those. (Done up until Milestone 2 - see “Project Timeline” above.)