privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

Create WARRANTY #919

Closed
asddsaz wants to merge 3 commits from patch-28 into master
pull from: patch-28
merge into: privacyguides:master
Conversation 11 Commits 3 Files Changed 1 +5
asddsaz commented 2019-05-10 02:42:33 +00:00 (Migrated from github.com)
Copy Link

Add WARRANTY.txt

As listed here: http://www.wtfpl.net/faq/

Add WARRANTY.txt As listed here: http://www.wtfpl.net/faq/
privacytoolsIO (Migrated from github.com) reviewed 2019-05-10 02:42:33 +00:00
jonah reviewed 2019-05-10 02:42:33 +00:00
netlify[bot] commented 2019-05-10 02:43:07 +00:00 (Migrated from github.com)
Copy Link

Deploy preview for privacytools-io ready!

Built with commit f0ade75ef9

https://deploy-preview-919--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit f0ade75ef9723dd4ca388babed56da88cc4b9b52 https://deploy-preview-919--privacytools-io.netlify.com
ghost commented 2019-05-10 13:43:03 +00:00 (Migrated from github.com)
Copy Link

Warranty notice is usually included in the license text.

Warranty notice is usually included in the license text.
jonah commented 2019-05-10 15:14:37 +00:00
Copy Link

I'm not sure if this is necessary since this is documentation, not source code? Nobody is "running" this on their own machines.

I'd rather see a license change to CC0 if anything.

I'm not sure if this is necessary since this is documentation, not source code? Nobody is "running" this on their own machines. I'd rather see a license change to CC0 if anything.
👍 1 ❤️ 3
Mikaela commented 2019-05-15 08:21:32 +00:00 (Migrated from github.com)
Copy Link

I'd rather see a license change to CC0 if anything.

WTFPL is compatible and would let us perform relicensing to CC0, wouldn't it?

> I'd rather see a license change to CC0 if anything. WTFPL is compatible and would let us perform relicensing to CC0, wouldn't it?
asddsaz commented 2019-05-16 00:38:09 +00:00 (Migrated from github.com)
Copy Link

@Shifterovich It shouldn't matter where you put the warranty.

@Shifterovich It shouldn't matter where you put the warranty.
ghost commented 2019-05-18 11:16:07 +00:00 (Migrated from github.com)
Copy Link

It shouldn't matter where you put the warranty.

So if it's in the license, why open this PR?

> It shouldn't matter where you put the warranty. So if it's in the license, why open this PR?
jonah commented 2019-05-18 15:07:56 +00:00
Copy Link

@Mikaela it is possible but I don’t know if something like #884 would cause us any issues.

@Shifterovich I don’t think it is in the WTFPL is it? The license is pretty bare.

@Mikaela it is possible but I don’t know if something like #884 would cause us any issues. @Shifterovich I don’t think it is in the WTFPL is it? The license is pretty bare.
ghost commented 2019-05-18 15:13:25 +00:00 (Migrated from github.com)
Copy Link

WTFPL is a shitty license. We should use an actual license like MIT or preferably CC0.

WTFPL is a shitty license. We should use an actual license like MIT or preferably CC0.
👍 1
gjhklfdsa commented 2019-05-29 20:43:24 +00:00 (Migrated from github.com)
Copy Link

@Shifterovich As I understand it, warranty can be put anywhere in a source code file and still be valid.

@Shifterovich As I understand it, warranty can be put anywhere in a source code file and still be valid.
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
jonah
privacytoolsIO
Labels
Clear labels
:mag:🤖 Search Engines
approved
approved, waiting for a PR
 dependencies
Pull requests that update a dependency file
 duplicate
feedback wanted
high priority
I2P
The Invisible Internet Project (I2P)
 iOS
low priority
OS
Operating Systems
 Self-contained networks
Social media
stale
A label for stalebot if it gets added
 streaming
Anything related to media streaming.
 todo
Tor
Anything covering the Tor network
 WIP
active work in progress, do not merge or PR (yet)!
 wontfix
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
 XMPP
Extensible Messaging and Presence Protocol
 [m]
Matrix protocol
 ₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
Browser Extension related issues
 ✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
Correction of content on the website
 🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
Firefox & forks, about:config etc.
 💻 hardware
🌐 hosting
🏠 housekeeping
Anything primarily related to site cleanup.
 🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
Virtual Private Network
 🌐 website issue
*Technical* issues with the website.
 🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
Domain Name System
 🗨️ instant messaging (im)
🇦🇶 translations
Anything covering a translated version of the site
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
jonah
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#919
Delete Branch "patch-28"

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?