Open Stack

I agree with Richard that we should clarity on the policy and rationale. However, OpenStack Foundation has a fundamentally different strategy to ASF so I don't think that their approach has much relevance. 

-----Original Message-----
From: Richard Fontana [mailto:rfontana at redhat.com] 
Sent: Thursday, March 20, 2014 6:23 AM
To: Mark McLoughlin
Cc: legal-discuss at lists.openstack.org
Subject: Re: [legal-discuss] [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Thu, Mar 20, 2014 at 08:22:12AM +0000, Mark McLoughlin wrote:
> I'm no fan (personally) of AGPLv3, but taking a stance that there must 
> be a way of deploying OpenStack in production without requiring any
> AGPLv3 code to be deployed is a significant policy decision for the 
> project and I don't think we've ever articulated the reasons clearly 
> for it.

Such a policy would be unprecedented for any Apache License 2.0 project as far as I am aware. For comparisons look at the legal policies of the Apache Software Foundation, which don't go this far.

I don't really care about the answer (as long as it doesn't create technical problems for OpenStack development and deployment -- unclear to me here) but I do care about the stated rationale. If the rationale is limited to something like 'the reality is that some users and Foundation members are sufficiently risk averse about AGPL that we feel we need to adopt this policy', so be it. 

- RF


_______________________________________________
legal-discuss mailing list
legal-discuss at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
Please consider the environment before printing this email.

The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you.