Re: Proposal for Incubation in the Extensions PMC: CF Dev
Is it too late to change the name? I suspect that folks might not instantly understand that cf-dev and CF Dev are two entirely different things.From: <cf-dev@...> on behalf of Stephen Levine <slevine@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, February 23, 2018 at 12:20 PM
To: "cf-dev@..." <cf-dev@...>
Cc: "Sisil, Scott (Pivotal)" <ssisil@...>, "Casey, Emily (Pivotal)" <ecasey@...>, Chip Childers <cchilders@...>, Michael Maximilien <maxim@...>
Subject: [cf-dev] Proposal for Incubation in the Extensions PMC: CF Dev
Pivotal is proposing CF Dev for inclusion in the Extensions PMC as a new incubating project.
CF Dev is a deployment of BOSH and cf-deployment that runs locally in Garden containers. It uses native hypervisors to start quickly with zero external dependencies. It also provides a fully functional BOSH director.
CF Dev is currently available on Github .
I would also like to introduce everyone to Scott Sisil, who is joining me as Co-PM on Pivotal's local and community developer initiatives. Please reach out to Scott and/or myself for questions about CF Dev.
Project Name: CF Dev
Project Proposal: See , and attached.
Proposed Project Leads: Stephen Levine, Pivotal & Scott Sisil Pivotal
Proposed Contributors: Emily Casey, Pivotal; Dave Protasowski, Pivotal; Stephen Hiehn, Pivotal
Proposed Scope: See , and attached.
Development Operating Model: Pairing (local + remote)
Technical Approach: CF CLI plugin that starts a VM using the OS native hypervisor.
Please let us know if you have any questions or feedback.