Create WARRANTY #919

Closed
asddsaz wants to merge 3 commits from patch-28 into master
asddsaz commented 2019-05-10 02:42:33 +00:00 (Migrated from github.com)

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)

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)

Warranty notice is usually included in the license text.

Warranty notice is usually included in the license text.

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.
Mikaela commented 2019-05-15 08:21:32 +00:00 (Migrated from github.com)

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)

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

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?

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

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.
gjhklfdsa commented 2019-05-29 20:43:24 +00:00 (Migrated from github.com)

@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.
No reviewers
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#919
No description provided.