Keynote slides used at OSGeo.nl Day June 28, 2012 in Velp, The Netherlands. See also www.osgeo.nl. Shows models of doing business with Open Source using a value chain. Also introduces OSGeo, OSGeo.nl.
How to get rich and save the world with Open Source - Keynote OSGeo.nl Day
1. How to get Rich
and
Save The Planet
with
Open Source
Just van den Broecke - OSGeo.nl Day - Velp (NL)
just@justobjects.nl - June 28, 2012
1
Good morning ! Yesss, our own very first OSGeo.nl Day has started! I hope you will enjoy it. This keynote is in English as we have
international guests for this plenary. (Excuse me for my American accent but I worked a long time for a US company. Just in case
you were thinking I wanted to sound as a businessman)
2. Sponsor
2
Again a word of thanks to our sponsor WebMapper.
3. About Me
Independent Open Source
Geospatial Professional
www.justobjects.nl
3
My name is Just van den Broecke. My daily work is being hired as a consultant/architect/developer in various open source
geospatial projects (like PDOK). I try to combine this with developing Open Source software myself. You can checkout some stuff
via my website.
(BTW and I am not rich as some suggested. Ok, richness is a relative measure plus there are various forms of richness.)
I also will often use the term Free and Open Source for Geospatial (FOSS4G).
4. Member of the
OpenGeoGroep (NL)
www.opengeogroep.nl
About Me
4
With the OGG we have a group of companies doing support/development services for FOSS4G.
5. Trailblazer “kwartiermaker”
for the
OSGeo Dutch Language Local
Chapter
About Me
5
But my role here today is as I call it trailblazer for OSGeo.nl the Dutch Chapter of OSGeo. I will tell you more about OSGeo and
OSgeo.nl later.
7. 7
I combine hobby and work, actually this how I entered the geospatial domain initially: recording tracks with GPS and upload
them with pictures and videos to
8. 8
my favorite pet-project GeoRambling but also to OpenStreetMap. So there is our conference neighborhood. If you have a chance:
explore it! (Also I wanted to show at least one map; this is a GIS conference after all).
13. 13
During that hike I was pondering about a subject for this keynote. I should say that my friends are not in IT.
But now and then I try to explain them my work in FOSS. Usually I talk about the technical stuff I know: maps, GPS, coordinates
etc. I always remain vague and fuzzy about the business side of FOSS in general. So what sticks with them is that we in
FOSS...
14. Create Software
&
Give Away for Free
14
This is what they don’t get. They see that billions can be earned and they tease me with this.
16. 16
Or even this guy (some of my friends got rich from stocks).
17. 17
and since I’m an Apple user off course this guy. May he rest in peace.
18. From: Paul Ramsey - FOSS4G Keynote 2009
http://blog.cleverelephant.ca/2009/10/foss4g-2009-keynote.html
18
I guess those of you in Open Source had to explain this to family, friends and colleagues. Paul Ramsey raises and answers that
question in a very entertaining and deep way during his Keynote. I will not repeat what Paul has said, since he does this far far
better than me. Paul is from OSGeo btw. I recommend watching his keynote..
So since I am mostly giving technical talks I wanted to force myself this time to talk about open source and money/business. If
only to understand & expand my own activities. I wanted to explore if there is some kind of overall framework/structure that
could possibly inspire also you to enter new niches in the FOSS4G market.
19. How to get Rich
and
Save The Planet
with
Open Source
19
So I challenged myself by raising the bar a bit and also do some good for the planet at the same time.
So today I would like to share with you what I found out. So sit back and relax.
(If the talk would have been called “Business Models in Open Source” it would not raise this crowd I guess).
20. How to Earn Money
with
Open Source
20
Before we get rich we at least need to start with earning money...
21. Open Source
is not a
Business Model
21
I used to say : “I do Open Source”. But without even putting a reference here, we all know that Open Source is a development
model and not a business model. Hmm.
22. “Ideals and Concepts by
itself will not sell a
Product”
http://worldisgreen.com/2008/10/17/open-source-and-sustainability-what-do-they-have-in-common/
22
This is painfully true...from the ref: ”Customers do not buy products/services for their ideals but for the value they provide to their business.”
23. Open Source
Business Tactics
23
But there are off course multiple what one could call “Business Tactics” around Open Source.
24. http://www.cascadoss.eu
24
I remembered having this report still on my computer. Read through it once quickly but what stuck was that it presented a visual
framework that was easy to understand for tech-nerds like me. Here’s the reference, you can download it as a PDF from the net.
25. The Architecture
of
Value Creation
From: CASCADOSS Del. 1.5 KULeuven
25
Aha architecture, this is something I can relate to as a developer.
26. Value-Chain
The steps that turn inputs
into value-added output
From: CASCADOSS Del. 1.5 KULeuven
26
Yes! Transforming input into output, that is what programming is also about.
27. Software Value-Chain
CASCADOSS:
Model of Berlecon Research (2002)
www.berlecon.de/studien/downloads/200207FLOSS_Basics.pdf From: CASCADOSS Del. 1.5 KULeuven
27
The SVC was taken from an earlier study from Berlecon als available on the net. But I will lead you through the essentials.
28. Software Value Chain
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
29. Software Value Chain
Development
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
30. Software Value Chain
Development Documentation
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
31. Software Value Chain
Development Documentation Packaging
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
32. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
33. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Consulting
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
34. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Consulting Integration
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
35. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Consulting Integration Training
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
36. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Consulting Integration Training Support
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
37. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
28
Each step adds value. Note: I am not talking about value in terms of money, just value, for example for a customer.
“The steps in this value-chain are:
-Software development: analysis, design, programming and testing of the software.
-Documentation: writing documentation (API documentation, Reference Manual, User Guides, Tutorials, Howto's, FAQs, ...)
-Software packaging: creating a user-friendly package of the software; bundling the software with other packages.
-Marketing/sales: marketing the software, closing sales, promoting wide-spread adoption, distribution.
-Consulting: providing consultancy with respect to the software.
-Integration/custom development: Integrating the software in the client's systems,
customizing it for user-specific needs
-Training: training in the use or customization of the software
-Support: end-user support (telephone, e-mail), installation and update support, bug fixing
-Application management: operational management of the client's applications based on the software.”
This chain is really no different than a value-chain for proprietary software. “Revenue-generating activities in the value chain such as
training, support and consultancy remain unaffected.” No business model yet here. Business models/tactics are basically one or more
slices where you want to intercept in this chain. Let’s look at a few of them.
38. Model 1: Dual-Licensing
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
29
We start easy: The Dual Licensing Model.
“In the dual-licensing model, the software product is available under two different licenses:
- a reciprocal open source license that obligates customers to release their own products also under the reciprocal license if they include the product as
part of their own software products.
- a commercial license that releases the user from his obligation to release under a reciprocal license.
In short: either the customer reciprocates by contributing to the software commons or he pays the developers.”
39. Model 1: Dual-Licensing
?
From: CASCADOSS Del. 1.5 KULeuven
30
So where’s the money earned here?
40. Model 1: Dual-Licensing
Licensing Fees
for
Commercial Licenses
From: CASCADOSS Del. 1.5 KULeuven
31
Simple: in license fees. (It is up to you for any judgement.)
41. Model 1: Dual-Licensing
ExtJS - JavaScript Lib
From: CASCADOSS Del. 1.5 KULeuven
32
Here’s some products that do Dual Licensing. MySQL is probably the best known. ExtJS/Sencha is a (powerful) GUI component
used in various webclients like the GeoExt JavaScript client. ExtJS is also used in the new Flamingo webclient presented next.
42. Model 2: Support Seller
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
33
“In this model the company that creates a F/OSS product offers support services to users of the product. The model is based on the premiss that the creators of a
software are the best suited to provide support because they are the creators.”
44. Model 2: Support Seller
Support Packages:
SLAs
Fixed Price Support
Subscription
From: CASCADOSS Del. 1.5 KULeuven
35
“Standardized support packages are offered as an SLA or support subscription for a fixed price on a (typically) yearly basis. This last model is the most important”
45. Model 2: Support Seller
From: CASCADOSS Del. 1.5 KULeuven
36
Could be also a third-party, i.e. not the company that is the creator of the FOSS product.
46. Model 3: Platform Provider
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
37
“The company bundles several F/OSS products into a complete solution or platform. The company provides quality-assurances that
the selected products work together. ...This model is usually combined with the (Third-Party) Support Seller Model. First, because it is
far easier to support and bug-fix a complete solution (platform) as it implies greater control over the operating environment. Secondly,
the value proposition is enhanced for the customer if he can source the platform and related support services for the same supplier.”
48. Model 3: Platform Provider
License Fee
usually combined with
Support Seller
From: CASCADOSS Del. 1.5 KULeuven
39
“Usually a license fee. However, the business model is mostly combined with a support seller model. In that case, the license fee will cover access to support
services together with the bundled product.”
50. Model 4: Consulting
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
41
“The company provides consulting and customization services with respect to a range of F/OSS products. This model is certainly the most widely adopted model.”
52. Model 4: Consulting
Consulting Services (p/hour)
Fixed Price Custom Development
From: CASCADOSS Del. 1.5 KULeuven
43
“Services are usually sold on a time & means basis. Custom developments are often contracted on a fixed price basis.”
53. Model 4: Consulting
From: CASCADOSS Del. 1.5 KULeuven
44
Many of you. Also means competition. This is good for customers. But you may also want to think to get into one of the other
models that may be more niche...
54. Model 5: Accessorizing
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
45
“The company sells physical accessories to F/OSS products. Most important of these are technical books and
manuals.”
58. Model 6: Software-as-a-Service
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
49
“In this model F/OSS is used to create a web-accessible application service. Such systems are labeled ““Software as a
Service”” (SaaS).”
These days the buzz-word is “In The Cloud!”.
60. Model 6: Software-as-a-Service
Access and Usage Fees
From: CASCADOSS Del. 1.5 KULeuven
51
“Usually the customer pays a monthly fee for access to the application services.”
61. Model 6: Software-as-a-Service
From: CASCADOSS Del. 1.5 KULeuven
52
“The best known company that uses this model is undoubtedly Google. “. Not yet a lot Geospatial activity. Opportunities!!! I find this one interesting since
GIS is a lot about web-services and we have stable Open Source.
62. Software Value Chain
Marketing/
Development Documentation Packaging
Sales
Application
Consulting Integration Training Support Management
From: CASCADOSS Del. 1.5 KULeuven
53
So all, in all we have seen these various models intercepting this value chain. As the FOSS4G market is sort of a niche within a niche (GIS) there are
still opportunities here apart from the usual Consulting. The Platform Provider and SaaS are relatively unexplored in FOSS4G, so take that with you...
63. .....
and
Save The Planet
with
Open Source
54
So how are we in time ? 10 minutes left to save the planet ? Can do..
65. 56
we can donate to various charities. Don’t get me wrong here: I think that these guys are doing very good things here. It is only
that we ourselves need to find alternative ways since we’re not rich yet. Let’s see what we can do...
66. Open Source
&
Sustainability
“Duurzaamheid”
57
One thing that sort of stuck into my head is the relationship between: Sustainability and Open Source. In Dutch we call this
“Duurzaamheid”. There’s lots of talk about Sustainable production etc. I wanted to see if this Sustainability has been explored
for FOSS. By the way when we talk about “sustainable Open Source projects” we often mean: projects that can support (sustain)
themselves. This is not the sustainability as meant here.
67. “In the current financial
crisis facing the world,
both open source and
sustainability will make a
great combination...”
http://worldisgreen.com/2008/10/17/open-source-and-sustainability-what-do-they-have-in-common/
58
And here I found some beginnings, not a complete answer. Some of my thoughts here next...
68. Lake ecosystem: Source: Georgia Department of Natural Resources
59
Usually natural ecosystems are taken as a model for forms of sustainability. Like for example aquatic ecosystems. There’s a
tension between chaos and an equilibrium like entropy and energy.
69. Open Geospatial Ecosystems
Users Developers
Open Open
Processes Source
(OSGeo)
Lake ecosystem: Source: Georgia Department of Natural Resources
60
I like this idea of ecosystems in Open Source: Users, Developers, Software tied together to produce long-term ever-increasing
value that is greater than the sum of individuals and software components. Within FOSS4G the notion of Open Standards, Open
Data and Crowd Sourcing also tends to make these components even better integrated. OGC standards also raise competition in
performance/quality/features for similar products. Think of WMS shootouts...
70. Open Geospatial Ecosystems
Users Developers
Open
Standards
(OGC)
Open Open
Processes Source
(OSGeo)
Lake ecosystem: Source: Georgia Department of Natural Resources
60
I like this idea of ecosystems in Open Source: Users, Developers, Software tied together to produce long-term ever-increasing
value that is greater than the sum of individuals and software components. Within FOSS4G the notion of Open Standards, Open
Data and Crowd Sourcing also tends to make these components even better integrated. OGC standards also raise competition in
performance/quality/features for similar products. Think of WMS shootouts...
71. Open Geospatial Ecosystems
Users Developers
Open
Standards
(OGC)
Open Open
Processes Source
Open (OSGeo)
Data (OSM)
Lake ecosystem: Source: Georgia Department of Natural Resources
60
I like this idea of ecosystems in Open Source: Users, Developers, Software tied together to produce long-term ever-increasing
value that is greater than the sum of individuals and software components. Within FOSS4G the notion of Open Standards, Open
Data and Crowd Sourcing also tends to make these components even better integrated. OGC standards also raise competition in
performance/quality/features for similar products. Think of WMS shootouts...
72. Open Geospatial Ecosystems
Users Developers
Open
Standards
(OGC)
Crowd
Sourcing Open Open
Processes Source
Open (OSGeo)
Data (OSM)
Lake ecosystem: Source: Georgia Department of Natural Resources
60
I like this idea of ecosystems in Open Source: Users, Developers, Software tied together to produce long-term ever-increasing
value that is greater than the sum of individuals and software components. Within FOSS4G the notion of Open Standards, Open
Data and Crowd Sourcing also tends to make these components even better integrated. OGC standards also raise competition in
performance/quality/features for similar products. Think of WMS shootouts...
73. http://geotux.tuxfamily.org/index.php/en/geo-blogs/item/291-comparacion-clientes-web-v6
61
Even in the small you find ecosystems in open source. These are all geospatial mapping clients and their interrelations.
And just as in a realworld eco-system: species arise, dominate for some time and die off. Watch the now Leaflet island in the
next years....
74. Open Source Development Model
Primary Motivation
Solve Problem
Demand-Based
62
If we look at the OS development model we find that development is usually driven by demand pull: to solve a problem.
It is driven by requirements either from users or a personal “developer’s itch”.
What this means is is that...
75. Open Source Development Model
Produce
Just
Enough
63
The consequence is that this driving force tends to produce just enough, i.e. it is harder to produce excess. Though we have
still may have off course failing projects and products. And there’s competition (MapServer vs GeoServer vs deegree), this is on a
performance/quality/features’ level.
76. Open Source Development Model
Sharing
Code Sharing
Knowledge Sharing
64
FOSS comes down to knowledge sharing. Software is merely codified knowledge. Software builds on other software and evolves
from previous software. The phrase “Standing on the shoulders of Giants” applies. So how does this relate to sustainability ?
77. Open Source Development Model
Minimize Resources
by
Sharing
65
We minimize resources by sharing code and other knowledge around the code. This is a good thing! I think there is less waist.
Online open communities and development environments also tend to produce e.g. less paper and do less travel.
78. Stepping
Up
66
So when doing Open Source in my opinion we are already saving the planet just a little bit. But you can get a step further.
79. Humanitarian
Mapping
67
When exploring several geospatial projects related to disaster support I learned about humanitarian mapping. It appeared that
this was already existing longer than I thought.
80. The Booth Maps of London Poverty - 1889
http://www.locallocalhistory.co.uk/municipal-housing/wedmore/part1v1/
68
Already in 1889 Charles Booth mapped poverty levels of citizens within Londen by using a classification with colours. Very soon
a relationship between sanity and disease was derived from this.
81. 69
In the present day we have for example the Humanitarian OpenStreetMap Team. They help in cases where humanitarian
response is needed. The most striking example is Haiti. In 2010 just a few hours after the disaster mapping efforts began. Here
the power of both Open Source and Open Data plus an interconnected online community helped enormously in getting started
and productive.
82. 70
Another example is the Uhahidi project, also geared at mapping and crowd sourcing information in crisis situations.
http://en.wikipedia.org/wiki/Ushahidi “Ushahidi, Inc. is a non-profit software company that develops free and open source software (LGPL) for information
collection, visualization and interactive mapping. Ushahidi (Swahili for "testimony" or "witness") created a website (http://legacy.ushahidi.com) in the
aftermath of Kenya's disputed 2007 presidential election (see 2007–2008 Kenyan crisis) that collected eyewitness reports of violence sent in by
email and text-message and placed them on a Google map.[2] The organization uses the concept of crowdsourcing for social activism and public
accountability, serving as an initial model for what has been coined as 'activist mapping' - the combination of social activism, citizen journalism
and geospatial information. Ushahidi offers products that enable local observers to submit reports using their mobile phones or the internet, while
simultaneously creating a temporal and geospatial archive of events.”
83. How to get Rich
and
Save The Planet
with
Open Source
71
So I hope to have given you some pointers and that when doing Open Source you are already helping the world today...
84. Where
To
Start ?
72
But where to start: where do I find the right people, right geospatial software ? A place to exchange ideas ?
85. Join
73
The answer is simple: Join OSGeo.nl if you did not already.
86. Open Source Geospatial Foundation
www.osgeo.org
Your Open Source Compass
...organizes geospatial IT
74
But first I have to explain what OSGeo, the worldwide organization, is.
100. The DreamTeam
Marketing
Coach
Coach
Keynote
Technical Business & Application
88
OSGeo Open Source Seminar - Geospatial World Forum - 25 April 2012 - Amsterdam
88
101. For Whom
Developers
Users
Students
Governments
Industry
Aim: Rich Mixture
89
103. And
my
Friends ?
91
So what about my friends ? At least I think I found a more structured answer. And did I get rich ? Well maybe I did not want to
get rich that badly.
104. 92
At least my friends are happy since they know I am earning enough money to buy them a beer!