From general-return-10246-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Thu Aug 03 23:30:26 2006 Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 28297 invoked from network); 3 Aug 2006 23:30:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Aug 2006 23:30:25 -0000 Received: (qmail 84054 invoked by uid 500); 3 Aug 2006 23:30:23 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 83969 invoked by uid 500); 3 Aug 2006 23:30:23 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 83958 invoked by uid 99); 3 Aug 2006 23:30:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 16:30:23 -0700 X-ASF-Spam-Status: No, hits=0.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of cctrieloff@redhat.com designates 66.187.233.31 as permitted sender) Received: from [66.187.233.31] (HELO mx1.redhat.com) (66.187.233.31) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 16:30:22 -0700 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k73NU0wp006914 for ; Thu, 3 Aug 2006 19:30:00 -0400 Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k73NU0Jq024208 for ; Thu, 3 Aug 2006 19:30:00 -0400 Received: from [10.13.248.10] (vpn-248-10.boston.redhat.com [10.13.248.10]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id k73NTxw3032726 for ; Thu, 3 Aug 2006 19:29:59 -0400 Message-ID: <44D287D8.7000700@redhat.com> Date: Thu, 03 Aug 2006 19:33:44 -0400 From: Carl Trieloff Reply-To: cctrieloff@redhat.com Organization: Red Hat User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 To: general@incubator.apache.org Subject: Re: Accept Glasgow into Incubator - Spec Terms References: <44D26B5D.2090203@rowe-clan.net> In-Reply-To: <44D26B5D.2090203@rowe-clan.net> Content-Type: multipart/alternative; boundary="------------020505010509090906090302" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --------------020505010509090906090302 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit The ASF does not recognize corporate members; Incorrect - Apace has a CCLA, and requires your employer to sign it From icla " For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity." and from ccla " This version of the Agreement allows an entity (the "Corporation") to submit Contributions to the Foundation, to authorize Contributions submitted by its designated employees to the Foundation, and to grant copyright and patent licenses thereto." ... all of our contributions are measured on an individual basis and individual merit correct. This mail seems to imply that Apache does not require employer to sign the CCLA, however I have first had experience that the ASF does require this. It seems that the objection is that I chose to be up-front write this down, even though the practice is the same at Apache. Without the CCLA there would no patient and copyright grants if you are not self employed and just about every employer would have claims on Apache code. Thus from a IP perspective, you have to recognize the employer. Key point - contributions - individual ICLA. IP - need employer CCLA. Hope that clears it up, regards Carl. William A. Rowe, Jr. wrote: > I'm sorry, but respectfully -1 this proposal as written. My specific objection > is to the language below, I don't see anything otherwise objectionable in the > proposal. > > The ASF does not recognize corporate members; all of our contributions are > measured on an individual basis and individual merit. > > This proposal under the "Mechanisms for Feedback" and ultimate participation > by the appropriate parties sends us down entirely the wrong track and conveys > the wrong message for an ASF project. > > I have no objection to that standards committee growing more corporate members. > But to the extent that ASF contributors offer productive growth and formative > input into the specification, the way this section is phrased is not acceptable. > If the contributor wish, and if under these terms their contributions merits > participation, that contributor should either lead the ASF's direct involvement > as the ASF spec liason (much as we've done within the JCP) or as an individual > contributor. > > The specific statement "In the same spirit of Apache, if an individual has shown > understanding of the project and substantive contribution to the specification, > a vote based on technical merit and understanding of the goals of the work can > be initiated to have that parties Employer join the specification working > group." > > is an Oxymoron. > > This section of the proposal below is entirely corporate-oriented, and that > is not what the ASF does. If this can be addressed, my opinion of this effort > is otherwise without issues. One alternative is to modify this as I hint at > above. The other alternative is to determine the specific standards body first > and vote participation up or down based on the body selected. > > Bill > > > > Cliff Schmidt wrote: > >> I believe all open questions about the Glasgow proposal (originally >> submitted as "Blaze") have now been addressed enough to call a vote >> for accepting the project for incubation. >> > > "a.) In the same way anyone can issue a JIRA on any Apache project having signed > the Apache CLA, anyone can issue a “JIRA” to the specification working group > through the RLA (Reviewer License Agreement). This agreement provides a license > to that IP so that the specification team can incorporate it and the > specifaction as they like and the specifications can remain entirely open and > royalty free. b.) In the same spirit of Apache, if an individual has shown > understanding of the project and substantive contribution to the specification, > a vote based on technical merit and understanding of the goals of the work can > be initiated to have that parties Employer join the specification working group. > On such acceptance the employer is required to sign an agreement to make sure > that employer also grants the ongoing and consistent licenses to the work as > posted in specifications. > > The Reviewer License Agreement (RLA) can be viewed from the AMQP specification > page of any of the members as listed above." > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org > > --------------020505010509090906090302--