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

proposal: REUSE compliance #957

Open
wtraylor opened this issue Dec 17, 2020 · 1 comment
Open

proposal: REUSE compliance #957

wtraylor opened this issue Dec 17, 2020 · 1 comment

Comments

@wtraylor
Copy link
Contributor

Currently, Popper’s Git repository is under the MIT license, which resides in the LICENSE file. That is common practice for open-source projects, but it has several drawbacks:

  1. The software license (MIT) doesn’t work well for media and text, which are also in the Popper repo. Creative Commons are specifically designed for media and text.
  2. A single file copied from the repository loses its licensing information because it’s not in the file itself.
  3. The copyright holders are not obvious. One would have to go through the Git log in order to find who contributed substantially (more than just removing a blank line for instance).
  4. Even insignificant content requires attribution (under the MIT license) where it would make more sense to place them in the public domain, e.g. .gitignore.

For these reasons (in particular the first one!) I suggest to make the Popper repository REUSE-compliant. REUSE is a standard from the Free Software Foundation Europe (FSFE). The website offers various resources, a tutorial, and tools.

I think it is crucial to do this now because it requires consent by the contributors to change a license, and the older a project gets the more difficult that becomes. For text and media files (images and Markdown texts) I suggest to move from MIT to CC-BY.

@ivotron
Copy link
Collaborator

ivotron commented Jan 5, 2021

thanks @wtraylor ! this is a great suggestion and I think we should do it!

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

2 participants