Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45028107EC for ; Tue, 9 Jul 2013 18:00:52 +0000 (UTC) Received: (qmail 38967 invoked by uid 500); 9 Jul 2013 18:00:46 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 38655 invoked by uid 500); 9 Jul 2013 18:00:46 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 38647 invoked by uid 99); 9 Jul 2013 18:00:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 18:00:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.145.54.173 is neither permitted nor denied by domain of evans@yahoo-inc.com) Received: from [216.145.54.173] (HELO mrout3.yahoo.com) (216.145.54.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 18:00:41 +0000 Received: from GQ1-EX10-CAHT06.y.corp.yahoo.com (gq1-ex10-caht06.corp.gq1.yahoo.com [10.73.118.85]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id r69HwUH9080778 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 9 Jul 2013 10:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1373392711; bh=/XSVxwQSIUSCIORnmbw75JyKHXqvP9Q/Und51rSvceE=; h=From:To:Subject:Date:Message-ID:In-Reply-To:Content-Type: MIME-Version; b=w0eseGW8KA8vfsISCqr8bjR7P5fHkz6fjBH9iljVDY2sAXeYNjAIWC4wSALPkIHmY GcgXjJ+VVJiWVzdEwcChQWUywkJAl5pAKdMa4VqQ3DZEkRe5hPSh5XpwdZF9dd9eIX JlaegQi2pupX/MdsGSHJ1ZazsCb3nEQltaVLmcLs= Received: from GQ1-MB01-02.y.corp.yahoo.com ([fe80::a049:b5af:9055:ada6]) by GQ1-EX10-CAHT06.y.corp.yahoo.com ([fe80::d160:3f30:42ad:8619%12]) with mapi id 14.03.0123.003; Tue, 9 Jul 2013 10:58:29 -0700 From: Robert Evans To: "user@hadoop.apache.org" Subject: Re: Apache Hadoop licensing question Thread-Topic: Apache Hadoop licensing question Thread-Index: AQHOfMt5clkSfKY9a0OhJVfgKN8zFJlcw8QA Date: Tue, 9 Jul 2013 17:58:29 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.5.130515 x-originating-ip: [10.74.91.218] Content-Type: multipart/alternative; boundary="_000_CE01B65E157A1evansyahooinccom_" MIME-Version: 1.0 X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 392711001 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CE01B65E157A1evansyahooinccom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am not a lawyer so please do not take my comments in any way as legally b= inding. When releasing the code the general guideline I have received is to= make sure that there is a header in all of your files indicating the licen= se being used and where to get the full text of the license. We generally = use the following header (for the apache foundation) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. See accompanying LICENSE file. Connected to this you probably want to include the full text of the license= in a LICENSE file like indicated in the header. Some files are binary fil= es and cannot have this header in there, you don't need to try to do crazy = thing to include it in those files. You may also want to put in a copyright statement in each file. This remov= es any ambiguity about who actually owns the copyright of the code. In Apa= che we don't do this, but we have git, svn, and JIRA to be able to trace ba= ck exactly which contributions came from whom. This is more important if y= ou think you may want to try and have your project be part of Apache in the= future. As for usage of the logo, if you use it in a way that is referring to a rel= ease of the Apache Distribution of Hadoop, and not claiming that your code = is part of Hadoop or is Hadoop in any way then there should be no issue. I= f you want to be totally on the up and up you can try to send a mail to pri= vate@apache.org and ask the PMC to give your permission to use it, but that= may take a while, just because everyone is busy and we will probably want = to see how the logo is being used in context. --Bobby From: Michel Rouly > Reply-To: "user@hadoop.apache.org" > Date: Tuesday, July 9, 2013 10:43 AM To: "user@hadoop.apache.org" > Subject: Apache Hadoop licensing question My name is Michel Rouly. I'm working in association with the Florida Instit= ute of Technology and the AMALTHEA REU on an undergraduate research project built on top of Apache = Hadoop and Mahout. I have a quick question about the licensing requirements for this project. = All of our code is being developed under the Apache license. Do we need to = take any actions outside of citing the Apache license when releasing our co= de? One further question - what permission do we need to obtain in order to use= the Apache Hadoop logo (o= r a higher quality version) on research presentation materials, specificall= y a poster? Thanks in advance. -- Best, Michel Rouly Computer Science BS, 2015 George Mason University Fairfax, VA --_000_CE01B65E157A1evansyahooinccom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
I am not a lawyer so please do not take my comments in any way as lega= lly binding. When releasing the code the general guideline I have received = is to make sure that there is a header in all of your files indicating the = license being used and where to get the full text of the license.  We generally use the following hea= der (for the apache foundation)

  Licensed under the Apache License, Version 2.0 (the "Licen= se");
  you may not use this file except in compliance with the License= .
  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, soft= ware
  distributed under the License is distributed on an "AS IS&= quot; BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or= implied.
  See the License for the specific language governing permissions= and
  limitations under the License. See accompanying LICENSE file.

Connected to this you probably want to include the full text of the li= cense in a LICENSE file like indicated in the header.  Some files are = binary files and cannot have this header in there, you don't need to try to= do crazy thing to include it in those files.

You may also want to put in a copyright statement in each file.  = This removes any ambiguity about who actually owns the copyright of the cod= e.  In Apache we don't do this, but we have git, svn, and JIRA to be a= ble to trace back exactly which contributions came from whom.  This is more important if you think you may want to = try and have your project be part of Apache in the future.

As for usage of the logo, if you use it in a way that is referring to = a release of the Apache Distribution of Hadoop, and not claiming that your = code is part of Hadoop or is Hadoop in any way then there should be no issu= e.  If you want to be totally on the up and up you can try to send a mail to private@apache.org and ask the= PMC to give your permission to use it, but that may take a while, just bec= ause everyone is busy and we will probably want to see how the logo is bein= g used in context. 

--Bobby


From: Michel Rouly <michel.rouly@gmail.com>
Reply-To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Date: Tuesday, July 9, 2013 10:43 A= M
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Subject: Apache Hadoop licensing qu= estion

My name is Michel Rouly. I'm working in association with the Florida Institute of Technolo= gy and the AMALTHEA REU on an undergraduate research project built on top of Apache Hadoop and Mahout.

I have a quick question about the licensing requirements for this proj= ect. All of our code is being developed under the Apache license. Do we nee= d to take any actions outside of citing the Apache license when releasing o= ur code?

One further ques= tion - what permission do we need to obtain in order to use the Apache Hado= op logo (or a higher quality version) on research presentation materials, specifi= cally a poster?

Thanks in advanc= e.


--
Best,
Michel Rouly

Computer Science= BS, 2015
George Mason Uni= versity
Fairfax, VA = ;
--_000_CE01B65E157A1evansyahooinccom_--