81–90 of 185 posts
I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
Earlier quoted context omitted.
Personally it's a mix of principle and practicality. On principle I'd like to be able to put code up on Github, tell people they can use it however they like and to credit me if it suits them, but otherwise I don't want the copyright or any other associated responsibilities on it. And practically I have no ability to enforce the terms of any licence once the code is in public anyway, so why should I spend time engagi…
// Oops, I misunderstood the context of this discussion. Disregard this :p
0BSD looks short and sweet, though. I don't need people using my libraries to include my LICENSE.txt, or give attribution, or tag any changes with their own copyright notice. Just take the code and do whatever you want, no strings attached.
I use it and will continue to use it because it most accurately reflects my intentions for my software. If some organization can't comply with it, it's worse for them. They should change, not me.
> They should change, not me. OK, they should change. Great. They won't, though, so your code won't be usable by them. If that's not a problem, then your code was never really relevant to this discussion. If that is a problem, then shoulds and woulds ain't gonna help.
If I put something up for free, it's because I want other programmers to be able to freely use it. I don't care if a big corporation with expensive lawyers likes the way the license is worded.
I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
isn't it cc0?
A one-line sentence should be more than enough to clarify my intent.
Earlier quoted context omitted.
Not an alike license.
What do you mean? CC0 and 0BSD are both public domain equivalent.
It's annoying that there's no internationally recognised way of saying "No, I (and my inheritors) are not going to sue you for using this source."
I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
There are really a lot of times that this is not important, or may be detrimental to your projects success.
Earlier quoted context omitted.
I'm not pretending copyright doesn't exist, but I want other people to be able to interact with my work as if copyright and other forms of IP didn't exist. There doesn't seem to be a perfect way to achieve this. The problem with CC0 (and I believe the reason OSI doesn't approve of it) is that it says: > No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected b…
So what do you do if a company contacts you for a commercial license? If the rights are permanently waived, how do you offer a different license?
A bit off topic, but commenting on footnotes is fair play: I don't believe that 'let' is in fact autoantonymic. A let is more-or-less lost, as a noun in English, but in the form inlet and outlet it remains ubiquitous. In "let or hindrance" we might observe that a right of travel (a let) might well be a hindrance to other uses of the property. A let in tennis is so-called because you 'let' the server try again. The se…
Your objection interests me, because these are both cases that I figured out myself with much contemplation and was quite content with many years ago and have never subsequently looked up in any reference (and I doubt your alternatives ever occurred to me). But after a spot of investigation now, I don’t believe you’re right on either count and stick to what I have written, at least for now. https://duckduckgo.com/?q=…