adding license

[hunterowens]

This might create issues, but this will open source the contents of the website.

Discuss below.

[jiahao]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[hunterowens]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

👍

[nalimilan]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

(Given the ridiculous size of the changes I did, it would be quite funny to be the one blocking the process...)

[simonbyrne]

I didn't even know I modified anything, but...

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[ViralBShah]

For the record, I agree to relicense my contributions I have contributed to this repository under the new open source license which will be decided by this thread.

[Carreau]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

And I now understand why the first thing you should do in a repository is to put a LICENSE file.
BTW should the LICENSE precise that the julia logo and trademark are copyrighted ? and/or can reference material that could be copyrighted ? Like link to GitHub, or even the term "GitHub".

It's a real question, not a rhetorical one.

[jhasse]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

I would favor the zlib license instead of MIT. But I just contributed a few parts, so I'm okay with anything. (Just wanted to promote the zlib license! Woohoo! zlib 4tw!)

[StefanKarpinski]

Why is the zlib license good?

[jhasse]

I find the zlib license text easy to read and understand as a non native English speaker. I needed to read the MIT license multiple times to understand what is meant by "the Software". Btw: what does substantial mean?

Also the MIT license has multible versions (the FSF considers "MIT License" ambiguous), MIT YELLS AT ME USING CAPS and it's named after the MIT which I don't have anything to do with. And the important one: If I understand it correctly the MIT license forces me to include a license copy in binary distributions. Guess this doesn't apply for a website though ;)

[ViralBShah]

I say we as a community have attached ourselves to the MIT license, and the downsides are minor - but everyone is familiar with the MIT license and comfortable. I do like the zlib license, but I'd say let's just stick with MIT for now.

[staticfloat]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

I love that we can all post the same thing here, and yet it's still useful for the discussion. I agree we should stick to the MIT license for simplicity's sake; especially since it seems to provide the functionality we agree on.

[i2000s]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

You guys are wonderful! I think MIT license will work well in our case.
BTW, I saw many organizations and companies also have separated sets of Contributor License Agreements for contributors. For example, this one for W3C and this one for Ubuntu. I didn't look into them too much. But seems CLA could help ease trademarks, patents or some other copyright disputes for organizations.

[Carreau]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

You guys are wonderful! I think MIT license will work well in our case.
BTW, I saw many organizations and companies also have separated sets of Contributor License Agreements for contributors. For example, this one for W3C and this one for Ubuntu. I didn't look into them too much. But seems CLA could help ease trademarks, patents or some other copyright disputes for organizations.

As far as I read clahub and alike are a pain because you have to ask almost all new contributors to click the CLA, often integrated with Travis so when test fail you don't know if it's just about CLA, or real code issues.

A simple things would be to add a note in the "Contributing" that people canot say they were not warn to read when submitting PRs.

[shashi]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

✌️

[jayschwa]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[StefanKarpinski]

CLAs make it possible for the party controlling the CLA to unilaterally relicense something. Without a CLA, you basically can't relicense a large project with many contributors – we're seeing why right here. That's a double edged sword: sometimes relicensing can be beneficial and helpful while other times it can be dangerous. If we had a CLA and some institution decided that they owned it they could then insist on changing the license of Julia to something more restrictive like the GPL, and require commercial users to purchase non-GPL licenses (this is how FFTW works). Without a CLA, such a scenario is basically impossible, so Julia is stuck, for better or worse, with the MIT license.

[pao]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[vtjnash]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[ihnorton]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[StefanKarpinski]

Ok, now we need to pick a license. How about dual license: MIT + some CC documentation license?

Also, I'm going to reserve rights to the logo for now – the logo may affect trademark issues, so I don't want to jump into that without getting legal advice first.

[johnmyleswhite]

I also relicense my content under whatever license we choose.

[timholy]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[MikeInnes]

For what it's worth, I consent to my work in this repo being relicensed in howeversuchway as is thought best in this thread.

[StefanKarpinski]

We need to pick a license. I'm in favor of using the MIT license to keep things simple – it covers "this software and associated documentation files", which in this case is mostly documentation and only a little code, but it seems applicable all the same. IIRC, when I chatted with Bradley Kuhn about licenses at the GSoC reunion thing, he said that the MIT license was fine for documentation too.

[hunterowens]

👍 to MIT, inline with Julia's other projects.

Also, since the docs are MIT licensed, it doesn't make sense to have a seperate content license only for the website. If the docs had a license that was different, I would say use that.

[Carreau]

MIT sounds fine and everyone agrees to whatever will be chosen by the core member of julia. So is the approval of anyone else needed ?

[StefanKarpinski]

No, I just figured I'd give people a chance to comment.

[Carreau]

Then I would write an explicit deadline, like "if you have not commented by Truesday, 37th Marchuary 2095, we will assume you agree with MIT licence".

[ViralBShah]

Can we go ahead and merge this - with the MIT license?

[StefanKarpinski]

We need @JeffBezanson to agree to the MIT license.

[mlubin]

Can I stick a CC-BY on my blog post? I agree to relicense all other content I have contributed.

[IainNZ]

I agree to whatever is required :)

[eford]

For the record, I agree to relicense my contributions I have contributed to
this repository under the new open source license which will be decided by
this thread.

On Thu, Mar 5, 2015 at 6:47 AM, mbaz [email protected] wrote:

For the record, I agree to relicense all the content I have contributed to
this repository under the new open source license which will be decided by
this thread.

—
Reply to this email directly or view it on GitHub
#204 (comment)
.

Eric Ford
Professor of Astronomy & Astrophysics
Center for Exoplanets & Habitable Worlds
Center for Astrostatistics
Institute for CyberScience
Penn State Astrobiology Research Center
Pennsylvania State University

[StefanKarpinski]

@mlubin – Yes, we should add a clause to the site license saying that all content is MIT unless otherwise stated, in which case it is licenced under whatever license is indicated. So people can write their own blog posts and put e.g. a CC-BY license on it.

[StefanKarpinski]

To that end, if you've written a blog post on julialang.org and want it under a particular license, please go ahead and make a pull-request to put that license on it.

[rsrock]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[Ivo-Balbaert]

For the record, I agree to relicense my contributions I have contributed to this repository under the new open source license which will be decided by this thread.

[Keno]

Yep, I'm fine with any license chosen here for my contributions to this repository.

[nolta]

For the record, I agree to relicense my contributions I have contributed to this repository under the new open source license which will be decided by this thread.

[carlobaldassi]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[danking]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[hunterowens]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[aviks]

For the record, I agree to relicense all the content I have contributed to this repository under a new open source license which will be decided by this thread.

[HarlanH]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[tkelman]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[JeffBezanson]

I agree to license content I have contributed to this repository under the MIT license.

[markhend]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[waldyrious]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[Alexander-N]

For the record, I agree to relicense my contributions I have contributed to this repository under the new open source license which will be decided by this thread.

[StefanKarpinski]

Thanks, everyone!

[nalimilan]

A bit late to the party:

For the record, I agree to relicense my contributions I have contributed to this repository under the new open source license which will be decided by this thread.

[RhysU]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.

[jasax]

For the record, I agree to relicense all the content I have contributed to this repository under the new open source license which will be decided by this thread.