News for hackers. Stuff that matters.
Re:A discussion of Fedora’s legal state by viraptor on Thursday February 16, 2017 @06:27AM (#13659082)
If you actually want your software used, then a known license is the best. In a corporate environment, it will be much easier to approve BSD or even GPL than WTFPL. There's most likely a preapproved list of known licenses and everything else needs to go through legal.

You want your library used in the next big project? Don't use WTFPL.

Re:A discussion of Fedora’s legal state by lmm on Thursday February 16, 2017 @07:38AM (#13659415)
> In a corporate environment, it will be much easier to approve BSD or even GPL than WTFPL.

This is false in the large corporate environments I've worked in. The WTFPL is sufficiently established and mainstream that legal knows what it is and has a position that it's fine. Use of anything GPL requires a lot more specific review to ensure we'll be compliant.

Re:A discussion of Fedora’s legal state by viraptor on Thursday February 16, 2017 @04:08PM (#13663588)
Yet true in my corporate environment. Corporate environments can differ.
Re:A discussion of Fedora’s legal state by lmm on Friday February 17, 2017 @06:37AM (#13667514)
I'm amazed. Your legal department is happy to approve the GPL (a long license that imposes significant obligations if you distribute anything) but not the WTFPL? I can understand maybe the WTFPL simply isn't on the list yet (though I'm still amazed they wouldn't put strict requirements on use of anything GPL, because you can't "statically" comply with the GPL - you have to take particular actions every time you distribute a derived work, and legal would need to be confident this was happening), but that's a one-time cost, and there's enough WTFPL software out there for it to be worthwhile.
Re:A discussion of Fedora’s legal state by belorn on Friday February 17, 2017 @09:22AM (#13668377)
A lot of companies have policy to always include license documents in specific place where customer can see it.

Very few companies are fine to write "fuck" in documents that reaches customers. Very few are fine to have no license attached to software.

A lot of companies distribute unmodified GPL software and have no issue with including the GPL licensing text (and source code) in ways that reaches customers.

Re:A discussion of Fedora’s legal state by lmm on Friday February 17, 2017 @10:22AM (#13668781)
> Very few companies are fine to write "fuck" in documents that reaches customers. Very few are fine to have no license attached to software.

Redistribute it under another license then? The WTFPL gives you permission to do that, after all.

> A lot of companies distribute unmodified GPL software and have no issue with including the GPL licensing text (and source code) in ways that reaches customers.

It's perfectly doable. But it's nonzero effort and it creates an ongoing obligation (as long as you're going to keep distributing the software, or something like 3 years after if you do the more customer-friendly thing of only distributing the source on request). I'm not surprised that a company would do it, but I'm amazed that a company would consider it less burdensome than the WTFPL.

Re:A discussion of Fedora’s legal state by belorn on Friday February 17, 2017 @11:03AM (#13669157)
Yes, writing a new license and just use that would be the better solution, but its in direct contrast to how companies handle software license. You don't generally take software and then replace the license with your own and pretend that the original license don't exist, even if the license do permits it.

As for the GPL ongoing obligation, I am not sure how many picks the source-on-request method or the subgroup of those that also get a request. Its a fix-it-later issue compared to the more immediate issue of "fuck" appearing in the product.

Just to be a bit clearer on my own opinion, a good company should have no issue of using both licenses. Writing code is costly and time consuming, and a good company should focus on core aspects rather than reinventing programming infrastructure. If the license is compatible with the business model then use it. If its not, ask the author for a exception. If all fails, then and only then waste developers time. In video games I often see software licenses in game credits, and many game studios will use any and all licenses that isn't in direct conflict with the business model, and I assume its because that market is too competitive to not do so. Including LGPLv3 source code on the disk (or offering) isn't a big deal compared to a game shipping a month or two later.

Re:A discussion of Fedora’s legal state by lmm on Friday February 17, 2017 @12:11PM (#13669856)
> You don't generally take software and then replace the license with your own and pretend that the original license don't exist, even if the license do permits it.

Sure, it's a slightly unusual thing to do. But I think it's less unusual than what you have to do for GPL compliance.

> As for the GPL ongoing obligation, I am not sure how many picks the source-on-request method or the subgroup of those that also get a request. Its a fix-it-later issue compared to the more immediate issue of "fuck" appearing in the product.

Legal should not be treating it as a fix-it-later issue if they're caring about licensing at all. Distributing GPL code not in compliance with the license is exactly as bad as distributing code you have no license to at all (and opens you up to exactly the same liability, given that the damages for copyright infringement are statutory).

Don't get me wrong, I support the GPL, but license compliance is important and nontrivial. Note that the LGPL is a very different license from the GPL, and much easier to comply with.

Re:A discussion of Fedora’s legal state by burntsushi on Thursday February 16, 2017 @07:04AM (#13659217)
Not sure I really buy this. I have at least one project[1] that lots of people use despite the WTFPL. I don't use the WTFPL any more though.

There's also SQLite, which is probably one of the most widely use libraries in existence. It's in the public domain.

[1] - https://github.com/BurntSushi/toml

Re:A discussion of Fedora’s legal state by kuschku on Thursday February 16, 2017 @10:48AM (#13660812)
> It's in the public domain.

With an additional license for countries, like Germany, where the public domain doesn’t exist (as copyright isn’t really a thing, but only "creator rights" and "usage rights")

Re:A discussion of Fedora’s legal state by annnnd on Thursday February 16, 2017 @06:56AM (#13659183)
Why not? It is basically a public domain license, it just uses more colorful language. IANAL, but I see no problem using such code in corporate environment. What are the risks?
Re:A discussion of Fedora’s legal state by halomru on Thursday February 16, 2017 @08:25AM (#13659684)
It's very unclear how it works around the world in different legal systems. In comparison the CC0 spends a lot of words to work with all the jurisdictions where you can't legally give up all rights over a work.

If you are operating internationally (like nearly the entire tech industry), complying in as many jurisdictions as possible is very valuable

Re:A discussion of Fedora’s legal state by ptaipale on Thursday February 16, 2017 @07:22AM (#13659331)
YANAL, and IANAL, but those who are, are always suspicious of modified license texts. They always fear there's a hidden catch that the language (colourful or not) tries to hide and get you tricked. And they are not entirely unjustified to do so.

Also, in a corporate environment, there's typically some additional overhead cost and bureaucracy and approvals that a new license text brings in, even when the engineers and lawyers manage to agree everything is OK.

Re:A discussion of Fedora’s legal state by viraptor on Thursday February 16, 2017 @07:35AM (#13659392)
I don't think there's a problem. The situation I experienced is just that standard OSI licenses are preapproved. Anything else needs to go via manual process which takes days/weeks. So even if you say "do whatever you want", it's not a standard OSI license which means I have to get a confirmation first. And if I can find/write an alternative quicker, I will.
Re:A discussion of Fedora’s legal state by kuschku on Friday February 17, 2017 @01:48PM (#13670649)
There actually is a problem: There’s countries where "public domain" is not a thing, so the WTFPL becomes legally the same as "all rights reserved".

Which is a problem.

Re:A discussion of Fedora’s legal state by jcranmer on Thursday February 16, 2017 @11:59AM (#13661471)
WTFPL lacks a disclaimer of the implied warrant of merchantability. If you're the author of such code, you could be sued for damages if there is a bug in it.