search

lmu-osc / code-publishing

A minimal reproducible example for the workshop on Quarto manuscripts. Also includes a reproducibility checklist and instructions for creating your own workflow with your existing project.
https://lmu-osc.github.io/code-publishing/
Creative Commons Attribution 4.0 International
0 stars 0 forks source link

Relicensing #11

Open fkohrt opened 1 week ago

fkohrt commented 1 week ago

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 commented 1 week ago

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

NeuroShepherd commented 1 week ago
  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 commented 1 week ago

@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.