Correct 0BSD License Title

[ghost]

github/choosealicense.com#464 (comment)

Edit: The OSI recognizes it as the "Zero-Clause BSD" license which you may confirm here: http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2018-November/003830.html

[landley]

Please don't. Just leave it alone.

[landley]

I should clarify: I want to encourage your interest in 0BSD and I'm happy you like it and want to promote its use, but... I just spent months convincing OSI that SPDX approved the name first and that OSI should change to match SPDX, after years of disagreement on that subject. If OSI didn't quite manage to get all the way there, that's still on OSI. SPDX came first.

Please don't touch the carefully piled rocks. I spent so long getting them up. The difference between "Zero Clause BSD", "BSD Zero Clause", and "0BSD", with an without hyphens, is trivial. Heck, when I put the name on my toybox website in 2014 (after years of using it informally) I put scare quotes around "zero clause" and didn't even capitalize it, and that's still what it says today:

landley/toybox@1748bdb6bfe4

[landley]

I just updated http://landley.net/toybox/license.html page to be closer to what SPDX says, and link to the SPDX page. Thanks for the push on that.

[ghost]

We respect you and your license deserves attention. Given the licences history I can't think of another license I'd rather use personally besides WTFPL (or maybe Zlib) for my public warez—especially when I want to start charging businesses I know won't touch the WTFPL because of crude language.

Maintainers here I think are on calls and emails most of the time so I don't think this will get merged. But at some point hopefully someone will update the License List. Kudos to you @landley.

[ghost]

Merge ready. As luck would have it someone updated the same line I was editing and didn't bother to fix the license name.

[jlovejoy]

@jhabdas @landley - I'm not sure I'm following the thread here: you are suggesting to change the full name, essentially the order of the words "BSD Zero Clause License" v. "Zero Clause BSD License"
I believe the reason we went with the former was for consistency with the other "BSD" licenses and to allow like-licenses to list together when the list is sorted alphabetically. But the short identifier was 0BSD - I'm guessing that was Rob's preference and we respected that as he's the license author.
Is there a compelling reason to change the full name now? Or are we leaving it be and I can close this PR?

[jlovejoy]

@landley - btw, I did see that the OSI (finally) came around on the name thing. Thanks for your patience and perseverance on that. I was alerted to that thread a bit too late to chime in.
FWIW, ever since that snafu, we have started asking if the submitter of new licenses is the license author/steward and if not, tried to find them. I have even asked for this to be added as a question in our new online new license submission tool :)

[ghost]

@jlovejoy Unless I'm mistaken author/publisher names the license, not the committee.

[landley]

I commented about this here: github/choosealicense.com#464 (comment)

I would prefer SPDX not change its name for this license, for the reasons stated there. If OSI still can't get the order and hypens to exactly match SPDX, that's OSI for you. I'm happy they've stopped causing obvious confusion that was interfering with adoption of the license.

If you want to replace the "Rob Landley" in the copyright statement of https://spdx.org/licenses/0BSD.html with the generic "Your Name" as described at github/choosealicense.com#643 (comment) that would be nice, but it wasn't a big enough issue to bother you about on its own.

Keep up the good work,

Rob

[landley]

P.S. I suggested the 0BSD short identifier because I thought that's how BSD did it. They're always talking about "2BSD" and "3BSD" and so on. Turns out that's not the 2 clause license, that's the BSD 2.0 release and BSD 3.0 OS releases.

People thought I knew what I was talking about rather than correcting me, and at this point it's there and in use, and as with the qwerty keyboard it's probably best to just leave it like that.

[ghost]

Closed per feedback from Rob. It's referential but I understand he said "leave it as is".

[jlovejoy]

If you want to replace the "Rob Landley" in the copyright statement of https://spdx.org/licenses/0BSD.html with the generic "Your Name" as described at github/choosealicense.com#643 (comment) that would be nice, but it wasn't a big enough issue to bother you about on its own.

@landley - this has been accommodated via our matching markup which indicates that that text is "replaceable" - meaning it can be any name. :)

[waldyrious]

this has been accommodated via our matching markup which indicates that that text is "replaceable" - meaning it can be any name. :)

For the record (as the person who submitted that change in #738), I still think it's unnecessarily confusing for humans. I would gladly submit a PR to do as @landley suggested:

If you want to replace the "Rob Landley" in the copyright statement of spdx.org/licenses/0BSD.html with the generic "Your Name" as described at github/choosealicense.com#643 (comment) that would be nice

...if that would be OK, @jlovejoy.

[jlovejoy]

@waldyrious it's not that that wouldn't be okay, it's just that we have a lot of other more pressing work that we could use help with if you have time!

[waldyrious]

I understand. I offered to do so because this happens to be (1) a particular itch of mine I'd be happy to scratch, as a self-professed fan of short-and-sweet licenses like 0BSD and ISC, and (2) a small enough issue that I can easily dig out a few minutes to submit a PR (I wish I had time to help out more!).

I'm not sure the other pressing work you speak of would fit similarly within my availability and priorities, but do let me know if you think otherwise :)

[jlovejoy]

I'm not sure the other pressing work you speak of would fit similarly within my availability and priorities, but do let me know if you think otherwise :)

anything that is in a existing issue, really! We can also always use help with adding new licenses, once they've been approved to be added to the list. That process is now documented here: https://github.com/spdx/license-list-XML/blob/master/DOCS/new-license-workflow.md (and the general info in Contributing)