Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: pass (athena.apache.org: domain of dennis.hamilton@acm.org
 designates 75.98.160.131 as permitted sender)
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <dev@community.apache.org>
References: <DD9692BD-1E27-45A8-8E80-6E42B6DA779E@jpl.nasa.gov>
 <CAM1yOjZHayPvdS=624xdKej3YMBXphTJCAFsVFNjUWNye0quZQ@mail.gmail.com>
 <15F56445-F5E3-4EBB-BAE4-71A7B973F294@jpl.nasa.gov>
 <CAKQbXgBj-txS6mpVMHvT7oF2PsS8gXNdDYDDmK_1odbdmJfpEw@mail.gmail.com>
 <983E76DE-3218-482D-B978-C1BD72A212B1@jpl.nasa.gov>
 <CAGU5spfo5zqk7wWwBcKy5pOisM39vHY4OhaqG1KnF6ARYCOb-A@mail.gmail.com>
 <1325190214.13347.YahooMailNeo@web27804.mail.ukl.yahoo.com>
In-Reply-To: <1325190214.13347.YahooMailNeo@web27804.mail.ukl.yahoo.com>
Subject: RE: Apache Extras Question
Date: Thu, 29 Dec 2011 12:42:28 -0800
Organization: NuovoDoc
Message-ID: <003301ccc66a$620a58a0$261f09e0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: 
 AQKUuYugsCYfHbpl9AppkUsutSA9wgI4W71mAe8IfCwCCkpFZwGKlKoaAnit6EkCbr1j+JP+QknQ
Content-Language: en-us

It is an interesting idea that the apache-extras.org domain be usable =
this way.  There is no mapping to projects directly (it being a mapping =
into code.google.com instead).

Nevertheless, if the project label is "mylabel" then =
org.apache_extras.mylabel.* would work as a technical solution.  (The =
mapping of "-" to "_" is part of the Java specification.)

 - Dennis

-----Original Message-----
From: Mark Struberg [mailto:struberg@yahoo.de]=20
Sent: Thursday, December 29, 2011 12:24
To: dev@community.apache.org
Subject: Re: Apache Extras Question

> If you are saying this is compatible with ALv2 ? Then why use Apache
> Extras instead of just the oodt SVN official repo in Apache ?

But that's exactly the point! It is NOT ALv2 because it seems that =
Chris' project compiles against GPL sources and thus also must be GPL =
licensed.

Would it be possible to have it under the package org.apacheextras ?
If we don't even allow that, then we can just close down =
apacheextras.org - because then there is no use for it imo.

Of course this all implies that apacheextras will make a prominent =
mentioning that apacheextras !=3D ASF and apacheextras might not only =
contain ALv2 licensed sources but also others.


LieGrue,
strub


----- Original Message -----
> From: Luciano Resende <luckbr1975@gmail.com>
> To: dev@community.apache.org
> Cc:=20
> Sent: Thursday, December 29, 2011 9:13 PM
> Subject: Re: Apache Extras Question
>=20
> On Thu, Dec 29, 2011 at 11:31 AM, Mattmann, Chris A (388J)
> <chris.a.mattmann@jpl.nasa.gov> wrote:
>>  (removing community@ from the CC list; aren't we trying to kill that =

> thread?)
>>=20
>>  Hi Ross,
>>=20
>>  Thanks for replying. Comments below:
>>=20
>>  On Dec 29, 2011, at 11:04 AM, Ross Gardler wrote:
>>  [...snip...]
>>=20
>>>  >
>>>  > It's my understanding that anyone can start up a project at=20
> Apache Extras,
>>>  > in which case, if that person doesn't have an availid here at=20
> the ASF, and
>>>  > doesn't have an ICLA on file, then that's another=20
> situation that I won't
>>>  > speculate on. What I'm much more interested in is in the=20
> situation I presented
>>>  > within this thread. I have an availid. I am an ASF member. I was=20
> looking
>>>  > at Apache Extras as a place to share some Apache OODT plugins =
that
>>>  > leverage code that is LGPL licensed, that I couldn't otherwise=20
> share within
>>>  > the normal Apache OODT SVN home. Prior to me coming to Apache=20
> Extras,
>>>  > this has been code housed in an internal JPL SVN repository for=20
> years, even
>>>  > before we brought the software to Apache. I'd like to use=20
> Apache Extras to
>>>  > facilitate sharing with an even broader community and to share =
the=20
> plugins
>>>  > we've developed (which themselves are ALv2 licensed) with=20
> others.
>>>=20
>>>  The ASF does not release code under any license other than the =
Apache=20
> license,
>>=20
>>  Who asked to release the code? I just want an SVN to throw the code =
up at.
>>  If you look at oodt-pushpull-plugins [1], the LICENSE.txt file is =
ALv2. The=20
> code
>>  we wrote (in Java) is ALv2. The code includes a runtime Maven2 =
dependency
>>  on libraries that provide FTP protocol implementations (Ftp4Che [2] =
and=20
> JvFtp [3])
>>  that are LGPL licensed.
>>=20
>=20
> If you are saying this is compatible with ALv2 ? Then why use Apache
> Extras instead of just the oodt SVN official repo in Apache ?
>=20
> --=20
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>=20