Versions Compared

Old Version 4

changes.mady.by.user Kyle McCormick

Saved on

compared with

New Version 5

changes.mady.by.user Kyle McCormick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Topics

Info

Please enter your proposed topics for discussion here.
In Lean Coffee Style (link1, link2), we will vote on which topics the group wants to discuss and time-box the discussion to 10 or 15mns → 5mns (if re-voted) → 5mns (if re-voted).

Blended Projects

Moving forward with:

  • Code health

    • Implement list of desired repo health checks (and possibly suggest new ones)

    • For the pylint cleanup

    • edx-platform cleanup

  • Frontend maintenance

Voting proceeded as following:

  • ⭐ was used first, for each participant’s favorite top-level, bolded category

  • 🌋 was used next - each participant got 3 of these votes, and put them on specific items they wanted to see happen

  • 🌴 was then used only inside Code Health to pick your one, top favorite item.
    (italicizedblue = probably self-contained effort; red = will probably need more hand-holding with edX engineers; bold green = on blended board)

  • Misc

  • Code Health ⭐⭐⭐⭐

    • Implement list of desired repo health checks (and possibly suggest new ones) 🌴 🌴 🌋

      • What environment is running in prod? (Python and Ubuntu versions, etc.)

      • Does this service still use ansible for deployment?

      • Do the Ansible and Dockerfile match in important respects?

      • Is there any non-ASCII in setup.cfg?

    • Fix remaining issues with using Black (or similar), start using it to standardize code formatting 🌋 🌴

    • edx-platform code health

      • Find and fix import direction issues in edx-platform (make it more logical, easier to move things out); e.g., fix it so things under common don’t import from lms packages, etc. 🌋 🌋🌋 🌴

        • maybe as part of or as a result of this: restructuring the platform to be more comprehensible/approachable

      • Not a new idea, but giving a +1 for the pylint cleanup and other edx-platform cleanup -Kyle 🌋🌋🌋 🌋 🌴 🌴🌴🌴

        • Pain points:

          • Escaped bugs

          • Can’t leverage pylint feedback in edx-platform IDE

  • Developer Experiences

    • Removing paver 🌋 🌋

    • Ditching karma/jasmine in favor of jest - many tests could probably be re-written fairly easily

      • (karma/jasmine are much slower and more finicky)

    • Fixing legacy frontend tooling

      • Anything more specific here?

      • e.g., running JS Tests locally - running single tests 🌋

  • Testing ⭐

    • Prototype consumer-based contract tests (Pact) (may be red)

    • If we decide they’re worth keeping – Improving our end-to-end tests

      • or implementing a new suite on better technology 🌋

      • Migrate our remaining browser automation tests (a11y, e2e, etc.) from bok-choy/Selenium to cypress or playwright

  • Frontend Maintenance ⭐⭐

    • DEPR-100 - deprecation and removal of old frontend libraries: frontend-auth, frontend-i18n, frontend-analytics, frontend-logging, frontend-base 🌋

      • Some MFEs may be private and can’t be updated via outsourcing.

    • Transitioning our ES6 repos from eslint-config-edx to @edx/eslint-config.

    • Upgrading our ES5 code to use all the ES6 language features that are now supported by our supported browsers, hopefully to aid the removal of our ES5 eslint-config-edx configuration.

...