In the Contributor Meetup a week ago we discussed the creation of a Devops related Working Group that is trying to focus energy and expertise around deployment of the platform. We currently have three groups that are focused on operations topics: Build, Test, Release (BTR), predominately focused…

I agree with this proposal. We need to strike the right balance between too few/broad and too many/focused working groups. I think that merging BTR with developer experience and devops will lead to more collaboration across a diversity of projects. For instance, many Open edX developers would have a…

I’m unclear on what this would mean in practical terms. In particular, my questions are: What would the responsibilities of the DevOps group be with respect to the subgroups? Would members of DevOps work on distinct issues/tickets from BTR and DevEx or would it be more of a coordinating group just…

Perhaps I can try to answer that one :slight_smile: The way I see it, the BTR, developer experience working groups and future efforts aimed at improving the Kubernetes integration have a lot of overlap. That’s perfectly fine; it’s actually great that people are working on closely related topics. Bu…

Thanks for your thorough response! To further clarify, would the flow for a particular project be something like: Someone in the community adds an issue to the DevOps GH project The DevOps WG decides if this issue fits best with DevEx or BTR or whether it might require another team entirely What…

Yes, very much so. And I don’t think we need to answer every question upfront, e.g., a what level Arch BOM should plug in. As long as there are mechanisms that increase coordination and communication, while preserving as much autonomy as practical, I think we’ll have a winning formula.

Any further thoughts from the community? Any other interest in chairing or co-chairing the group? If there’s no disagreement perhaps it’s time to talk about the practical steps to take to make this happen.

First I am happy to see this proposal/change, I definitely believe those areas intersect with each other as you already have said, and sometimes it’s important for a particular change (be it proposed from BTR, DevExp, or DevOps) to be communicating widely so say if we do arch change for BTR it do…

[image] e0d: Any further thoughts from the community? Any other interest in chairing or co-chairing the group? If there’s no disagreement perhaps it’s time to talk about the practical steps to take to make this happen. I’ll start bootstrapping the various GitHub projects, Jira pages, etc. but…

[image] regis: Create the following project and make me (@regisb) an admin: https://github.com/openedx/devops-wg/ @regis I can help with this. Just to clarify, do you want a new repository, a new project , or both? Keep in mind that issues can be created in any repo, and then added to any numb…

[image] kmccormick: Just to clarify, do you want a new repository, a new project , or both? It would be great if you could create both. [image] kmccormick: Keep in mind that issues can be created in any repo, and then added to any number of projects. Right. I think it’s best if issues …

Proposal: Devops Interest Group Structure

Working Groups Build-Test-Release

Topic		Replies	Views
A Modest Proposal for Lilac and Beyond Build-Test-Release	6	1105	January 21, 2021
Contributors Meetup Async Update - August 19th, 2023 - September 1st, 2023 Core Contributors core-sprints , retrospective	11	1133	September 21, 2023
Contributors Meetup Async Update - March 2nd - March 15th , 2024 Core Contributors core-contributor , retrospective	3	339	March 19, 2024
Single GitHub project for all working groups? Working Groups	4	700	January 5, 2023
Contributors Meetup Async Update - August 5th, 2023 - August 18th, 2023 Core Contributors core-sprints , retrospective	0	267	August 18, 2023

Proposal: Devops Interest Group Structure

Related topics