4 ms·
This is a wonderful article, and a great summary of the current open-source software licensing issues, but I feel uneasy about the apparent conclusion. After
by nkurz 13y ago
This is a wonderful article, and a great summary of the current open-source software licensing issues, but I feel uneasy about the apparent conclusion. After dozens of paragraphs about the intricacies and uncertainties of licensing, it seems to suggest that if instead of asking people to choose from a drop-down list of licenses, things would be greatly improved if they were given a 10 minute overview before being forced to choose.
Any overview, even if vetted by vast teams of international copyright lawyers, can only brush the surface of the issues. At best, you could end up with a list of reasons to eliminate certain licenses based on your personal goals, with the wordings chosen by the ideologies of the lawyers involved. Would this be any better than GitHub deciding internally which license(s) they want to promote, and putting these at the top of the list?
I think we should start to seriously consider simplifying our software licensing environment
This I can agree with. Having seen the amount of time wasted by open-source projects on licensing issues, copyright worries, and patent fears (and the resulting reinvention of the wheel) I think simplification is the way to go. Personally, I don't think this simplification can be achieved by piling more layers of abstraction on top of copyright and contracts.
Most books and papers seem to get along alright without licenses. I'd love to see "fair use" defined more broadly, but I don't think that adding additional licensing would be an improvement. Most electronic parts can be used as building blocks for whatever project you want without worrying whether one part will "contaminate" the others or "infect" the project. Music is licensed more frequently, but I don't think amateur musicians would benefit if they had to agree to terms of service before attending a concert.
Please tell me again why we want every project on GitHub to choose and stick to a license? And who is this "we", and what do "we" stand to gain?
- spacelizard 13y agoYes, the morass of software licensing sucks. But unfortunately another side effect of that is that not choosing a license or making uninformed decisions about licensing creates situations that end up with users becoming extremely susceptible to copyright trolling. It is true though that the solution is obviously to ease up on some of the powers granted by copyrights.
- nkurz 13y agosituations that end up with users becoming extremely susceptible to copyright trolling I worry the trolling is largely extra-legal, and that the actual terms of the license matter little. Currently, anyone can create an account on GitHub and without proof-of-positive-ID can apply any license to any code they choose to upload. Whether they have the right to issue this license is unknown to the user other than by direct due diligence. Consider: I take a small function out of a piece of proprietary or GPL code, and without permission put it into a library which I publish on GitHub. You use it in your successful commercial venture. Is your legal exposure different depending on whether I chose "BSD" from the drop-down or left it unlicensed? Is my liability different? What about GitHub's? Does there exist a software equivalent of real-estate title insurance? I like the SQLite approach to this: http://www.hwaci.com/cgi-bin/license-step1 http://www.hwaci.com/cgi-bin/license-step1
- tjaerv 13y ago> Currently, anyone can create an account on GitHub and without proof-of-positive-ID can apply any license to any code they choose to upload. Whether they have the right to issue this license is unknown to the user other than by direct due diligence. A good exemplar of this from just the other day: http://lists.gpl-violations.org/pipermail/legal/2013-July/004100.html http://lists.gpl-violations.org/pipermail/legal/2013-July/00...
- nkurz 13y agoYes, that is a gem. With liberty, I've submitted it hoping it will also be a conversation starter: https://news.ycombinator.com/item?id=6094223 https://news.ycombinator.com/item?id=6094223 Reading one of the linked comments, it's even more interesting because the "Samsung proprietary code" looks clearly copied from the Linux kernel: http://phoronix.com/forums/showthread.php?82576-Samsung-Accidentally-Leaked-The-exFAT-Linux-Driver&p=344872#post344872 http://phoronix.com/forums/showthread.php?82576-Samsung-Acci... Sometimes I wonder if much of the corporate fear of open source is that it would slow development and restrict code reuse, since rather than just swiping the code and releasing the driver, once it's out in the open they'd also have to have endless discussion of what is and is not a derived work.
- tjaerv 13y agoYes, the conclusion feels like a letdown. With the title of his post ("post copyright") you might think he'd have something to say about releasing code into the public domain, yet there's no mention at all of this. How is licensing your code under the copyright monopoly supposed to be "post copyright"? The introduction at http://unlicense.org http://unlicense.org seems spot on for the topic of the blog post: Why use the Unlicense? Because you have more important things to do than enriching lawyers or imposing petty restrictions on users of your code. How often have you passed up on utilizing and contributing to a great software library just because its open source license was not compatible with your own preferred flavor of open source? How many precious hours of your life have you spent deliberating how to license your software or worrying about licensing compatibility with other software? You will never get those hours back, but here's your chance to start cutting your losses. Life's too short, let's get back to coding.
- the_mitsuhiko 13y ago> you might think he'd have something to say about releasing code into the public domain Author of the post here. I'm Austrian - the whole concept of public domain does not even exist in my legislation. I cannot legally waive copyright currently. The closest to putting code into the public domain is probably something like the WTFPL but I am perfectly fine with my stuff having a few more restrictions through the MIT/BSD to avoid license confusion. > How is licensing your code under the copyright monopoly supposed to be "post copyright"? It is not. However there is a certain trend ongoing that people wish the whole copyright system would be reformed and that would have more impact on Copyleft licenses than MIT/BSD. Aside from all of that I don't want to make license decisions for other people. :-)