www-community mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Kienenberger <mkien...@gmail.com>
Subject Re: Apache Extras Question
Date Thu, 29 Dec 2011 14:33:09 GMT
I am not an official Apache member, but here's my take on it.

The Extras project area is for projects related to Apache, but not in
any way managed by the Apache Software Foundation.  Because of that,
it may not use the Apache brand-name, trademarks, nor the "org.apache"

Consider Apache Extras to be more of an unofficial fan site of Apache.

If someone (in this case, you) wants to create something that directly
interacts or is related to Apache OODT, this non-related site gives
you a place to put it where other Apache OODT users are more likely to
find it.   But how the project is managed is up to you, and the
ownership of the project and its assets remains with you.

On Wed, Dec 28, 2011 at 8:49 PM, Mattmann, Chris A (388J)
<chris.a.mattmann@jpl.nasa.gov> wrote:
> Hey Guys,
> I was reading [1] and I noticed item 3.1 and 3.2 stating that projects at Extras shouldn't
> use the org.apache namespace (e.g., if Java), and they shouldn't use the apache project
> name in their extras name. I find this kind of odd.
> Here's my concrete situation. Over in Apache OODT ville, I've got 2 plugins for our PushPull
> system that pulls down remote file content from sites and downloads them. The 2 plugins
> are Java plugins that integrate libraries that are LGPL licensed. I can't include these
> in Apache OODT as part of PushPull even though we use the plugins extensively on
> projects where we deploy OODT and they are better FTP plugins than existing friendly
(to ALv2)
> licensed projects. So, given the choice of simply keeping the code housed in our internal
> JPL SVN and being unable to more broadly share it, I decided to throw up a project on
> Extras called oodt-pushpull-plugins, and throw the code up there. I however did this
> reading [1] and am now worried I'm in violation of 3.1 and 3.2 because I used org.apache.oodt.cas.pushpull
> as the namespace for my java package and I used oodt all over my code (which I licensed
> under ALv2 FWIW, here [2]). FWIW also, the only folks I would expect to work on
> [2] would be OODT PMC members, myself so far, and Brian Foster who are folks
> who work on PushPull.
> So I'm wondering what's up with 3.1 and 3.2. Isn't the use of similar project names precisely
> what we want at Extras? And what's the harm in allowing projects to use org.apache.oodt
> in their namespace over there? That won't confuse people IMHO, because I'm not to
> publish to Maven Central (and wouldn't want to -- I'd want folks to download this library
> independently and mvn install it locally, and instructed folks to do so on [3]) and because
> we will make it clear with documentation on our Wiki (that I was just about to write
> will hold off on until I hear the result of this thread) that the code at oodt-pushpull-plugins
> on Apache Extras is *not* Apache OODT.
> Comments back would be appreciated. Ross told me that ComDev is charged with
> Apache Extras so that's why I'm asking here.
> Cheers,
> Chris
> [1] http://community.apache.org/apache-extras/guidelines.html
> [2] http://code.google.com/a/apache-extras.org/p/oodt-pushpull-plugins/
> [3] http://s.apache.org/8FB
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: community-unsubscribe@apache.org
> For additional commands, e-mail: community-help@apache.org

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

View raw message