Steve, this was exactly the point I wanted to make and the reason I chose the verbiage of "reasonably accessible" since I believe that this would classify as such. However, as Thierry pointed out in his response to the review that wasn't his primary focus.
Rather, he didn't want a project to benefit a single contributor, vendor, organization and I've submitted a revision for his comments. But, your point is well taken, and I didn't realize that the RHEL free for developers was a recent change. -amrith > -----Original Message----- > From: Steve Gordon [mailto:[email protected]] > Sent: Thursday, June 16, 2016 11:40 PM > To: OpenStack Development Mailing List (not for usage questions) > <[email protected]> > Subject: Re: [openstack-dev] [all][tc] Require a level playing field for > OpenStack projects > > ----- Original Message ----- > > From: "Jeremy Stanley" <[email protected]> > > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > > Sent: Thursday, June 16, 2016 5:04:43 PM > > Subject: Re: [openstack-dev] [all][tc] Require a level playing field > for OpenStack projects > > > > On 2016-06-16 16:04:28 -0400 (-0400), Steve Gordon wrote: > > [...] > > > This is definitely a point worth clarifying in the general case, > > > but tangentially for the specific case of the RHEL operating > > > system please note that RHEL is available to developers for free: > > > > > > http://developers.redhat.com/products/rhel/get-started/ > > > http://developers.redhat.com/articles/no-cost-rhel-faq/ > > > > > > This is a *relatively* recent advancement so I though I would > > > mention it as folks may not be aware. > > > > Just to clarify, this is free-as-in-beer (gratis) and not > > free-as-in-speech (libre)? If so, that's still proprietary so I'm > > curious how that changes the situation. Would OpenStack welcome a > > project built exclusively around a "free for developer use" product > > into the tent? > > Well, in the context of evaluating this specific proposed change that > really depends on the final language used. Under the wording that is > currently proposed the answer would seem to be "yes" if developers of all > organizations have access to that same software - whether that's the > intent or not is perhaps a different question. In reality of course such a > hypothetical project would likely fall afoul of the earlier criteria > around dependencies anyway... > > -Steve > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
