Re: Introducing OSS Release Integration Team


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

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

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.