Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
panelIconId1f6a7
panelIcon:construction:
panelIconText🚧
bgColor#FFFAE6

This is a work-in-progress!

Date:

Info (Delete before publishing): This report is intended to be, as much as possible, short and sweet. It's mostly fill-in-the-blanks. The audience for all sections is "whole community"; there are optional "deep dive" sections where you can be more technical.

Introduction

The {working_group_name} focuses primarily on {areas_of_focus_and_interest}. Our primary goal(s) is/are to {goals}. Optional: group guiding principles or vision statement.

Consider this report as a compilation of what we’ve done over the past year, what we’re looking at doing in the next 6 months, and a wider vision of the group’s future beyond that.

Accomplishments

Over the past year, our major accomplishments were:

  • Accomplishment 1; 1-2 sentences of importance/impact

  • Accomplishment 2; 1-2 sentences of importance/impact

Further, we’ve made significant progress on the following initiatives:

  • In-progress initiative 1; 1-2 sentences of importance/impact

  • In-progress initiative 2; 1-2 sentences of importance/impact

[optional] We continue to engage in a set of ongoing tasks; these tasks are work we need to be sure we’re doing on a regular basis, but we don’t want to lose sight of their importance. Those tasks are:

  • Ongoing task 1; 1-2 sentences of importance/impact

  • Ongoing task 2; 1-2 sentences of importance/impact

...

Date:

Introduction

The DevX Working Group focuses, unsurprisingly, on improving the experience for developers contributing to the Open edX platform and its extensions. It is under the DevOps Working Group umbrella.

Accomplishments

Over the past year, we:

  • Formed in December 2022, and have since had our first few sync meetups & async updates.

  • Delivered incremental improvements to the Tutor development experience, including: plugin API simplifications, a new patch-listing CLI, simplified provisioning instructions, and edx-platform build speed-ups.

  • Did preparatory work for bigger projects in 2023 (see next section).

Concrete Plans - Next 6 Months

Over the next six months, {working_group_name} has some really exciting work queued up. We hope to drive {key metrics, description of impact, etc}. Our primary goals are to {work on / complete / another word} the following tasks and projects:

  • Task/project 1; 1-2 sentences of importance/impact

  • Task/project 2; 1-2 sentences of importance/impact

If applicable: Links to roadmaps/GitHub projects/important wiki pages/etc

Optional: We’ll provide a deeper dive into (name project(s) you’ll deep dive into) later in this report.we’ll be:

  • continuing comparative research into development environment options,

  • continuing development of metrics for measure the developer experience,

  • continuing to make Tutor work better with local copies of repositories, and

  • completely rewriting the edx-platform asset processing system (ADR) for speed and simplicity.

Our board: https://github.com/orgs/openedx/projects/37/views/1

Our top-level initiatives and epics: https://github.com/openedx/wg-developer-experience/issues/1

Future Vision for the Group (Optional)

Moving beyond the next six months, the {working_group_name} is really excited about making progress in {areas of interest}. Describe why these areas are interesting/important, and what their intended impact is. Include as much information as you wish here, but short and sweet is also OK.

Deep Dive: Accomplishment/In-progress Initiative/Ongoing Task/Concrete Plan (Optional)

Use this section to write or link to deep dives into any of your accomplishments or initiatives that would benefit the community to know more about. You can assume readers at this point will have the background knowledge to understand this being written in industry jargon. You may have as few or many “Deep Dive” links as you’d like. If you don’t have a place to post deep-dive content at the moment, consider posting them as blog posts on the Open edX siteGoing forward, we’re going to continue to simultaneously:

  1. Make Open edX itself simpler, so that its developer tooling can be simpler.

  2. Improve Tutor for Open edX development.

  3. Research and compare various development environment solutions, hopefully landing on a cohesive development environment vision.