<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div><div><div><br></div><div><div id="MAC_OUTLOOK_SIGNATURE"></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Dean Troyer<br><span style="font-weight:bold">Reply-To: </span> "OpenStack Development Mailing List (not for usage questions)"<br><span style="font-weight:bold">Date: </span> Friday 5 February 2016 at 14:57<br><span style="font-weight:bold">To: </span> "OpenStack Development Mailing List (not for usage questions)"<br><span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [all] [tc] "No Open Core" in 2016<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Feb 5, 2016 at 4:57 AM, Thierry Carrez <span dir="ltr">
<<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My personal take on that is that we can draw a line in the sand for what is acceptable as an official project in the upstream OpenStack open source effort. It should have a fully-functional, production-grade open source implementation. If you need proprietary
software or a commercial entity to fully use the functionality of a project or getting serious about it, then it should not be accepted in OpenStack as an official project. It can still live as a non-official project and even be hosted under OpenStack infrastructure,
but it should not be part of "OpenStack". That is how I would interpret "no open core" in OpenStack 2016.<br></blockquote><div><br></div><div>Should we host projects that have no hope of becoming official projects due to this sort of criteria? Would we host GPL-only projects under openstack/?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Of course, the devil is in the details, especially around what I mean by "fully-functional" and "production-grade". Is it just an API/stability thing, or does performance/scalability come into account ? There will always be some subjectivity there, but I think
it's a good place to start.<br></blockquote><div><br></div><div>I think defining 'fully-functional' is easy enough until you allow 'vendor extensions' into the API. But there is still an amount of objective criteria to look at to make it something that a group of, say 13 judges, might arrive at a reasonable answer.</div><div><br></div><div>'Production-grade' is more subjective, especially with the size of deployment differences in 'production' for a bunch of other things. But again, it is one of those things that reasonably technical people will generally arrive at a useful conclusion .
Existing components (DB, message queues, etc) can point at known production deployments as evidence; new components have a harder sell.</div></div></div></div></div></div></blockquote></span><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div dir="ltr"><div class="gmail_extra"><div><br></div><div>For a time many projects used SQLite as a reference implementation for testing DB functionality, and have moved away from that (completely? I'm not sure) as we all agree it really is not a production-grade implementation. That is an easy example, but
as a community we have crossed this bridge multiple times already and will be able to do it again.</div></div></div></div></div></blockquote></span><div><br></div><div>This could also be covered by needing scaleable as well as fully-functional and production grade. Again, it would be subjective but it would avoid reference implementations that only work at devstack scale.</div><div><br></div><div>Tim</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div dir="ltr"><div class="gmail_extra"><div><br></div><div>dt</div><div><br></div>
-- <br><div class="gmail_signature"><br>
Dean Troyer<br><a href="mailto:dtroyer@gmail.com" target="_blank">dtroyer@gmail.com</a><br></div></div></div></div></div></blockquote></span></body></html>