Return-Path: X-Original-To: apmail-legal-discuss-archive@www.apache.org Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E37F9132 for ; Thu, 2 Aug 2012 14:00:20 +0000 (UTC) Received: (qmail 67297 invoked by uid 500); 2 Aug 2012 14:00:19 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 67136 invoked by uid 500); 2 Aug 2012 14:00:19 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 67128 invoked by uid 99); 2 Aug 2012 14:00:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 14:00:19 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.208.4.194] (HELO mout.perfora.net) (74.208.4.194) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 14:00:11 +0000 Received: from [192.168.1.107] (pool-173-76-33-115.bstnma.fios.verizon.net [173.76.33.115]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0Md3NK-1TE35L1lli-00Hrcg; Thu, 02 Aug 2012 09:59:50 -0400 Message-ID: <501A87D3.7020409@shanecurcuru.org> Date: Thu, 02 Aug 2012 09:59:47 -0400 From: Shane Curcuru User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: legal-discuss@apache.org Subject: Re: Upcoming CloudStack release References: <6005BE083BF501439A84DC3523BAC82DE44D7E3B72@LONPMAILBOX01.citrite.net> <5D8DB0DD-CC0C-4DF2-9898-453F34E87808@apache.org> <6005BE083BF501439A84DC3523BAC82DE44D7E3D0B@LONPMAILBOX01.citrite.net> <000288FC-EBF6-45B3-826B-7CBCB3C0C9D7@apache.org> In-Reply-To: <000288FC-EBF6-45B3-826B-7CBCB3C0C9D7@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:4kxEvXOPE3YQZ/20j+HaRele0X08lwyeJkD2VSfBJS2 3f7Pq/WAjHUe3R9CR1YCwx4EnZFYzzDmZ0PyITYnZkoevjl+X8 J6yGFdHKjWFihqTZr8OOabyVg2s4OuSw2jprcRlCSqb5aYrN11 EZZ5YB7OvJdJ41bRBzsG0DrIzKe3fxExkaX+fa1DqCPP3XCFsl KQ8/wzZcSRtQyU0AGbvci+YuT7YZ9QNXdpIw4VpVqnyHTnt5GG 2CcLOfmeCjGsvExj38bw1vkon0VAQVyEFVJET2Wwbs8VEmGGGF e7O2hEvIqH4D7wjH/o4DfSEIYsk1M3bV/2U0EGh1z/rGeMghR1 4pHa684XzF7x2A9Ct1j4DcnCNpvFUq9brbsw8k+Zj X-Virus-Checked: Checked by ClamAV on apache.org Ewan & CloudStack folk: a quick reminder of how the Legal Affairs Committee works might be helpful. The legal-discuss@ list is a public place where anyone (although primarily Apache committers) can discuss legal issues relating to Apache projects. This is a good place to bring a question to either 1) get the obvious answer that's already documented, or 2) refine the question to be very specific in the legal sense. It is not a place to get any new policy decisions or answers to new questions made. So it's not likely that you'll get a specific "OK" on this list for a new question. The LEGAL JIRA queue is for *specific* legal questions. Primarily, it's for Apache projects who have a specific and documented need to do something, and need a legal approval or ruling if the specific thing you need to do is allowable by ASF policy or not. Note that hypothetical questions will typically not get an answer in JIRA. It's too difficult to answer hypothetical legal questions, and it's not necessarily a good use of volunteer member or pro bono counsel time to answer that kind of question. Does that make sense? This is the legal realm, which is a bit different than most other lists at the ASF. 8-) Also, Brett seems to have some really good advice here. On 8/2/2012 8:47 AM, Brett Porter wrote: > > On 02/08/2012, at 10:27 PM, Benson Margulies > wrote: > >> In my personal opinion, a request for an exception to the LGPL >> policy from a podling should be put up for discussion at >> general@incubator before being sent to legal. However, that's just >> my opinion, and anyone who wants to throw a tomato at me for >> manufacturing a spurious procedure is welcome to do so. > > *lob* :) > > IMO, the incubator is for pointing podlings at the right resources, > not becoming a layer of indirection. But I'm not sure we need to get > into the role of the Incubator here ;) +1 Brett. The best possible scenario would have been for mentors/Incubator peeps to ensure the question was laid out with the specific details before coming here. Then refine the very specific question on legal-discuss@, and then create a LEGAL JIRA to decide. >> >> More broadly, I wonder if it really should be legal, as opposed to >> the board or some other delegate, who decides if adequate >> justification is offered for such an exception. > > As a policy question, I think the board has already delegated that > authority to this committee: "the Legal Affairs Committee be and > hereby is responsible for establishing and managing legal policies > based on the advice of legal counsel and the interests of the > Foundation". +1 Brett. The board has been consistent for several years now that specific policy areas have been delegated to various officers. Running to the board before the relevant VP has provided a specific answer to a specific question is typically not productive. After an officer renders a decision, if the relevant PMC still really believes it's wrong, would you make an appeal (so to speak) to the board. - Shane --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org