trying to categorize the various features and tasks we need a development environment to do to see which ones we can make orchestration- and deployment-independent (eg: once we have all our Dockerfiles set up, we should be able to build images without regard to the eventual orchestration or deployment, but discovering related services will probably always be orchestration-dependent)
Collecting a lot of good specific devstack problems to help us both find quick wins and decide the future of the repo
I’m getting rid of the Paver assets code in edx-platform and rewriting it mostly in bash. If you are interested or have feedback here’s an ADR: https://github.com/openedx/edx-platform/issues/31605 . I’m going to merge that soon so let me know asap if you have any concerns!
ShellCheck will be available to add to all repo’s CI suites soon, as applicable.
I was playing a little bit with plugins and index, which is an interesting opportunity
Each challenge should have a follow up action.
If you have an idea for follow up actions, add it.
Or if you aren’t sure, leave it blank.
We’ll discuss all actions either way.
Getting lost in the edx-platform weeds on the way to making tutor dev easier
Lmk if you need my help on anything or I’ve been missing anything in the past few weeks -Kyle
What is the process of adding a plugin in public tutor indexes?