Skip to content

Commit 00dda85

Browse files
bastbast
committed
mv the cake example to own slide deck
1 parent 3e0a71c commit 00dda85

File tree

2 files changed

+147
-122
lines changed

2 files changed

+147
-122
lines changed

‎licensing-and-cakes.md

+147
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
1+
class: center, middle
2+
3+
# Software licensing and open source explained with cakes
4+
5+
---
6+
7+
<img src="img/cake-1.svg" style="width: 15%;"/>
8+
9+
- Imagine you compose a recipe for a really tasty cake (a great idea).
10+
- In regular intervals you distribute cakes (release binaries).
11+
- Your family and friends love it.
12+
- But you can only bake so many.
13+
14+
(cake emoji licensed under CC-BY-SA-4.0, attribution: [EmojiOne](https://www.emojione.com))
15+
16+
<!--- Perhaps may be worth saying that this is a metaphor - the
17+
ingredients list and basic instructions simply facts, so not
18+
protectable. However, your description *is* protectable. -->
19+
20+
---
21+
22+
## Possible outcomes 0/4: closed
23+
24+
### Closed source (recipe never released)
25+
26+
- Your cake is celebrated by The New Yorker magazine.
27+
- People will have difficulties to reproduce your celebrated recipe.
28+
- Nobody else will improve your recipe.
29+
- Bad copycats might appear, you don't get any credit.
30+
- Fewer tasty cakes will get consumed.
31+
32+
---
33+
34+
## A friend tells you: why not distribute the recipe?
35+
36+
- Put your recipe on GitHub.
37+
- Start the OpenCake organization.
38+
- Get feedback / start a mailing list.
39+
- More people will be able to enjoy the cake (.emph[increase impact]).
40+
- Maybe somebody will find ways to improve the recipe.
41+
- Everyone will know that it was your idea even though somebody else bakes it.
42+
43+
---
44+
45+
## Mrs. X (running a famous restaurant) finds your cake recipe on GitHub
46+
47+
<img src="img/cake-1.svg" style="width: 15%;"/>
48+
49+
- The chef tries it and it is great.
50+
- The chef suggests improvements (derivative work):
51+
52+
<img src="img/cake-2.svg" style="width: 15%;"/>
53+
54+
- It becomes part of the restaurant menu.
55+
- Or does it? .emph[Depends on your license!]
56+
57+
<!--- What is most important is *how are the changes handled*. Since
58+
you are giving the recipe out yourself, people can use it "personally"
59+
however they want. But if they want to improve/reuse/redistribute it,
60+
then what? -->
61+
62+
---
63+
64+
## Possible outcomes 1/4: custom
65+
66+
### No license or custom license
67+
68+
- No restaurant chef will touch it: too much hassle to employ a lawyer to be sure
69+
that the cake can be served to customers.
70+
- But maybe they will bake it and eat it and not distribute it and that is OK
71+
("fair use" provision permits the making of copies for own use).
72+
73+
<!--- The restaurant industry is infamous for copying recipes and there are
74+
very few published court cases. Let's skim over this fact and stay in the
75+
fictitious example though. -->
76+
77+
---
78+
79+
## Possible outcomes 2/4: permissive
80+
81+
### License: MIT or Apache or BSD-2
82+
83+
- It is OK to use the recipe and sell the cake.
84+
- It is OK to not share the improved recipe.
85+
- If somebody becomes sick, it is not the fault of the OpenCake organization (limit of liability).
86+
- You may not get the improvements back to use yourself.
87+
88+
### License: BSD-3
89+
90+
- In addition to the above it is understood that the updated recipe are not endorsed by the OpenCake organization.
91+
92+
---
93+
94+
## Possible outcomes 3/4: share-alike
95+
96+
### License: GNU Lesser GPL (LGPL)
97+
98+
- The famous restaurant has to share only the improved cake recipe but can keep the rest of the menu closed.
99+
- The restaurant guests have to be able to exchange the cake from the menu by improved cakes from other restaurants (dynamic relinking).
100+
101+
### License: Mozilla Public License v2.0
102+
103+
- Like LGPL but do not require that the modified cake can be exchanged by the restaurant guest.
104+
105+
---
106+
107+
## Possible outcomes 4/4: viral
108+
109+
### License: GNU GPL or GNU Affero GPL
110+
111+
- If the cake is a part of the menu, the famous restaurant has to
112+
.emph[share the recipes of the entire menu].
113+
- You can use their improved recipe and improve it further:
114+
115+
<img src="img/cake-2.svg" style="width: 15%;"/>
116+
<img src="img/cake-3.svg" style="width: 15%;"/>
117+
118+
- Other restaurants can then reuse and improve the full menu and the hope is that we will all eat better food.
119+
- You support open restaurants. You can use everything they do, too.
120+
121+
<!--- Example of benefits of virality in software: Linksys routers and
122+
GPL's kernel image. Some company used linux, didn't distribute source.
123+
They were fourced to distribute it, and that has directly led to
124+
a huge community of firmware modders. -->
125+
126+
---
127+
128+
## What outcomes did we have?
129+
130+
### 1. Custom/closed
131+
132+
- **Derivative work typically not possible**: others have to reimplement the wheel
133+
134+
### 2. Permissive
135+
136+
- You may lose access to **derivative work**
137+
- Attractive for companies with proprietary software
138+
139+
### 3. Share-alike
140+
141+
- You can reuse **derivative work**
142+
- Compatible with proprietary software
143+
144+
### 4. Viral
145+
146+
- .emph[You always have access if someone improves and re-shares]
147+
- Not attractive for companies with proprietary software

‎talk.md

-122
Original file line numberDiff line numberDiff line change
@@ -426,128 +426,6 @@ make an impact.
426426
- Code without license is not useful for reuse or derivative work.
427427
- Example why choice of license matters, X vs. SunView: https://lwn.net/Articles/26608/
428428

429-
430-
## Software licensing and open source explained with cakes
431-
432-
<img src="img/cake-1.svg" style="width: 15%;"/>
433-
434-
- Imagine you compose a recipe for a really tasty cake (a great idea).
435-
- In regular intervals you distribute cakes (release binaries).
436-
- Your family and friends love it.
437-
- But you can only bake so many.
438-
439-
(cake emoji licensed under CC-BY-SA-4.0, attribution: [EmojiOne](https://www.emojione.com))
440-
441-
<!--- Perhaps may be worth saying that this is a metaphor - the
442-
ingredients list and basic instructions simply facts, so not
443-
protectable. However, your description *is* protectable. -->
444-
445-
---
446-
447-
## Possible outcomes 0/4: closed
448-
449-
### Closed source (recipe never released)
450-
451-
- Your cake is celebrated by The New Yorker magazine.
452-
- People will have difficulties to reproduce your celebrated recipe.
453-
- Nobody else will improve your recipe.
454-
- Bad copycats might appear, you don't get any credit.
455-
- Fewer tasty cakes will get consumed.
456-
457-
---
458-
459-
## A friend tells you: why not distribute the recipe?
460-
461-
- Put your recipe on GitHub.
462-
- Start the OpenCake organization.
463-
- Get feedback / start a mailing list.
464-
- More people will be able to enjoy the cake (.emph[increase impact]).
465-
- Maybe somebody will find ways to improve the recipe.
466-
- Everyone will know that it was your idea even though somebody else bakes it.
467-
468-
---
469-
470-
## Mrs. X (running a famous restaurant) finds your cake recipe on GitHub
471-
472-
<img src="img/cake-1.svg" style="width: 15%;"/>
473-
474-
- The chef tries it and it is great.
475-
- The chef suggests improvements (derivative work):
476-
477-
<img src="img/cake-2.svg" style="width: 15%;"/>
478-
479-
- It becomes part of the restaurant menu.
480-
- Or does it? .emph[Depends on your license!]
481-
482-
<!--- What is most important is *how are the changes handled*. Since
483-
you are giving the recipe out yourself, people can use it "personally"
484-
however they want. But if they want to improve/reuse/redistribute it,
485-
then what? -->
486-
487-
---
488-
489-
## Possible outcomes 1/4: custom
490-
491-
### No license or custom license
492-
493-
- No restaurant chef will touch it: too much hassle to employ a lawyer to be sure
494-
that the cake can be served to customers.
495-
- But maybe they will bake it and eat it and not distribute it and that is OK
496-
("fair use" provision permits the making of copies for own use).
497-
498-
<!--- The restaurant industry is infamous for copying recipes and there are
499-
very few published court cases. Let's skim over this fact and stay in the
500-
fictitious example though. -->
501-
502-
---
503-
504-
## Possible outcomes 2/4: permissive
505-
506-
### License: MIT or Apache or BSD-2
507-
508-
- It is OK to use the recipe and sell the cake.
509-
- It is OK to not share the improved recipe.
510-
- If somebody becomes sick, it is not the fault of the OpenCake organization (limit of liability).
511-
- You may not get the improvements back to use yourself.
512-
513-
### License: BSD-3
514-
515-
- In addition to the above it is understood that the updated recipe are not endorsed by the OpenCake organization.
516-
517-
---
518-
519-
## Possible outcomes 3/4: share-alike
520-
521-
### License: GNU Lesser GPL (LGPL)
522-
523-
- The famous restaurant has to share only the improved cake recipe but can keep the rest of the menu closed.
524-
- The restaurant guests have to be able to exchange the cake from the menu by improved cakes from other restaurants (dynamic relinking).
525-
526-
### License: Mozilla Public License v2.0
527-
528-
- Like LGPL but do not require that the modified cake can be exchanged by the restaurant guest.
529-
530-
---
531-
532-
## Possible outcomes 4/4: viral
533-
534-
### License: GNU GPL or GNU Affero GPL
535-
536-
- If the cake is a part of the menu, the famous restaurant has to
537-
.emph[share the recipes of the entire menu].
538-
- You can use their improved recipe and improve it further:
539-
540-
<img src="img/cake-2.svg" style="width: 15%;"/>
541-
<img src="img/cake-3.svg" style="width: 15%;"/>
542-
543-
- Other restaurants can then reuse and improve the full menu and the hope is that we will all eat better food.
544-
- You support open restaurants. You can use everything they do, too.
545-
546-
<!--- Example of benefits of virality in software: Linksys routers and
547-
GPL's kernel image. Some company used linux, didn't distribute source.
548-
They were fourced to distribute it, and that has directly led to
549-
a huge community of firmware modders. -->
550-
551429
---
552430

553431
## What outcomes did we have?

0 commit comments

Comments
 (0)