Note: lists.cloudfoundry.org will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
- Introducing OSS Release Integration Team
Re: Introducing OSS Release Integration Team
Cornelia Davis <cdavis@...>
Thought so. :-)
toggle quoted messageShow quoted text
Great news. Thanks for the detailed overview Amit!
Sent from my iPhone
On Jul 16, 2015, at 10:37 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
Ah, copy-paste fail! Zak is a Pivotal engineer, not IBM.
On Thu, Jul 16, 2015 at 7:33 PM, Amit Gupta <agupta(a)pivotal.io> wrote:_______________________________________________
As some of you may already be aware, the Runtime team has recently been refactored:
- The "CAPI" team will be responsible for the Cloud Controller and Services API
- The Routing team will be responsible for work on routing, including the existing Gorouter component and new work on TCP routing
- The OSS Release Integration team (MEGA) will be primarily responsible for the integration of all components
There is a little more to that last one, so I'd like to share our mandate document and open it up to questions, comments, and clarifications. A rough draft had been previously shared with the community. We have since gathered feedback and held a team Inception to socialize our goals and refine our mandate:
I'd also like to introduce the members of the new OSS Release Integration team, so our names don't look unfamiliar when we respond to your issues, pull requests, and mailing list messages.
Joseph Palermo, Technical Lead, Pivotal
Dan Lavine, Software Engineer, IBM
Zak Auerbach, Software Engineer, IBM
Duncan Winn, Solutions Engineer, Pivotal
Amit Gupta, PM, Pivotal
cf-dev mailing list
Join firstname.lastname@example.org to automatically receive all group messages.