Does open source need its own Priority of Constituencies?
Tobie Langel (@tobie) Principal, UnlockOpen
Slide 1
Slide 2
Slide 3
Slide 4
Slide 5
Slide 6
Slide 7
Slide 8
Slide 9
Open source crisis
- Maintainer burnt out.
- Cloud capturing too much value.
- Ethical concerns over impact on end-users.
Slide 10
What’s going on? We’re witnessing the emergence of new constituencies.
Slide 11
The 4 freedoms & the OSD
Slide 12
The 4 freedoms & the OSD
Slide 13
How do we handle this increased diversity of constituencies?
Slide 14
W3C’s Priority of Constituencies
Slide 15
Slide 16
Slide 17
Slide 18
Slide 19
W3C priority of constituencies
End users > Authors > Implementors > Spec editors > Theoretical purity
Slide 20
Size of each constituency
Slide 21
Cost of 1 hour of spec work
Slide 22
Apache Software Foundation mantra
Slide 23
Apache Software Foundation mantra
Slide 24
Apache Software Foundation mantra
End users > Theoretical purity
Slide 25
Apache Software Foundation mantra
People > Code
Slide 26
What would an open source priority of constituencies look like?
Slide 27
Open source priority of constituencies
Slide 28
Open source priority of constituencies
People > End users > App devs > Cloud infra > Contributors > Maintainers > Theor. pur.
Slide 29
But is W3C’s priority of constituencies a silver bullet?
Slide 30
Economic situation
Slide 31
Economic situation
Slide 32
Economic situation
Slide 33
Economic situation
Slide 34
Slide 35
Let’s apply this to open source.
Slide 36
The canary in the coal mine
Slide 37
Open source priority of constituencies
People > End users > App devs > Cloud infra > Contributors > Maintainers > Theor. pur. `
Slide 38
Open source priority of constituencies
Slide 39
Open source priority of constituencies
Slide 40
Open source priority of constituencies
Slide 41
Benefits of a priority of constituencies
- Keeps focus on people & downstream impact.
- Maximizes benefits to the commons by upstreaming work.
- Surfaces discrepancies between economic situation and work expectations.
