Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

  • 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.

    • 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

  • Staging environment

  • Meta

    • We need to define scope for next span of work.

    • 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.

  • No labels