Apple Public Source License Now FSF Approved

BWJones writes "Apple has now made their public source license 2.0 free. From the release "The Darwin team at Apple is pleased to announce that version 2.0 of the Apple Public Source License has been certified as a 'Free Software License.' APSL 2.0 includes numerous changes and simplifications to make it even easier to use Apple Open Source software as part of your programs. To indicate acceptance of APSL 2.0, you can now use your new or existing "Apple ID", rather than having a separate Darwin account."" proclus adds "This is great news for Darwin-based free software projects like The GNU-Darwin Distribution and Fink. GNU-Darwin has had an ongoing discussion about this development, and annouced and end to our 'Free Darwin Campaign,' so long as Apple avoids DMCA-based legal action."

Comments

Long arm of open source community

[Doesn't_Comment_Code]

This is one more feather in our collective cap. This means that in very recent history (less than a year) open source was significantly impacted every major player. Microsoft is keeping a close eye on us and implementing an open source lab. Big business companies like IBM and Oracle have jumped onboard. And now Apple is realizing that its better to go with it than fight it. This is great news. I could have dreamed of this five years ago, but I never would have bet on it.

We are making history and leaving a big footprint. Little people influencing very large companies.

Re:External Deployment

[ShieldW0lf]

Licensees will only be required to release source code of Modifications they "Externally Deploy" (new Section 1.4, and Sections 2.1, 2.2). "External Deployment" is defined to cover the external distribution of APSL'ed code or use of APSL'ed code to provide a service (including content delivery) to a third party through electronic communication with that party.

Don't know how I feel about this one...

You can't run an application service provider program without releasing changes to all your clients, and possibly the public if your clients deal with the public?

You can't run a b2b service without releasing all your changes to your distributors that use it and your clients that use it?

This is very different from the "no black box public distribution" that I previously considered the GPL to represent.

If I had a client who sold widgets, and he had to release all his source to clients who connected to his b2b setup, allowing them to leave him and then give all his internal systems to his competitor, even though he never distributed his software, I don't think he'd be wanting to buy anything I built.

Could you insulate against this by putting a "dumb layer" between your apps? You could argue that ANY system that was interacted with by the public, however indirectly, required publication... in most businesses, this would eliminate the "internal deployment" angle almost totally, unless you had a typist carrying out your data-syncronisation work