Skip to main content

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?


This is a canonical question. New questions asking effectively the same thing as this question may be closed as a duplicate of it.

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?


This is a canonical question. New questions asking effectively the same thing as this question may be closed as a duplicate of it.

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?


This is a canonical question. New questions asking effectively the same thing as this question may be closed as a duplicate of it.

added 204 characters in body
Source Link
MadHatter
  • 53k
  • 5
  • 133
  • 185

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?


This is a canonical question. New questions asking effectively the same thing as this question may be closed as a duplicate of it.

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?


This is a canonical question. New questions asking effectively the same thing as this question may be closed as a duplicate of it.

fix link to mail archives
Source Link
Mureinik
  • 5.2k
  • 3
  • 33
  • 42

Bruce Perens (co-founder of OSI) has coined the term "crayon licensecrayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?

Bruce Perens (co-founder of OSI) has coined the term "crayon license":

I've been calling these "crayon licenses", taking a line from an old Monty Python sketch about a dog license with the word "dog" crossed out and "cat" written in, in crayon.

The licenses referenced are typical well-intended free software licenses that have been written by programmers in simple, easy-to-understand, non-legalese language. Some typical examples are the WTFPL and the somewhat more elaborate Artistic License 1.0.

Perens seems to imply that such licenses may pose a problem for developers using them, or for the open source community.

How can these licenses be a problem?

Or is Perens wrong about them being a problem?

Notice removed Reward existing answer by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Reward existing answer by Zizouz212
Bounty Started worth 100 reputation by Zizouz212
edited tags
Link
ArtOfCode
  • 9.6k
  • 2
  • 30
  • 71
Loading
added 2 characters in body
Source Link
ArtOfCode
  • 9.6k
  • 2
  • 30
  • 71
Loading
Source Link
Free Radical
  • 9.2k
  • 3
  • 31
  • 62
Loading