Relicense under CC0 #940
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#940
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "cc0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Releasing our work into the public domain seems like the correct path. WTFPL currently grants users an unlimited license to use our work, which is maybe fine, but CC0 actually revokes all copyright wherever possible, and falls back to an unlimited license where that's legally not a possibility. CC0 also includes a warranty disclaimer (so this merge Closes #919).
Under the terms of WTFPL we're able to relicense this site however we see fit so there should be no issues converting to CC0.
Deploy preview for privacytools-io ready!
Built with commit
e28dc35e26
https://deploy-preview-940--privacytools-io.netlify.com
Why wasn't this discussed more among the community?