Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D68A6EB1 for ; Sun, 26 Jun 2011 19:11:49 +0000 (UTC) Received: (qmail 45860 invoked by uid 500); 26 Jun 2011 19:11:47 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 45758 invoked by uid 500); 26 Jun 2011 19:11:46 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 45750 invoked by uid 99); 26 Jun 2011 19:11:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Jun 2011 19:11:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.97.132.81] (HELO homiemail-a63.g.dreamhost.com) (208.97.132.81) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Jun 2011 19:11:40 +0000 Received: from homiemail-a63.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTP id 242AE2F4059 for ; Sun, 26 Jun 2011 12:11:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; q=dns; s= gbiv.com; b=Q78zWU9H6sFEPh+zey3Ksriaz24GuCJSc4GN9XYXOYWYHrnxX+3n 2LNyYIjNCqhSSV491ih68t1ruflt33dfSK6lf9ssdE73Y3y/01aciJr4lPhMBJip o9yuc82PXJbNiZJONNA3jOusHcV7ewObVJQjJffGIMFtWsUXK7pI7GA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=TeclYzF9l/P4a1mW7N8phQXYZeQ=; b=qNrvjQUPIz12mkSr3QGE29RaxoxY b+Q93PYuhrOBrBIIoXzKH2cUxNdiVia7Nfp8Kvwl3HSr2SPq+0Oq4LTyVeQuw9/j XGdPguMJfL9vW/4DMjRdTZ0e4eChnJAtZTuoETrKyLfNFSUgdeEtDTZhuCAhsc4H gg2+3Pv1rSQV9Ek= Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTPSA id E988B2F4057 for ; Sun, 26 Jun 2011 12:11:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [VOTE] Shall we adopt the "Defining Hadoop" page From: "Roy T. Fielding" In-Reply-To: <4E056D3B.9030008@apache.org> Date: Sun, 26 Jun 2011 12:11:19 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <16935C45-FE78-418E-9999-EDD1ECC3257D@gbiv.com> References: <4E04948B.4050802@apache.org> <4E056D3B.9030008@apache.org> To: general@hadoop.apache.org X-Mailer: Apple Mail (2.1084) On Jun 24, 2011, at 10:08 PM, Doug Cutting wrote: > On 06/24/2011 07:07 PM, Owen O'Malley wrote: >> On Jun 24, 2011, at 6:43 AM, Doug Cutting wrote: >>=20 >>> Might it be better to improve the existing Apache trademark policy >>> page? >>=20 >> When the project is having trouble agreeing, reaching agreement at >> the foundation level seems unrealistic. >=20 > ASF trademark policy is set by Shane, VP Trademark, not by a = committee. If we apply trademark policy to this discussion, then the only answer = possible is that only releases made by the Apache Hadoop PMC can be called = Hadoop. That is, after all, the essence of board delegation to PMCs and the = meaning of trademarks. Traditionally, we have also allowed distributions that apply released security patches, for example as found in=20 http://www.apache.org/dist/httpd/patches/ and turned a blind eye toward changes that are purely to port to a new = platform. I did not write those exceptions down because I don't know what (if any) = impact they might have on enforcement. I said before that we typically don't argue about distributions that = include revisions that are on a release branch, but that assumed the project is actually working toward a release of that branch. I have a hard time = believing that Hadoop's trunk is a release branch. In any case, this very = specific exception should be entirely decided by the project -- the VP of = Trademarks has no role in deciding what is the purview of each PMC, namely the = decision on what is or is not released in the name of that project. ....Roy