Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 209.85.216.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=ZiVzdJJs9zLBeawM31nmgdB35eUUvIbiRZU5uOEy8EnwPcGccvP8z2gkEfmCq6BX9I
         gPW56b7BjHtYJ9R5qZg5nIFAPBi9q+ZDb73H7RnCc5ZL1hScxmfSJGyvGqNuoD+fR15a
         9W0+6uQGGWj4zFXE2LGVaymdFUBuUl1eZ1z8c=
MIME-Version: 1.0
In-Reply-To: <4D4C6191.70104@shanecurcuru.org>
References: <4D4C6191.70104@shanecurcuru.org>
Date: Fri, 4 Feb 2011 15:47:14 -0500
Message-ID: <AANLkTi==acNr93NZrj3AdgUHgzdHfuBhseYzC-zbwWge@mail.gmail.com>
Subject: Re: Policy suggestions for associated marks?
From: Greg Stein <gstein@gmail.com>
To: legal-discuss@apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The Subversion community has said "use 'svn' as you like. we don't care."

Not sure that we need anything more formal than that.

On Fri, Feb 4, 2011 at 15:29, Shane Curcuru <asf@shanecurcuru.org> wrote:
> How can we allow friendly third parties maximum freedom to use names that
> are related or associated to our key Apache marks, while still keeping a
> reasonable expectation of protection for Apache marks?
>
> This is a case best described by example - although please note, I'm more
> looking for general advice or policy suggestions rather than specific
> comments on existing cases.
>
> Example: The Apache Maven project ships the Maven software product that d=
oes
> cool build things, and the "Maven" mark is important to us. However the
> project has also encouraged (via documentation for developers) third part=
ies
> to use the "MVN" name in their software that is related to Maven.
>
> I.e. we encourage third parties to hypothetically build something like MV=
N
> Accelerator, which might let you use Maven and MVN Accelerator together f=
or
> lighting fast builds. =A0In one way, this may be an advantage to the Apac=
he
> Maven project itself, because it encourages third parties to build softwa=
re
> associated with our software products.
>
> A separate example is the Powered By metaphor [1]. =A0The httpd project h=
as
> long had a graphic that displayed "Powered by Apache" which we explicitly
> allow third parties to display on servers that use httpd software.
>
> ----
> - What are the best ways to create these "associated" or "related" brands=
,
> especially to encourage third parties to respectfully name their related
> software products in an appropriate way?
>
> - What issues do we need to watch out for to ensure that third party use =
of
> these associated brands (like MVN) does *not* significantly weaken our
> trademark claim to our primary brands for our software products (like Mav=
en
> or "Apache")?
>
>
> I believe if we can have some positive and easy to use guidelines in this
> are for Apache projects, that both a number of our projects, as well as a
> number of third parties, would start taking advantage of it pretty quickl=
y.
>
> - Shane
>
> [1] discussed in more detail:
> http://www.apache.org/foundation/marks/faq/#poweredby
> http://httpd.apache.org/docs/1.3/misc/FAQ.html#logo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org