Date
1 - 7 of 7
Introducing OSS Release Integration Team
Amit Kumar Gupta
Hi all,
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:
https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#
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
Thanks,
Amit
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:
https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#
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
Thanks,
Amit
Amit Kumar Gupta
Ah, copy-paste fail! Zak is a Pivotal engineer, not IBM.
toggle quoted message
Show quoted text
On Thu, Jul 16, 2015 at 7:33 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
Hi all,
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:
https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#
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
Thanks,
Amit
Cornelia Davis <cdavis@...>
Thought so. :-)
Great news. Thanks for the detailed overview Amit!
Cornelia
Sent from my iPhone
toggle quoted message
Show quoted text
Great news. Thanks for the detailed overview Amit!
Cornelia
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:_______________________________________________
Hi all,
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:
https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#
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
Thanks,
Amit
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
Noburou TANIGUCHI
A useless question: Why is the team called MEGA?
There is no 'M' 'E' 'G' 'A' in the initial characters of 'The OSS Release
Integration team.'
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p764.html
Sent from the CF Dev mailing list archive at Nabble.com.
There is no 'M' 'E' 'G' 'A' in the initial characters of 'The OSS Release
Integration team.'
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p764.html
Sent from the CF Dev mailing list archive at Nabble.com.
Amit Kumar Gupta
It's just a historical oddity.
Well before it was clear that there was going to be a "MEGA" team with the
specific mandates set out above, we knew we had this big set of interrated
problems, cf-release being too monolithic, etc. Informally these set of
problems were referred to as "MEGA". The name stuck in people's heads and
conversations, as the actual name and responsibilities of the team
eventually got clarified.
It's similar to Diego in a way. Originally thought/discussed as a rewrite
of the DEA in Go, that description would now be considered misleading as
the project is so much more than that.
We're open to backronym suggestions for what MEGA could stand for though ;).
Amit
toggle quoted message
Show quoted text
Well before it was clear that there was going to be a "MEGA" team with the
specific mandates set out above, we knew we had this big set of interrated
problems, cf-release being too monolithic, etc. Informally these set of
problems were referred to as "MEGA". The name stuck in people's heads and
conversations, as the actual name and responsibilities of the team
eventually got clarified.
It's similar to Diego in a way. Originally thought/discussed as a rewrite
of the DEA in Go, that description would now be considered misleading as
the project is so much more than that.
We're open to backronym suggestions for what MEGA could stand for though ;).
Amit
On Fri, Jul 17, 2015 at 3:51 AM, Noburou TANIGUCHI <dev(a)nota.m001.jp> wrote:
A useless question: Why is the team called MEGA?
There is no 'M' 'E' 'G' 'A' in the initial characters of 'The OSS Release
Integration team.'
--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p764.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
Noburou TANIGUCHI
Thank you for the scrupulous answer, Amit.
(I apologize this late response)
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p805.html
Sent from the CF Dev mailing list archive at Nabble.com.
(I apologize this late response)
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p805.html
Sent from the CF Dev mailing list archive at Nabble.com.
Amit Kumar Gupta
No problem, more than happy to clarify!
Amit
toggle quoted message
Show quoted text
Amit
On Tue, Jul 21, 2015 at 4:03 PM, Noburou TANIGUCHI <dev(a)nota.m001.jp> wrote:
Thank you for the scrupulous answer, Amit.
(I apologize this late response)
--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-Introducing-OSS-Release-Integration-Team-tp757p805.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev