On 12/19/2013 12:10 AM, Mike Perez wrote: > On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez <thin...@gmail.com > <mailto:thin...@gmail.com>> wrote: <snip> > I reviewed the TC meeting notes, and my question still stands. > > It seems the committee is touching on the point of there being a worry > because if > it's a single company running the show, they can pull resources away and > the > project collapses. My worry is just having one company attempting to > design solutions > to use cases that work for them, will later not work for those potential > companies that would > provide contributors. > > -Mike Perez
Which is our fundamental chicken and egg problem. The Barbican team has
said they've reached out to other parties, who have expressed interest
in joining, but no one else has.
The Heat experience shows that a lot of the time companies won't kick in
resources until there is some kind of stamp of general approval.
If you showed up early, with a commitment to work openly, the fact that
the project maps to your own use cases really well isn't a bug, it's a
feature. I don't want to hold up a team from incubating because other
people stayed on the sidelines. That was actually exactly what was going
on with Heat, where lots of entities thought they would keep that side
of the equation proprietary, or outside of OpenStack. By bringing Heat
in, we changed the equation, I think massively for the better.
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
