Seriously? Your problem is that a contributor has to state that they have added something? Why are you worried about this?
Musical Notation <musicdenotat...@gmail.com> writes: >> Each Contributor must identify itself as the originator of its Contribution, >> if any, in a manner that reasonably allows subsequent Recipients to identify >> the originator of the Contribution. > > That's my problem. > > On Sep 12, 2013, at 19:18, phillip.l...@newcastle.ac.uk (Phillip Lord) wrote: > >> >> This is an interesting thread. I think, though, it repeats what is a >> misconception about GPL -- that you cannot produce GPL code using >> Clojure. This isn't true, as far as I can see -- you can write GPL code >> using any language, because it doesn't usage restrictions in GPL do not >> percolate through a "standard interface". >> >> So, for instance, my own library is covered by LGPL; it is possible to >> link this to GPL code without problems. >> >> Historically, the first GPL products (Emacs for example) were built >> using on non GPL platforms; it is the same issue. >> >> Sean Corfield <seancorfi...@gmail.com> writes: >>> Searching the archives would have turned up some _long_ threads about >>> this where it would have been clear that the license is not going to >>> change - as well as explaining why it is the way it is. For example: >>> https://groups.google.com/forum/#!topic/clojure/bpnKr88rvt8 (from >>> 2008) >>> >>> Sean >>> >>> On Wed, Sep 11, 2013 at 6:41 AM, Kalinni Gorzkis >>> <musicdenotat...@gmail.com> wrote: >>>> I think that Clojure should switch to a better license with similar spirit >>>> like Apache 2.0, BSD, or MIT. >>>> While the EPL doesn't have the evil "copyleft" requirement of GPL, and >>>> therefore allows and encourages commercial uses of the code, it has a >>>> requirement that makes it incompatible with the GPL: If you create modified >>>> versions of EPL-covered software, you must slap your name (or any other >>>> identity) on it. In my humble opinion, this restriction isn't justified. >>>> (All, or most, creators of modified versions will do that anyway). It may >>>> have been chosen uncarefully. Other permissive licenses better fulfill Rich >>>> Hickey's spirit. >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with your >> first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- -- Phillip Lord, Phone: +44 (0) 191 222 7827 Lecturer in Bioinformatics, Email: phillip.l...@newcastle.ac.uk School of Computing Science, http://homepages.cs.ncl.ac.uk/phillip.lord Room 914 Claremont Tower, skype: russet_apples Newcastle University, twitter: phillord NE1 7RU -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
