<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<pre>Dear Lawrence Rosen,
Totally agree with your message which is what I'm understand when I'm
first reading the license GPLv3 and OSD. However, back to my question
is why Apache License v2.0 doesn't require Licensor open the source in
the *stated way* but still approved by OSI. It seems the Apache License
not comply with OSD #2. Why I'm start this thread is because SpringSource
new maintenance policy. I just wonder SpringSource has no obligation to
release the fixes/patches along with source code after the "free" period
base on Apache License v2.0 that you can access by some means (although
somebody say they will release the fixes in source code somewhere)
Rgds,
Arthur
John Cowan wrote:
> Open Source does not mean that if I have the source, you can make me
> send it to you. It means that if you have the source, the copyright
> owner can't stop you from sending it to whoever you want.
>
> Likewise, the GPL does not mean that if I have the source, you can make
> me send it to you, *unless* I have already (or at the same time) sent
> you a binary version.
Open source usually means what the OSI-approved license says it means.
For OSL 3.0, "Licensor agrees to provide a machine-readable copy of the
Source Code of the Original Work along with each copy of the Original Work
that Licensor distributes. Licensor reserves the right to satisfy this
obligation by placing a machine-readable copy of the Source Code in an
information repository reasonably calculated to permit inexpensive and
convenient access by You for as long as Licensor continues to distribute the
Original Work." [<a href="http://opensource.org/licenses/osl-3.0.php">http://opensource.org/licenses/osl-3.0.php</a>, §4]
So this license places an obligation on the *Licensor* to provide the source
code to licensees regardless of whether any licensee asks for it. Source
either accompanies the Original Work, or it is posted by the Licensor
somewhere convenient. [Or else the Licensor is in breach of his own license
and subject to paying damages and attorney's fees if a licensee can't
actually get the source code!]
With OSL 3.0, any licensee who in turn distributes the Original Work or
Derivative Works to third parties automatically and reciprocally becomes a
*Licensor* and thereby accepts the obligation to provide source. [§1(c), §4]
As for the GPL, the issue with that license is usually whether a licensee
who modifies the code is required to publish *its* source code. I leave that
interpretation for the FSF to write.
/Larry
Lawrence Rosen
Rosenlaw & Einschlag, a technology law firm (<a class="moz-txt-link-abbreviated" href="http://www.rosenlaw.com">www.rosenlaw.com</a>)
3001 King Ranch Road, Ukiah, CA 95482
707-485-1242 * cell: 707-478-8932 * fax: 707-485-1243
Skype: LawrenceRosen
> -----Original Message-----
> From: John Cowan [<a class="moz-txt-link-freetext" href="mailto:cowan@ccil.org">mailto:cowan@ccil.org</a>]
> Sent: Friday, September 26, 2008 8:54 AM
> To: Arthur Tam
> Cc: John Cowan; <a class="moz-txt-link-abbreviated" href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>
> Subject: Re: Apache License v2.0
>
> Arthur Tam scripsit:
>
> > Thanks for your rapid reply. But OSI approved Apache License v2.0 which
> > imply it should complied to OSD. However, if just base on the license,
> > a software using Apache License v2.0 can be not open the source. If so,
> > why the license can be approved by OSI. Am I missing something?
>
> Open Source does not mean that if I have the source, you can make me
> send it to you. It means that if you have the source, the copyright
> owner can't stop you from sending it to whoever you want.
>
> Likewise, the GPL does not mean that if I have the source, you can make
> me send it to you, *unless* I have already (or at the same time) sent
> you a binary version.
>
> OSD #2 is different from all the other parts of the OSD. #1 and #3-#10
> are constraints on the *license*: they say, "If a license does not allow
> <whatever>, it is not an Open Source license". But #2 says that if the
> *program* is not available in source form, the *program* is not open
> source. So there are two requirements for a program to be open source:
> the source must be available and the license must conform to the OSD #1
> and #3-#10. If something is not source, then it cannot be open source.
>
> --
> A mosquito cried out in his pain, John Cowan
> "A chemist has poisoned my brain!" <a
href="http://www.ccil.org/%7Ecowan">http://www.ccil.org/~cowan</a>
> The cause of his sorrow <a class="moz-txt-link-abbreviated" href="mailto:cowan@ccil.org">cowan@ccil.org</a>
> Was para-dichloro-
> Diphenyltrichloroethane. (aka DDT)
</pre>
</body>
</html>