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

Relicensing #11

Open
fkohrt opened this issue Sep 7, 2024 · 5 comments
Open

Relicensing #11

fkohrt opened this issue Sep 7, 2024 · 5 comments

Comments

@fkohrt
Copy link
Contributor

fkohrt commented Sep 7, 2024

I would like to make the whole tutorial available under two licenses, at the choice of the reader:

CC0 1.0 is a more permissive license than the current one (CC BY 4.0), which I prefer because it puts no restrictions on how the material can be reused. It does not require attribution, however per academic requirements appropriate citation in published articles is required anyways. The reason for the second license is that it is specifically designed for code, of which there is plenty in the tutorial. By making this change, the license of the tutorial also aligns with the recommendations it gives to others concerning licenses.

In order to make the whole tutorial, including all of its materials, available under CC0 or Apache 2.0, I need the consent of all previous authors to this repository that they agree to this relicensing.

The SPDX identifier of the new license will be as follows: CC0-1.0 OR Apache-2.0

Of course, content by others that are used within this tutorial will not be covered by the new license, in particular any logos, trademarks, quotes, or screenshots are excluded.

If you agree to this relicensing, can you please respond to this issue? Of course, if you have any questions, also feel free to ask them!

@fkohrt
Copy link
Contributor Author

fkohrt commented Sep 7, 2024

This is the list of contributors I need the consent from:

@NeuroShepherd
Copy link
Member

  1. I would not say I've made any intellectual contributions to this repo that would require me to be included as an author or require my permission for license changes.
  2. More generally, I think we should come up with guidance on how the LMU OSC licenses its materials given that we already have 10-15 tutorials, and several more to be developed. My suggestion is that we leave current licenses alone, create guidance after the summer school, and then relicense content where/if needed.

@fkohrt
Copy link
Contributor Author

fkohrt commented Sep 7, 2024

@NeuroShepherd

Ad 1: I agree, but I also think it's a courtesy to ask.

Ad 2: Yes, I don't think this needs to happen before the summer school, also as @ChScheffel is on vacation right now.

@fkohrt
Copy link
Contributor Author

fkohrt commented Sep 23, 2024

Josephine and Christoph are fine with this change and I would like to move forward with it. @NeuroShepherd and @MalikaIhle, what are your thoughts on this subject?

@MalikaIhle
Copy link
Member

you seem to have this well thought out - feel free to go ahead.

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

3 participants