Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F11FFC8.4030204@shanecurcuru.org>
Date: Sat, 14 Jan 2012 17:20:56 -0500
From: Shane Curcuru <asf@shanecurcuru.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: trademarks@apache.org
CC: "Mattmann, Chris A (388J)" <chris.a.mattmann@jpl.nasa.gov>,
 "dev@community.apache.org" <dev@community.apache.org>
Subject: Re: Apache Extras Question
References: <DD9692BD-1E27-45A8-8E80-6E42B6DA779E@jpl.nasa.gov>
 <CAM1yOjZHayPvdS=624xdKej3YMBXphTJCAFsVFNjUWNye0quZQ@mail.gmail.com>
 <15F56445-F5E3-4EBB-BAE4-71A7B973F294@jpl.nasa.gov>
 <CAM1yOjZqYUVv-KoivU4zdnVbozrt02MUCeLr=D3d9ebX1g-_oA@mail.gmail.com>
 <8D8C4302-AD75-4AD6-990A-DAAB6098C9E2@jpl.nasa.gov>
 <002501ccc666$5a3c8020$0eb58060$@acm.org>
 <DFC3FB12-98F6-46DC-8B86-1205BD1301B7@jpl.nasa.gov>
 <003501ccc66c$caa94400$5ffbcc00$@acm.org>
 <10F7EB13-FA75-4F5B-B7BC-F0445EAE99EB@jpl.nasa.gov>
 <002f01ccc696$32fff110$98ffd330$@acm.org>
 <31EB91E3-CE8D-4E74-9F52-0DCC6BF0624D@jpl.nasa.gov>
 <CAKDPwQYcNTrtA63+xjyKtbkGWO7V3eZuvUZu94cRx75CSubTeg@mail.gmail.com>
 <290EA0D0-4E7D-42A8-85F3-D40E80AC2FDD@jpl.nasa.gov>
 <E42587A2-C92D-4266-9E97-B049410A5F74@jpl.nasa.gov>
 <CAKDPwQbecNR4y8zzJ35qWiDAh5=4mJ=1HXd-QFTDn=SB2kLQCQ@mail.gmail.com>
 <6252FD29-A919-4F0E-A3B6-9B1A2CFCB74B@jpl.nasa.gov>
In-Reply-To: <6252FD29-A919-4F0E-A3B6-9B1A2CFCB74B@jpl.nasa.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Neat, I took a mental vacation on this issue, and it's mostly done when 
I come back to the thread!

Trademarks and brand are primarily about the primary name of a product, 
not classnames or package names.  So unless your project is called 
org.apache.SuperThing on the home page, the package name is of much less 
importance in the trandmark world than what you do say on your 
homepage/download page - presumably "Get Apache SuperThing!".

Apache Extras projects must not use the name "Apache" in their branding; 
i.e. to describe their projects or products.  Similarly, they must not 
use the same name as an Apache project or product, without having a very 
clear separation, a'la the Powered By guidelines.

Apache Extras projects probably should be able to use the 
org.apacheextras.* package name; I think along with the rest of the 
Apache Extras site guidelines, that keeps a sufficient "distance" with 
their projects.

Apache Extras projects must not create their own org.apache.* package 
names for their own projects.  While this is not the same level of 
importance as the overall Extras SuperStuff primary brand name, it is 
still inappropriate for Apache Extras projects to create new 
org.apache.SuperStuff packages.

Apache Extras probably can have some *existing* org.apache.SuperThing 
packages in their source tree, *if* they come from the actual Apache 
SuperThing project itself.

The point here is that Extras projects should not create new 
org.apache.* packages: that would imply their new SuperStuff is an 
official Apache bit of code (which it isn't).  But if they happen to 
want to fork some of our org.apache.SuperThing code, and incorporate it 
into their SuperStuff product, that's generally OK.

Does that all make sense?

- Shane

Sorry for the delay, but I was really burnt out on policy issue thinking 
over the holidays.

On 2012-01-02 10:14 PM, Mattmann, Chris A (388J) wrote:
> Hey N�ir�n et al.,
>
> Happy New Year! I've went ahead and updated my patch
> on COMDEV-65 [1] with information on the org.apacheextras
> namespace and with the suggestion to get further information
> from the responsible Project Management Committees and
> from ComDev PMC in general. I also changed Project Committees
> to Project Management Committees per N�ir�n's advice.
>
> I also went ahead and (a) started a VOTE thread with the OODT
> PMC on the naming of oodt-pushpull-plugins at Apache Extras [2];
> and (b) updated the package names on [2] to match org.apacheextras.
>
> With that, I'm considering this matter closed.
>
> Thanks for the advice everyone and best wishes in the New Year.
>
> Cheers,
> Chris
>
> [1] https://issues.apache.org/jira/browse/COMDEV-65
> [2] http://code.google.com/a/apache-extras.org/p/oodt-pushpull-plugins/
>
> On Dec 30, 2011, at 12:21 AM, N�ir�n Plunkett wrote:
>
>> Chris,
>>
>> On Thu, Dec 29, 2011 at 10:30 PM, Mattmann, Chris A (388J)
>> <chris.a.mattmann@jpl.nasa.gov>  wrote:
>>> Hey Guys,
>>>
>>> I was talking with Greg, and I think I'm OK with org.apacheextras as
>>> the namespace.
>>
>> Thanks for your patience :-) I wasn't trying to discount your
>> proposals, and I appreciate that you'd created a patch--I was just
>> trying to understand the reasons you disliked the org.apacheextras.*
>> proposal.
>>
>> If your conversation with Greg is easy to summarize, it might be worth
>> documenting why this proposal ended up being ok for you--but if you
>> just want to get back to writing code, that's fine too :-)
>>
>>> It sounds like Noirin thought that was cool and so did Mark S.
>>> Are folks here on ComDev cool with that namespace for our Extras
>>> projects? If so, I'll update my COMDEV-65 patch with docs stating that
>>> and document it and move forward.
>>
>> Tiny nit on the patch: we have project management committees, not
>> project committees :-) (Hey, at least I read it, right? :-))
>>
>>> I'm also of the mindset that the PMC should be the ones saying
>>> if they are OK with my oodt-pushpull-plugins Extras name and
>>> to me it should be fine if the PMC is OK with that. I can update
>>> the FAQ/guidelines to state that.
>>
>> My very vague recollection from when Apache Extras was booting up was
>> that we didn't want "official PMC-sanctioned projects" to have special
>> status there. I'd give this one a day or two to collect more input
>> before updating anything.
>>
>> Noirin
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>