Why your next project should be public domain

Re:Why your next project should be public domain by ds9 on Thursday July 11, 2013 @09:31AM (#6025877)

The author compares PD with MIT/BSD type licences, but does not explain why he/she wants to give everyone the relatively full set of rights that these alternatives represent.

My code, outside the day job, is GPL. Why should I let others commercialize it without giving anything back? But I want to allow noncommercial use for everyone, and commercial use for those who will contribute their changes.

I'm not saying everyone should have these preferences - in fact I admire the generosity of anyone who donates valuable IP to the public domain. It's just that the title is "Why your next project should be public domain", yet the author does not explain the motive for this type of licence over others.

[ Parent | on HN ]

Re:Why your next project should be public domain by rmc on Thursday July 11, 2013 @09:39AM (#6025911)

The restrictions for GPL code is nothing to do with whether it's used commerical or noncommerically, the same restrictions apply.

Someone can use your GPLed code commerically without paying you or asking your permission, and someone can use your GPL code noncommerically as well. In both cases they have to abide by the GPL conditions.

[ Parent | on HN ]

Re:Why your next project should be public domain by ds9 on Thursday July 11, 2013 @09:49AM (#6025962)

Correct, I was just using "commercial" as a shorthand for "closed source". It is only commercial users that would use it with concealed changes if it were PD or BSD-type licence. This would enable privatizing public value.

The point is that my motive is giving value to the public, in a way that prevents it "leaking" into private profits without compensation. The effect of the article-author's licensing is giving some of the value to the public and some to private profit-oriented exploiters, while the motive for preferring the latter over the former is not stated.

[ Parent | on HN ]

Re:Why your next project should be public domain by tjaerv on Thursday July 11, 2013 @10:00AM (#6026025)

Slapping a copyleft license on your project doesn't mean that people magically won't use it where that use would be "infringing". It only means that you can sue, if you should learn of it.

See this recent talk by Rob Landley, of BusyBox fame, on how casual and widespread GPL infringement is in large corporations, and why he no longer advocates the use of the GPL:

http://www.youtube.com/watch?v=SGmtP5Lg_t0

Landley's the guy who started the infamous BusyBox GPL lawsuits that then spiraled totally out of his control, so he has more skin in the game than most.

[ Parent | on HN ]

Re:Why your next project should be public domain by belorn on Thursday July 11, 2013 @10:58AM (#6026403)

You don't actually need to sue people to make GPL have an effect. Some companies might casually infringe copyright, but they are less likely to do so once informed about it by the public. At that point, it becomes willingly infringement. Willingly infringement on a commercial scale is one of those key legal terms that turn fines into millions, and in some countries, can even become a criminal offence rather than civil (criminal offences are handled by the state rather than by the complaint).

[ Parent | on HN ]

Re:Why your next project should be public domain by steveklabnik on Thursday July 11, 2013 @10:15AM (#6026118)

This is true in theory, but in my experience, every big company asks for all the licenses of the software they use, and if it's GPL, that's a non-starter. Maybe I've only worked for the good ones.

Obviously there will be some that violate the license, as there is with any license. But the point is that you do have _some_ sort of legal recourse if they do, and also, you make your intent clear as an author: this is supposed to be Free forever.

If your anti-argument is "people will just ignore the license," then using a permissive license isn't an argument either. After all, people will just ignore it.

[ Parent | on HN ]

Re:Why your next project should be public domain by tjaerv on Thursday July 11, 2013 @10:39AM (#6026275)

It may be a cultural difference. As I recall, Landley's examples are from the East (Sony, for example). Intellectual property as a sacred institution is somewhat less established there than in the West.

The point is that users who would give credit will do so anyway (without needing a gun held to their heads), and those who won't, won't. A license only changes things by giving the recourse to sue in the latter case. If you aren't going to sue anyway (as Landley isn't, anymore), then there's not much point to using a relatively restrictive license.

I recommend watching the Landley talk. He used to be among the most rabid copyleft advocates, before the BusyBox fiasco and GPLv3.

[ Parent | on HN ]

Re:Why your next project should be public domain by rmc on Thursday July 11, 2013 @01:28PM (#6027534)

Please don't use "GPL = noncommerical" shortcut. It furthers the damaging meme that opensource and GPL is not for businesses and is only for hobbyists and is a 'toy licence'.

[ Parent | on HN ]

Re:Why your next project should be public domain by burntsushi on Thursday July 11, 2013 @10:13AM (#6026108)

> The author compares PD with MIT/BSD type licences, but does not explain why he/she wants to give everyone the relatively full set of rights that these alternatives represent.

For me, I don't believe I (or anyone) have any rights over information. Therefore, I use a license that assumes the smallest amount of rights possible (subject to legal interpretations).

[ Parent | on HN ]

Re:Why your next project should be public domain by gw on Thursday July 11, 2013 @09:43AM (#6025931)

I am specifically addressing people who already intend on using a permissive license. I understand that doesn't include everyone, but I'm intentionally restricting the scope of the subject.

[ Parent | on HN ]