Re: A proposal to offer mongodb 3.2.6 bosh release to cloudfoundry

Michael Maximilien

Yes, that's absolutely a path forward. You can use community as springboard and create proposal for incubation later as you see acceptance and need more visibility. Best,


ibm cloud labs
sillicon valley, ca

Sent from my iPhone

On Feb 28, 2017, at 12:59 AM, Lin, Lynn <Lynn.X.Lin(a)> wrote:

Thanks Dieu ! Can we put it into cloud foundry community firstly then later on we can revisit to see if we want to put into cloudfoundry-incubator ?

From: Dieu Cao [mailto:dcao(a)]
Sent: Tuesday, February 28, 2017 4:14 PM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)>
Cc: Huang, Peter <Peter.Y.Huang(a)>; Michael Maximilien <maxim(a)>; Coen, Shannon (Pivotal) <scoen(a)>
Subject: [cf-dev] Re: Re: Re: A proposal to offer mongodb 3.2.6 bosh release to cloudfoundry

Lynn, I think whether to put it in the Extensions PMC or in cloudfoundry-community simply depends on your goals.

There's some additional visibility given to projects in the Extensions PMC [1] as Max mentioned.
These projects can be viewed as official extensions to Cloud Foundry.

The cloudfoundry-community repo is also a great place to make useful extensions to CF available and is very easy to achieve.
Lots of great projects are hosted there.
However, these projects are not part of the Cloud Foundry Foundation intellectual IP.


On Mon, Feb 27, 2017 at 8:26 PM, Dr Nic Williams <drnicwilliams(a)> wrote:
Bonus tip:

Upload all blobs so they appear in the config/blobs.yml - for example the simple_server/mongodb3.tgz in simple_server package.

And remove large files from the git repo (they add up over time)

Join { to automatically receive all group messages.