----- Original Message ----
> From: "Mattmann, Chris A (388J)" <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: Wed, December 1, 2010 11:38:31 AM
> Subject: Re: Basing Apache releases on releases from incubating projects
>
> On Dec 1, 2010, at 8:04 AM, Joe Schaefer wrote:
>
> > ----- Original Message ----
> >
> >> From: "Mattmann, Chris A (388J)" <[email protected]>
> >> To: "[email protected]" <[email protected]>
> >> Sent: Wed, December 1, 2010 10:57:48 AM
> >> Subject: Re: Basing Apache releases on releases from incubating projects
> >>
> >> Hi Owen,
> >>
> >> It's my understanding that Apache software can depend on other software
>that
>
> >> falls within the guidelines here [1]. ASF Podlings, by definition are
>software
>
> >> (released or not) that fall under the confines of Category A from [1],
> >> so
>it's
>
> >> fine to depend on them (again, *released* or not).
> >
> > Not so fast. We don't require podlings to have their legal issues fully
> > resolved until it's time to release, so other projects should *not* be
> > shipping a podling's non-released codebase.
>
> Hrm, umm, so what's the difference between this, and oh I don't know,
> some other library I pick up as a TLP off Google code who claims their
> source is ASLv2 licensed? I have no guarantee over there that the license
> issues are resolved either, yet we do that all the time over here in Apache?
>
> So, I don't agree with your point.
The major issues with liability are always tied up in who releases stuff. We
aren't all that liable for code we are redistributing from someone else's
release. But we are liable for releasing code that is only being otherwise
distributed out of our svn repo.
Don't believe the remarks of Niclas and others who live in countries where
all copyright infringement violators are subject to public stonings. In the
US damages are assessed based on how many times and for what purpose those
infringements are actually done.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
