At the requests of my co-workers, I added the old unintern-conflicting
restart back to use-package, which makes it once again easier to solve
the common case of package conflicts than to restart the lisp.
My employer is Cadence Design Systems, GmbH, which is a German company,
so like with Gerd's contributions, it's FreeBSD licensed. I'd like to
start pushing SBCL changes I make at work back upstream, and this patch
is partially an attempt to figure out how to do that. Everything is
sorted out internally, the only question remaining is for you all: is it
okay to attach a copyright notice to a file just to include a relatively
small change like the one included here, or should I only submit more
That said, here's the patch:
Thomas Burdick <tfb@...> writes:
> Everything is sorted out internally, the only question remaining is
> for you all: is it okay to attach a copyright notice to a file just to
> include a relatively small change like the one included here, or
> should I only submit more substantial work?
I think you/Cadence are the only ones capable of answering that. Do
you consider the contribution to be substansial and original with you?
If you can say that the contribution is "not original" and/or
"insignificant" without belittling your own work I would assume the
licence can stay out. If, however you don't think those words apply
then obviously the licence needs to be applied.
My point is that while BSD-licenced additions are OK with me (and I
understand the necessity created by the German law) I'd still prefer
to see as much of SBCL as possible to remain in Public Domain.
I've no idea how others feel about this, though.
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."
Get latest updates about Open Source Projects, Conferences and News.