Conversation
Notices
-
Somewhat !disturbing that #leiningen pre-selects #EPL for you !clojure #hmm
about 10 months ago from web- Matthias Benkard likes this.
- Clacke Moved to Unlimited and Matthias Benkard repeated this.
-
@fontana indeed. The Clojure culture is even more permissive minded than that choice would suggest (generally)
-
I'm sorry about that… a teaching moment has been lost. Separately I've been thinking about creating copyleft Clojure libraries.
Richard Fontana likes this. -
@tmarble highly #disturbing experience - then again doesn't seem so disturbing as to make one want to use #maven
-
@tmarble well I've decided to meet the !Clojure community halfway and make #copyleft-next #EPL compatible
-
@fontana interesting.. can CLN be used to create a combined work with EPL code (see thread on list)?
-
@fontana what is disturbing about project creation tool defaulting to most common license in community? Seems very reasonable to me.
-
@fontana outbound? is EPL US-derivative-work copyleft less strong than "based on...such that permission required"? that could be !disturbing
-
@mlinksva It would require weakening of #copyleft-next copyleft, I think (barring future change in EPL 2.0)
-
@fontana what is this "natural" evolution you posit? canard I say. why exclude defaults in tools as an evolutionary mechanism?
-
@fontana if there is an Emacs-based skeleton generator for some language or framework predominantly using GPLv3, sounds good.
Jesús E. Franco Martínez likes this. -
@fontana I don't see benefit, unless indeed quid pro quo for EPL 2.0 bilateral, and thus GPL compatibility.
-
@mlinksva just strikes me as the licensing equivalent of peer pressure, at best.
-
@mlinksva that is not a bad idea... I had a similar thought myself, though less well-formed.
-
@fontana or, a behavioral-economics-libertarian-paternalist nudge.