3 ms·
The open source release has been pretty amazing so far, and I believe it's without precedent in Apple's history (with the possible exception of ResearchKit). I
by mikeash 11y ago
The open source release has been pretty amazing so far, and I believe it's without precedent in Apple's history (with the possible exception of ResearchKit).
I was afraid they would just toss a snapshot over the wall and leave the community to struggle with maintaining it (if anyone cared to). At best, I thought we might get some regular snapshots and discussion.
Instead, everything is out in the open, the team at Apple is apparently pushing to the same repository we get to see, they have an open bug tracker, they're actively soliciting and discussing proposals from the community, accepting patches from the community, etc.
This is business as usual for most open source projects, of course, but to see it coming from Apple blows my mind a bit. It's really great to see.
- panic 11y agoThere is some precedent at Apple: WebKit is also developed in the open.
- bsimpson 11y agoDidn't it have to be because of KHTML?
- panic 11y agoNo, originally Apple just provided huge patch sets. Here is some history from 2005, a few months before WebKit moved to a public CVS repo: https://blogs.kde.org/2005/05/13/webcore-khtml-firefox-know-your-facts https://blogs.kde.org/2005/05/13/webcore-khtml-firefox-know-...
- mikeash 11y agoGood example! And yes, KHTML's license requires Apple to release the source code for their changes, but it doesn't require them to do so in anything like a nice fashion. You can comply with the (L)GPL with tarballs and silence-implying-raised-middle-fingers rather than public repositories and bug trackers.
- tzs 11y agoIt goes even farther than that. They could have separated most of their work out into separate modules that linked with the LGPL code from KHTML, and all they would have to do to comply with LGPL is provide a way for the user to replace the LGPL code. They would not have had to release the source for their modules. LGPL is quite friendly to proprietary code.
- rsynnott 11y ago> They could have separated most of their work out into separate modules that linked with the LGPL code from KHTML, and all they would have to do to comply with LGPL is provide a way for the user to replace the LGPL code. And indeed, they _do_ do this, I think; a lot of WebKit is BSD license.
- tadfisher 11y agoYou can also comply by sending CDs in the mail. You can require postage and reimbursement for the CD as well.
- mikeash 11y agoGood point. Have any companies actually tried this as their open source license compliance strategy?
- reidrac 11y agoI may be wrong but I have the feeling that KHTML case is a good exception. Apple traditional way of complying with OSS licenses is not that nice (tarball + patches and there you are). See for example: http://www.opensource.apple.com/release/os-x-1011/ http://www.opensource.apple.com/release/os-x-1011/
- zimbatm 11y agoWebKit was open from the start because they forked KHTML which was licensed under the LGPL.
- deleted 11y ago[deleted]