-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New license request: BSD-Source-Code-Justin-Gibbs #2233
Comments
Note: there is no Fedora License Data issue for this license at this time. |
@bsdimp - do you have any thoughts on this one as it seems to come from FreeBSD?? |
tl;dr: I'm fine, but would prefer a differnet name. tl: This is similar, or substantially the same, as one that we talked about last summer. This is the origin of the 'immediately at the front of the file' text that has crept into other licenses. There's maybe 168 of these in the FreeBSD kernel and another 120 in FreeBSD's user space. Though I admit that I grepped only for this particular clause. This is the source of the Having spoken to Justin about this very issue around the time we did the Nugent license, the intent of the word 'immediate' was that it's at the start of the file before code and includes which is the traditional place for such notices in BSD starting around 4.3BSD-TAHOE. Someone stole (in his view) code of his and moved his copyright notice to the end of the file to try to obscure the origin of the code while being technically complaint. Such behavior was sadly common in the early 90s, but has since all but disappeared at least from the FreeBSD and its known downstreams part of the world. FreeBSD has plans to remove or eliminate this license, but curating the tree of ~100k files is difficult and time-consuming, especially for a volunteer organization. See below for why we may not get below 50 instances after the cleanup, though I'll be committing changes to the 7 that I somehow copied later today... I'd be tempted to use |
thanks @bsdimp ! (And sorry I didn't see this sooner) so I think we can consider this approved to add, but need to finalize the name and id: So maybe... |
Yea.. still don't like the bsd-source prefix... But it is similar to the bsd license... maybe BSD-var- prefix? BSD-var-at-start-no-endorce? Since I've noticed lots of weird variations and we will want to have a sane scheme in place... this nonsense lasted only a couple of years... but was sadly blindly copied... BSD-var-bill-paul-voices comes to mind... |
License Inclusion DecisionDecision:
NameBSD Source Code Attribution - beginning of file variant License IDBSD-Source-beginning file XML markupNotes:This license is mostly the same as BSD-Source-Code but adds includes a specific requirement requiring retention of the copyright notice "immediately at the beginning of the file". Next stepsIf the license has been accepted, please follow the accepted-license process to create the PR. |
I kept there the <alt> variations from original BSD-Source-Code and slightly altered it to the actual example in the submission. Fixes: spdx#2233 Signed-off-by: Miroslav Suchý <msuchy@redhat.com>
How license meets inclusion principles
This is similar to
BSD-Source-Code
but adds some problematic language ("immediately at the beginning of the file") to clause 1 reminiscent oflibutil-David-Nugent
. It seems to have originated in FreeBSD but has propagated to a number of other projects. For example, it occurs in the Linux kernel (though sadly it may have been replaced with an incorrect SPDX-License-Identifier by now) and in the Linux userspace package acl.License Name
BSD Source Code Attribution Justin Gibbs Variant
Suggested short identifier
BSD-Source-Code-Justin-Gibbs
License or Exception?
license
URL to license text
https://github.com/lattera/freebsd/blob/master/sys/cam/cam.c
OSI Status
Not submitted
License author or steward
Unknown
URL to project(s) that use license
https://kernel.org
https://savannah.nongnu.org/projects/acl/
paste text of license here
The text was updated successfully, but these errors were encountered: