New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add license to site #1889

Merged
merged 9 commits into from Jan 1, 2014

Conversation

Projects
None yet
6 participants
@doktorbro
Member

doktorbro commented Dec 29, 2013

This is an answer to #1885 (comment). The text on the License page is from Jquery.

@afeld

View changes

site/docs/license.md Outdated
permalink: /docs/license/
---
You may use any Jekyll project under the terms of the [MIT License]({{ site.repository }}/blob/master/LICENSE). The MIT License is simple and easy to understand and it places almost no restrictions on what you can do with a Jekyll project. You are free to use any Jekyll project in any other project (even commercial projects) as long as the copyright header is left intact.

This comment has been minimized.

@afeld

afeld Dec 29, 2013

Contributor

You may use any Jekyll project under the terms of the MIT License

That makes it sound like any Jekyll site is automatically MIT licensed.

@afeld

View changes

site/_includes/footer.html Outdated
@@ -1,7 +1,7 @@
<footer>
<div class="grid">
<div class="unit one-third center-on-mobiles">
<p>By <a href="http://tom.preston-werner.com">Tom Preston-Werner</a>, <a href="http://quaran.to/">Nick Quaranto</a>, and many more <a href="{{ site.repository }}/graphs/contributors">awesome&nbsp;contributors</a>.</p>
<p>Written by <a href="{{ site.repository }}/graphs/contributors">Jekyll&nbsp;Team</a>. Released under the <a href="{{ site.url }}/docs/license/">MIT&nbsp;License</a>.</p>

This comment has been minimized.

@afeld

afeld Dec 29, 2013

Contributor

"Written by the Jekyll Team"

@parkr

This comment has been minimized.

Member

parkr commented Dec 29, 2013

Cool! Thanks for putting this PR together.

Do you think we need a whole new page just for the license, though? Seems like we could just say "The contents of this website are © 2013 Tom Preston-Werner under the terms of the MIT License." in the footer and that would be that.

doktorbro added some commits Dec 29, 2013

Revert "Add license page"
This reverts commit 8e94371.
@doktorbro

This comment has been minimized.

Member

doktorbro commented Dec 29, 2013

@parkr I think we should not mention the originator but the whole team. As @mojombo have said:

I think it would be a nice gesture to signify that it's a community project and that we intend to work on it more.

@parkr

This comment has been minimized.

Member

parkr commented Dec 29, 2013

@parkr I think we should not mention the originator but the whole team.

I agree that it would be nice, but we can't modify the license's copyright holder once copyright has been claimed. At least according to U.S. law that I know. We'd need consent of every person who's contributed to this project over the last 5 years to do so. @benbalter would know more, though.

@parkr

This comment has been minimized.

Member

parkr commented Dec 29, 2013

But, overall, I think adding a license is the perfect plan. Thanks again for writing this PR :)

@benbalter

This comment has been minimized.

Contributor

benbalter commented Dec 29, 2013

we can't modify the license's copyright holder once copyright has been claimed

True (although it can be assigned), but here, we don't actually care about copyright, but rather license. The original contributor retains the copyright in any case, and licenses it to the world, here under an MIT license.

We'd need consent of every person who's contributed to this project over the last 5 years to do so.

Yes and no. It depends on the license you're moving to. The copyright holders have already granted certain rights. If we're moving to a license that provides end users with fewer rights, e.g., CC-BY-SA-NC, we could sublicense the contribution under more restrictive terms. We couldn't however, release under less restrictive terms (e.g grant additional rights we don't have).

Think of it as the author has ten "rights'. He retains one, and says to the world, you can have these nine. We as project contributors then take those rights, and bundle them with all the other contributors granted rights, and distribute them as Jekyll. We can distribute all nine, or two or three, but can't distribute all ten, because we don't have that tenth right. The original author retains it.

So it depends on what license we're moving to, but it may be possible to do so without having to reach out to contributors. In any case, it'd just be contributors to the Docs, not the whole project, but again, may not be worth the effort, unless there's a specific reason to make the move.

doktorbro added some commits Dec 29, 2013

@mattr-

This comment has been minimized.

Member

mattr- commented Dec 30, 2013

👍 from me!

Your turn, @parkr!

@ghost ghost assigned parkr Dec 30, 2013

@parkr

View changes

site/_includes/footer.html Outdated
@@ -1,7 +1,7 @@
<footer>
<div class="grid">
<div class="unit one-third center-on-mobiles">
<p>By <a href="http://tom.preston-werner.com">Tom Preston-Werner</a>, <a href="http://quaran.to/">Nick Quaranto</a>, and many more <a href="{{ site.repository }}/graphs/contributors">awesome&nbsp;contributors</a>.</p>
<p>The contents of this website are ©&nbsp;2013 <a href="http://tom.preston-werner.com/">Tom Preston-Werner</a> under the terms of the <a href="{{ site.repository }}/blob/master/LICENSE">MIT&nbsp;License</a>.</p>

This comment has been minimized.

@parkr

parkr Dec 31, 2013

Member

Should we use &copy; instead of the literal there?

parkr added a commit that referenced this pull request Jan 1, 2014

@parkr parkr merged commit c00c8c2 into jekyll:master Jan 1, 2014

1 check failed

default The Travis CI build failed
Details

parkr added a commit that referenced this pull request Jan 1, 2014

@doktorbro doktorbro deleted the doktorbro:site-link-license branch Jan 1, 2014

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.