Dims, Given the strong language around partnership between Intel, Mirantis, and Google in that press release, and the activity in the review queue (2 pages of outstanding reviews) it seems clear to me that the intent is for this part of Fuel to participate in the big tent. The right thing to do here is for fuel-ccp to submit their repos to TC oversight by adding them to the official project list.
Fuel requires a mission change, or it may be perceived that Fuel itself does not adhere to the Four Opens [1] specifically Open Development and Open Community. Regards -steve [1] https://github.com/openstack/governance/blob/master/reference/opens.rst On 7/26/16, 11:15 AM, "Davanum Srinivas" <dava...@gmail.com> wrote: >And. it's here in OpenStack: > >Look for fuel-ccp-* in http://git.openstack.org/cgit/ or the gerrit search >https://review.openstack.org/#/q/status:open+branch:master+project:^openst >ack/fuel-ccp.* > >-- Dims > >On Tue, Jul 26, 2016 at 1:53 PM, Fox, Kevin M <kevin....@pnnl.gov> wrote: >> They are starting their own project. >> ________________________________________ >> From: Stephen Hindle [shin...@llnw.com] >> Sent: Tuesday, July 26, 2016 10:35 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: [openstack-dev] [Kolla] [Fuel] Looks like Mirantis is getting >>Fuel CCP (docker/k8s) kicked off >> >> So just saw this: >> >>http://www.computerweekly.com/blog/Open-Source-Insider/OpenStack-on-Kuber >>netes-Mirantis-fuels-Fuel-with-Google-Intel-heat >> >> Wonder if that means we'll get more devs or maybe some prebuilt >> containers for Kolla? >> >> >> -- >> Stephen Hindle - Senior Systems Engineer >> 480.807.8189 480.807.8189 >> www.limelight.com Delivering Faster Better >> >> Join the conversation >> >> at Limelight Connect >> >> -- >> The information in this message may be confidential. It is intended >>solely >> for >> the addressee(s). If you are not the intended recipient, any >>disclosure, >> copying or distribution of the message, or any action or omission taken >>by >> you >> in reliance on it, is prohibited and may be unlawful. Please >>immediately >> contact the sender if you have received this message in error. >> >> >> >>_________________________________________________________________________ >>_ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >>_________________________________________________________________________ >>_ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > >-- >Davanum Srinivas :: https://twitter.com/dims > >__________________________________________________________________________ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev