I believe that an equitable Contributor Agreement is a reflection of the nature of the relationship between the parties. The best agreements are mutually equitable. A one-sided Agreement such as this is inequitable and does not respect the rights or motivations of individual contributors. I believe that addressing these issues would be a positive step towards improving the Scala community.
Mike
We have had an internal discussion / round of advice on this already. The resulting policy is documented under "licensing" on this page: https://typesafe.com/activator/template/contribute
we require a liberal license and suggest public domain (aka "CC0") for seed templates and Apache for tutorials.
Activator doesn't make this decision though. It's case by case and up to the template author. Activator just copies what the author puts in the file.
I do think we intended to change some of Typesafe's seed templates to public domain and didn't do it yet. I'll confirm that. It isn't a change to Activator though, but to the templates. It will be up to other template authors how to copyright their stuff, except that we require something liberal (Apache style) to list in the catalog.
I just ran my script again. This issue has been ignored and has become worse.
56 seed projects now exist. No change for most seed projects: they still use the Apache or MIT license, except for the following which use the desirable CC0 license: cats-seed, finch-seed, libgdx-scala-seed, play-slick-codegen-flyway-seed, scala-forklift-with-slick-start-seed. No Lightbend seed projects currently use CC0.
Disturbingly, six seed projects fail to state a license. These should not be used: play-java-react-seed, primary-scala-scalatest-seed, primitive-scala-scalatest-seed, reactive-salesforce-rest-javascript-seed, salesforce-canvas-seed, spray-slick-seed.
The Scala license and CLA have come up before.
Mike
Thanks, Miles. I did not know that.
It seems, then, that changing the license would solve all problems. If that is unattainable in the short term, then an interim improvement would be to simply improve the existing CLA. I agree that bringing up the matter again seems like a good idea.
Mike
--
--
You received this message because you are subscribed to a topic in the Google Groups "scala-debate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scala-debate/ryr2q18b74w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to scala-debate+unsubscribe@googlegroups.com.
Adriaan,
I'm not implying anything, I made some very direct statements, as concretely as I could.
Seems you have adopted a contrary position,
although I am unclear what you base that opinion on, or which of the two parties that you identify with. Should we assume you do not speak for EPFL? Obviously you cannot speak for individual contributors. I think your status in legal terms is "lacks standing" and/or conflicted.
Mike,Danielle is administrative staff at EPFL, she used to handle CLAs whilethey were still in paper form and required a hand-written signature. That'sas far as her involvement goes in this :)
On Thu, Oct 27, 2016 at 11:55 AM, Michael Slinn <msl...@gmail.com> wrote:
Danielle,
You are the official EPFL contact shown below the "Software Grant and Individual Contributor License Agreement ("Agreement"), v1.0". Four days ago I invited you to participate in this discussion, but you have not responded. We respectfully ask that someone reply to this thread on behalf of EPFL, who is authorized to negotiate the issues raised.
The courtesy of an acknowledgement by yourself is requested.
Thank you,
Mike Slinn
--
You received this message because you are subscribed to a topic in the Google Groups "scala-debate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scala-debate/ryr2q18b74w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to scala-debate...@googlegroups.com.
From various people I've spoken to, I did a terrible job of explaining what I was trying to bring up. The original ensime points are here:
http://ensime.github.io/contributing/center/#licensing
I think the CLA is perfectly reasonable, but it's the scala licence that I'd like to see become Apache 2.0. Martin more or less hinted that changing the current situation would involve long protracted discussions with their legal department, which sounds painful no i can understand everybody's desire to avoid it. It is concerning when one realises how many noftwace patents EPFL owns (even in the USA) but I guess we're all willing as a community to trust that EPFL are not planning on coming after users of scalac for patent royalties.
The request in this thread for a designated jurisdiction would be something I'd completely be against. Apache doesn't do it, but Typesafe do, and it's the sole reason I don't sign the Typesafe CLA (different to the Scala CLA). There is absolutely no way I am signing anything that moves my rights to the Caliornian legal system. Jurisdiction of the defender is the norm.
Best regards,
Sam
--
--
--
You received this message because you are subscribed to the Google Groups "scala-debate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-debate+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-debate...@googlegroups.com.