Skip to content
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 contributor license #33

Open
djfurman opened this issue Sep 3, 2021 · 10 comments
Open

Add contributor license #33

djfurman opened this issue Sep 3, 2021 · 10 comments

Comments

@djfurman
Copy link

djfurman commented Sep 3, 2021

Excited for this project; would you please consider adding a license to this repository so I can contribute to your documentation? I have a PR ready to help improve, but I need a license declared for review by our open source office.

@msrd0
Copy link
Member

msrd0 commented Sep 3, 2021

Hi @djfurman and thanks for your interest in this project!

I'd expect I can't just upload a license file to this repository, it probably requires consent by all contributors. Also, I don't know any license that is specifically for documentation - do you just put MIT/Apache like for code? I'm open for suggestions.

@djfurman
Copy link
Author

djfurman commented Sep 3, 2021

MIT or BSD-3 would let me contribute without restriction. The current maintainers should be listed as copyright holders and of course be in agreement, but I would be happy to contribute if a license can be defined and added.

The framework itself allows choice between MIT and Apache2 which could mirror here.

Thanks for the quick response!

@msrd0
Copy link
Member

msrd0 commented Sep 4, 2021

So the plan would be to relicense this repository under dual MIT and Apache-2.0 just like the main repository. This requires permission by all contributors. Can you please reply to this issue and explicitly state if you consent to relicense your contribution under both the MIT and the Apache-2.0 license? Thank you.

@secretfader
Copy link
Contributor

@msrd0 Relicensing under MIT, Apache 2.0 is an acceptable plan to me.

@berkus
Copy link
Contributor

berkus commented Sep 4, 2021

@msrd0 I'm generally fine with re-licensing under SPDX: MIT OR Apache-2.0, however for the documentation sites CC BY-NC-SA might be a better one.

See for example my site's license.

@bradleybeddoes
Copy link
Contributor

I consent to the change in license 😀

@bardiharborow
Copy link
Contributor

I hereby license any of my past or future contributions to this repository under the terms of the MIT license or the Apache 2.0 license.

@smangelsdorf
Copy link
Contributor

I'm sorry, I completely missed this in a sea of notifications back when it happened. It showed up today in an unrelated search I was doing.

I consent to the change in license, for whatever it's worth this much later. 😅

@berkus
Copy link
Contributor

berkus commented Apr 3, 2023

I consent to the change in license, for whatever it's worth this much later. 😅

It's dead, Jim.

@smangelsdorf
Copy link
Contributor

Yeah, fair call. I had two choices:

  1. Reply to a super old issue that everyone has forgotten
  2. Not reply to a super old issue that might eventually matter

🤷🏻‍♂️ Lesser of two evils.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants