Linked by Eugenia Loli on Thu 12th Jul 2007 19:23 UTC, submitted by wibbit
Apple Apple has bought the CUPS code base, and has hired it's lead developer. "CUPS was written by Michael R Sweet, an owner of Easy Software Products. In February of 2007 Apple Inc. hired Michael and acquired ownership the CUPS source code. While Michael is primarily working on non-CUPS projects, he will continue to develop and support CUPS, which is still being released under the existing GPL2/LGPL2 licensing terms."
Thread beginning with comment 255393
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Ooookay...
by steviant on Sat 14th Jul 2007 00:31 UTC in reply to "RE[2]: Ooookay..."
steviant
Member since:
2006-01-11

For a start, you don't even know how to *spell* contributor, so I don't see why it would affect you. ;)

Secondly, you're wrong, wrong, wrong about iCal and ZeroConf. In both of those cases Apple released code.

iCal may be a specification, but Apple also released source sometime last year for "Darwin Calendar Server" which is what I believe the original poster referred to. In the case of ZeroConf, Apple released code for MDNSResponder, which is essentially all that is required to begin advertising services.

If you're wondering, both projects are now covered by the Apache 2.0 License, so unless you object to the majority of the world's websites (this one included) which are served by Apache and free OS's which include Apache, you probably have no reason to be concerned.

If any license change occurs, my guess is it will be to move it to the same license as the majority of Apple's other open source projects, namely the Apache 2.0 License.

The only reason I can imagine that Apple would want to own the copyrights to allow them to do things which the GPL would prohibit them from doing, like integrating CUPS more deeply into the OS. The real problem with that is that by enabling themselves to do so they gain a competitive advantage without having the bad PR of changing the license.

If that were to happen, and I were a contributor to CUPS, I would be watching very closely to make sure that my code is not being used as leverage against competition, and would be ready to pull the plug on their copyright to my code come release-day.

There is no need to overreact though, Apple have learned through bitter experience that geeks are less tolerant of being shafted than their traditional (fan) base.

Reply Parent Score: 1