# Goodbye DevX Working Group... hello Tutor Users' Group! **URL:** \ **Category:** Dev Experience\ **Tags:** devstack, tutor, announcement\ **Created:** [January 29, 2024, 4:37pm UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200 "2024-01-29T16:37:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\ **Post date:** [January 29, 2024, 4:37pm UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/1 "2024-01-29T16:37:23Z")
## Background šŸ“š In 2022, we [started the Developer Experience Working Group](https://discuss.openedx.org/t/introducing-the-developer-experience-working-group/8834). At the time it wasnā€™t clear if [Tutor](https://docs.tutor.edly.io/), [Devstack](https://github.com/openedx/devstack), or [something else](https://openedx.atlassian.net/wiki/spaces/AC/pages/3647700997/Development+Environment+Notes) would be the ideal development environment for everybody. Great progress has been made since then: - Built-in ARM support for both Tutor and Devstack. - Persisted bind-mounts for Tutor, making application & package development much easier. - edunextā€™s [Tutor Version Manager](https://github.com/eduNEXT/tvm). - Various other Tutor improvements, including: build parallelization, patch listing, new plugin hooks, and the ā€œdoā€-jobs framework (more details in the [tutor changelog](https://github.com/overhangio/tutor/blob/master/CHANGELOG.md)). - simpler & quicker [edx-platform static asset compilation](https://github.com/openedx/edx-platform/blob/master/docs/decisions/0017-reimplement-asset-processing.rst) - [management commands for loading dev data](https://github.com/openedx/edx-django-utils/pull/369). - Grove-hosted PR sandboxes (more info to come on this laterā€¦) - [bundling xblock-utils with the XBlock package](https://github.com/openedx/XBlock/issues/675) - More volunteers stepping up to [maintain and improve Tutor and its plugins](https://discuss.openedx.org/t/tutor-maintainers/7287). Despite all this work, the DevX meetings themselves have become quiet. With resources changing and everyone busy with their various projects, we [spent our last meeting discussing a new structure](https://openedx.atlassian.net/wiki/spaces/COMM/pages/4026073094/Future+of+DevX+Working+Group). So, I have **two announcements** and **one proposal** : ## Announcement: The DevX Working Group is dissolved! šŸ’„ - Tutor improvements and maintenance will be continued by [Tutor maintainers](https://openedx.atlassian.net/wiki/spaces/COMM/pages/4026073094/Future+of+DevX+Working+Group). - Devstack ā€œkeep-the-lights-onā€ maintenance will be done by 2U. - The [Developer Data tool](https://github.com/openedx/edx-django-utils/pull/369) will be looked at by [Maintenance WG](https://discuss.openedx.org/t/introducing-the-maintenance-working-group/12159). - Platform simplification will be continued by [Maintenance WG](https://discuss.openedx.org/t/introducing-the-maintenance-working-group/12159) and Open edX repo maintainers. ## Announcement: Join the Tutor Usersā€™ Group šŸ¤ Itā€™s become clear that there is an acute need to support new Tutor users and plugin developers. Itā€™s also clear that Tutor maintainers benefit from hearing feedback from people who are using the tool. So, I will host **one-hour [usersā€™ group](https://en.wikipedia.org/wiki/Users%27_group) every other week** for sharing help, tips, and feedback on **using Tutor** and **developing Tutor plugins**. Bring your questions, and get ready for some live debugging! Expert or newbie, all are welcome. Please let me know which times would work for you: _Poll ([view on site](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/1))_ Just like DevX WG was, the Tutor Usersā€™ Group will be nested under the ā€œDevOps Working Groupā€ of which @regis is the chair. ## Proposal: Deprecate Devstack in favor of Tutor šŸŒ† The Open edX project has nominally supported both Devstack and Tutor as developer environments for a while. I know there are still a couple pain points with Tutor, particularly build times and MFE development. I also know that **these issues are solvableā€“especially if we focus on them**. I think itā€™s time to move on from Devstack and focus our collective efforts on Tutor. Together, with efforts of the Tutor Usersā€™ Group and Tutor Maintainers, Iā€™m confident that Open edX project can support a single excellent development & production deployment tool. Please comment your thoughts below. If there arenā€™t serious objections, I can officially propose this using the OEP process [just as we did when we switched from the Native Installation to Tutor](https://docs.openedx.org/projects/openedx-proposals/en/latest/architectural-decisions/oep-0045/decisions/0001-tutor-as-replacement-for-edx-configuration.html). ---
**Author:** ![Emad](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/emad/32/8930_2.png) [@Emad](https://discuss.openedx.org/u/Emad)\ **Post date:** [February 26, 2024, 7:46am UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/2 "2024-02-26T07:46:58Z")
Looks like a tie between Monday and Tuesday. I can vote on Tuesday if this meeting is biweekly (like before) and not scheduled on the same day as the ā€œKubernetes & Large/Multi Instances DevOps collaborationā€ and ā€œLTI Working Groupā€ meetings. https://calendar.google.com/calendar/u/0/embed?src=c_v86shrnegshsqgp4fj2k94u7bc@group.calendar.google.com&rm=minimal Regarding the depreciation proposal, I think people would love using Tutor over DevStack! šŸš€ But as you mentioned, we should find the reasons why people are fighting against adopting Tutor over DevStack and start fixing them. ---
**Author:** ![zhancock\_edx](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/zhancock_edx/32/3589_2.png) [@zhancock\_edx](https://discuss.openedx.org/u/zhancock_edx)\ **Post date:** [March 20, 2024, 1:49pm UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/3 "2024-03-20T13:49:59Z")
@kmccormick did this group ever get scheduled? I donā€™t see anything of the WG calendar. Iā€™m hoping to keep tabs on Tutor developments on behalf of 2U. ---
**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\ **Post date:** [March 20, 2024, 3:55pm UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/4 "2024-03-20T15:55:02Z")
Thanks for your patience folks šŸ™ Letā€™s get this going. šŸ”Š We will be meeting **every other Monday at 14 UTC, opposite weeks Build-Test-Release.** So that first meeting would be this coming **Monday, 25 March** at 14:00 UTC (10:00am in Boston, and 19:00 in Lahore). [Weā€™ll take notes here](https://openedx.atlassian.net/wiki/spaces/COMM/pages/3583016961/Tutor+Users+Group), and you can add agenda items ahead of time, but you donā€™t have to. See you there! FYI [@tutor-maintainers](https://discuss.openedx.org/groups/tutor-maintainers) . ---
**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\ **Post date:** [November 18, 2024, 2:25pm UTC](https://discuss.openedx.org/t/goodbye-devx-working-group-hello-tutor-users-group/12200/5 "2024-11-18T14:25:20Z")
Hi again šŸ‘‹ The attendance of this group has dwindled over time. When we do meet, it is usually a collection of advanced users discussing how to improve Tutor rather than new users and plugin authors looking for help and feedback. I have to assume that this is because Tutorā€™s documentation and the Open edX forums have become wildly successful at giving Tutor users all the help they need šŸ˜‰ Of course, it is also possible that someone else would do a better job managing the group than I. So, I am stepping down as facilitator, and I call on anyone who is interested to take my place and run the group however theyā€™d like! If there are no volunteers before our next scheduled meeting (Monday 2024-12-01), then weā€™ll consider the group ā€œdeprecatedā€ and Iā€™ll remove the meeting from the public calendar.