Topics

• Topics for Tuesday’s Arch Study Group

• Open edX

  • proposals

    • joining us at 1x a month Arch Tea

    • shared slack channels

  • community participating in our architectural work

    • Loci: Slack, tea-time, https://discuss.openedx.org, pull requests, OEPs, ADRs

    • What would success look like? What has to change to make it happen?

  • How to get Open edX community involved in decentralized devstack discussions and development?

    • Jinder Singh (Deactivated) ​will post in the Open edX Slack #architecture and on discuss.openedx.org to gauge interest and inquire about discussion venue preference

      • just created quick post in discuss.openedx.org: https://discuss.openedx.org/t/decentralized-devstack/3154

• e2e tests

  • Purpose/overview of how they work/infrastructure

  • Is there an inventory of all our e2e tests? e.g. which repos have them, which don’t

  • What's the difference between e2e-tests on build jenkins vs e2e tests for ecommerce (per https://edx-internal.slack.com/archives/CD9FTF8HW/p1598969607013300?thread_ts=1598967197.011500&cid=CD9FTF8HW)?

Backlog of Questions/Discussions

• React - Discussions Forum - editor input - draft JS

• Branding: How can we keep branded edX Strings separate from the open source code (right now English string values are also edX-branded string values)

• Future (when folks are not on PTO)

  • Q&A with Feanil on Inter-service Eventing

  • Observability with Robert

    • What are your biggest pain-points?

    • Any we should dive into (e.g JS Error alert fatigue)Type hinting: Do we want it? Everywhere or just in APIs? etc?

  • Shopping cart deprecation with Diana

    • lessons learned, knowledge sharing on dead code, etc.