Here’s what @Rebecca Graber (Deactivated) and @Kyle McCormick came up with, but we can always change it:
We aim to improve the experience for developers working on the Open edX platform by:
identifying what qualities make a developer experience “good” (low on-boarding overhead, easy testing, etc.), with understanding that needs will vary between different members of the community;
identifying the gaps between our current developer experiences and the desired state;
actively improving our current developer processes and tools;
empowering the community to build and maintain tooling extensions that suit their needs; and
where possible, aligning different groups of developers on shared development solutions.
The Working Group will serve as a space for folks who are collaborating on developer experience projects to seek help, share knowledge, discuss ideas, and align their work with one another. We are likely to focus both on high-level questions (“what would the ideal developer experience be?”) and concrete improvements (“what will we do this month to make Tutor/Devstack easier to use?”).
At this time, Working Group itself will not be taking on maintenance responsibilities for any component of the Open edX developer experience.