@braden @lpm0073 @Andres.Aulasneo @gabor @keithgg @regis @jhony_avella @Felipe @MoisesGonzalezS @Neo
To follow-up on the discussions in OEP-59: Deploying Open edX on Kubernetes Using Helm by bradenmacdonald · Pull Request #372 · openedx/open-edx-proposals · GitHub and get everyone up to date, would it be useful to schedule a follow-up to our last synchronous meeting? When we meet it also usually boosts the progress and decision-making, too 
And also, discussing with @Kelly_Buchanan this week we realized that there isn’t currently a good community working group to discuss this type of collaboration, and many other DevOps topics. The closest is the build-test-release working group, but it has its hands very full with managing the releases, and is understandably focused on it.
Maybe our current group could be a good starting point for a more general DevOps working group? From past experiences in other areas of Open edX, having regular meetings helps to find ways to collaborate more, and keep the momentum of initiatives going. It could also help liaising more with people from DevOps at 2U, which was what prompted this realization in the discussion with @Kelly_Buchanan – as 2U doesn’t use at all the named releases, the build-test-release discussions are often pretty far from their concerns.