BOSH PMC refactoring – Call for Nominations
Marco Voelz
Dear friends of BOSH,
Within the BOSH project management committee (PMC) we want to ensure that our project structure reflects how our platform is currently built and managed. Consequently, we propose the following changes:
Archiving the BOSH CPIs project — This project has been inactive for a while. Most CPIs are currently maintained by the owners of the various IaaS they relate to. The rest of the work is performed by the BOSH Core project. We need to reassess our project structure with the stakeholders of the various CPIs. This will likely result in the creation of a few new projects.
Splitting the BOSH Core project in two — The BOSH core team is currently divided between San Francisco, USA and Toronto, Canada. Until recently, a single Product Manager was overseeing both halves of the team. This PM was also the BOSH Core project lead. We propose to replace the current BOSH Core project by the BOSH Core San Francisco and BOSH Core Toronto projects. Since these projects are a continuation of the existing BOSH Core project, there is no need for a formal project proposal or incubation period.
New BOSH Core Project Management — Dmitriy Kalinin is rotating into a role internal to Pivotal. As such, nominations are now open for that roll. Pivotal would like to nominate the following individuals to fill the positions of project leads: * Morgan Fine from Pivotal as project lead for the BOSH Core San Francisco project * Frédéric Desbiens from Pivotal as project lead for the BOSH Core Toronto project
If any Cloud Foundry Foundation member participating in a BOSH PMC project wishes to nominate someone else, please do so by contacting me directly. Nominations will close by August, 16th. After the nomination window, we will hold votes of the BOSH PMC to officialize the changes to our project structure and select the new project leads.
Warm regards Marco
For reference, the role of project lead is defined in the Development Operations Policy, available here: https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF_Development_Operations_Policy.pdf
Relevant extract from the policy: “If a Project Lead is removed, or decides to step down for any reason, any Foundation member can nominate a replacement to the out-going Project Lead. If consensus is not reached among the Project Members on the selection of a new Project Lead, the PMC Chair shall call for a Governance by Contribution vote within that PMC. Alternately, if the Project exists within a PMC that has delegated Project decisions to the individual Projects, the PMC Lead of such PMC, not the PMC Chair, shall call for a Governance by Contribution vote within that Project.” |
|
Chip Childers
I think it's also time to talk about graduating some (all) of the incubating CPI's to "active" status. WDYT? On Thu, Aug 9, 2018 at 6:10 AM Marco Voelz <marco.voelz@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815 |
|
Marco Voelz
That’s a change we have on the list for the next refactoring. We tried to keep the scope small for this one ;)
Warm regards
Marco
|
|