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: CC BY-SA 4.0 #2097

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Relicensing: CC BY-SA 4.0 #2097

merged 1 commit into from
Apr 15, 2024

Conversation

jonaharagon
Copy link
Member

Changes proposed in this PR:

  • Change site license from CC BY-ND 4.0 to CC BY-SA 4.0

We should have consent from all copyright holders to relicense content w/ team approval already, so that is not an issue. My current feeling is that #1820 was probably a mistake, and that the No Derivatives license doesn't really provide us with significant advantages, but it does mean we're not really "giving back" to the community in a sense, it doesn't feel open.

  • I have disclosed any relevant conflicts of interest in my post.
  • I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
  • I am the sole author of this work.
  • I agree to the Community Code of Conduct.

@jonaharagon jonaharagon added the m:contributing relating to contributing/community label Mar 21, 2023
@jonaharagon jonaharagon self-assigned this Mar 21, 2023
jonaharagon added a commit that referenced this pull request Mar 21, 2023
@netlify

This comment was marked as outdated.

@dngray
Copy link
Member

dngray commented Mar 22, 2023

My only concern is that some of our articles could be considered "testimony" as in what we observed when we tested something. In such a situation no derivatives makes sense:

The CC BY-ND is not compatible with either the OSI's Open Source definition or the FSF's Free Software Definition.

That said, the FSF still considers it to have an appropriate use that is compatible with their movement: to licence opinions and testimonies. The licence shouldn't be used for documentation or project assets, but they do consider it to be appropriate for works which represent the thoughts of a single person and which it would be misleading to change. To quote Richard Stallman:

The second class of work is works whose purpose is to say what certain people think. Talking about those people is their purpose. This includes, say, memoirs, essays of opinion, scientific papers, offers to buy and sell, catalogues of goods for sale. The whole point of those works is that they tell you what somebody thinks or what somebody saw or what somebody believes. To modify them is to misrepresent the authors; so modifying these works is not a socially useful activity. And so verbatim copying is the only thing that people really need to be allowed to do.

I also can't think of a reason someone would need to take our site "modify it" and reproduce it, that doesn't really make sense. If there were errors they would just contribute them back here and that would benefit everyone, including translations.

@jonaharagon jonaharagon mentioned this pull request Mar 22, 2023
4 tasks
@jonaharagon
Copy link
Member Author

I guess that is a convincing argument... We can reopen this if anyone else has a different opinion but I'm fine with closing this issue.

@jorgesumle
Copy link

We can reopen this if anyone else has a different opinion

I have a different opinion.

Non-derivative licenses promote centralization. If I want to make my own version and publish it elsewhere, I can't. If I want to improve something or translate it (maybe I don't want to use the centralized and privacy-invasive software that you promote here), I can't if I don't have the permission.

@jonaharagon
Copy link
Member Author

maybe I don't want to use the centralized and privacy-invasive software that you promote here

If you don't like our work then why use it at all?

@jorgesumle
Copy link

If you don't like our work then why use it at all?

I'm talking about Crowdin and GitHub (both proprietary and non-free). It's called network effect. I host my projects on NotABug and mostly contribute translations using Weblate.

@jonaharagon
Copy link
Member Author

Looking at your Weblate profile, the projects that you contribute to are simply very technically different than privacyguides.org.

Weblate was something we heavily investigated, and I had my own Weblate server set up to try to use for this purpose. The problem was that Weblate simply could not work with unstructured Markdown files effectively.

The alternative would have been somehow converting the entire website into individual strings and a format understandable by translation platforms like Weblate, but that would have made it virtually impossible to contribute on the English side of things.

Crowdin has native support for Markdown documents, and as far as I'm aware it is the only free (as in beer) solution that does so.

@jorgesumle
Copy link

The problem was that Weblate simply could not work with unstructured Markdown files effectively.

WeblateOrg/weblate#3106

@jonaharagon jonaharagon reopened this Apr 12, 2024
jonaharagon added a commit that referenced this pull request Apr 12, 2024
Copy link

github-actions bot commented Apr 12, 2024

Your preview is ready!

Name Link
🔨 Latest commit 7346c4d
😎 Preview https://2097--glowing-salamander-8d7127.netlify.app/

@jonaharagon jonaharagon marked this pull request as ready for review April 12, 2024 06:39
@dngray
Copy link
Member

dngray commented Apr 12, 2024

Now that we have proper translations, there is less reason for the whole ND restriction. Anyone plagiarizing the site and cloning it entirely will be punished by the various duplicate content algorithms which search engines have. This encourages things to stay on the main site. Also in the past that restriction was because clones of the website appeared in other languages and were all hugely out of date with source material but still used the source material's logo as an endorsement.

A BY-SA license is more like a GPL license, in that content based off it still has to be available under the license that we provide it under and not more restrictive, so this is also a good thing.

jonaharagon added a commit that referenced this pull request Apr 12, 2024
jonaharagon added a commit that referenced this pull request Apr 15, 2024
Signed-off-by: Daniel Gray <dngray@privacyguides.org>
Signed-off-by: Freddy <freddy@privacyguides.org>
Signed-off-by: Niek de Wilde <niek@privacyguides.org>
Signed-off-by: Olivia <47239784+hook9@users.noreply.github.com>
@jonaharagon jonaharagon merged commit 7346c4d into main Apr 15, 2024
19 checks passed
@jonaharagon jonaharagon deleted the jonaharagon/relicense-site branch April 15, 2024 18:14
@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/2024-04-16/17905/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
m:contributing relating to contributing/community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants