This might be a bit of a long and windy road type post, so bare with me as I try to work my way through this topic. If you are impatient, skip the intro and jump into the meat of it.
Go back 4 years and I wrote a post called “Cocktails on the Titanic” based on a couple of talks I had given about future business models within the geo space. I said
“Open Source software is increasingly recognised as a cost effective alternative to proprietary software, particularly for web mapping applications where the functionality is quite well established and becoming commoditised through open standards interfaces. Open Source is not free but it is potentially a very cost effective alternative to traditional license models, particularly if hosted in the cloud”
That post prompted some quite robust comments from a couple of friends particular about the apparent deception that open source is free (their views not mine) when of course it is not. Things have moved on and I have participated in dozens of sales engagements where the value proposition for open source based solutions has won out against proprietary software models with a combination of performance, features, flexibility, scalability and of course lower cost of ownership (no it is not free). There really aren’t many occasions when you need to defend or justify the use of open source, it’s rarely a factor in the decision making process. In public sector where I spend a lot of my time open source (and open standards) is actually the preferred approach if you follow the government’s ICT Strategy.
A couple of years ago I got into a discussion about the ‘Free’ in FOSS4G (that’s Free and Open Source Software for Geo) which lead to a post titled “Get the eff out of FOSS4G” which worked through thoughts on “Free as in speech not beer” and “Freedom to ..”. I still think that ‘Free’ is a problem for the open source community because I think it encourages a misunderstanding of the open source business model and the ecosphere that creates and supports open source software. At FOSS4G in Nottingham last year I was blown away by our final keynote from Paul Ramsey entitled “Being an Open Source Citizen”, if you are interested in how the open source ecosphere works this is a great presentation (re-presented and recorded after FOSS4G) so get yourself a coffee or a beer (depending on the time of day), sit back and listen to Paul for 20 minutes.
You’re back? Enjoy that? Remember what Paul said? This is a win-win ecosphere.
“It’s all about me”
Open source isn’t solely an altruistic movement of volunteers, it has a business model that supports thousands of developers and service delivery people around the world. It’s a win-win model, win for the user or customer, win for the developers of the projects and win for the people who deliver services and help to make it all happen.
“You get what you pay for, everyone gets what you pay for, you get what everyone pays for”
This sums up the community element of the open source ecosphere and also how user organisations can influence future developments by sponsoring features which everyone else will benefit from
“Using is not the same as supporting, an organisation supports open source with time or money”
If you have been wondering where this post was going, stop wondering, we’ve got there – this is the important bit. If your organisation (or you as an individual) get benefit from open source software how are you going to contribute and support the community that creates and maintains that software? Or don’t you think about it? I suspect many organisations that make use of open source software are supportive of the idea but somehow neglect or don’t know how to support the projects that deliver benefits and savings to their businesses.
So I thought “wouldn’t it be a good idea to have a User Charter or Guide to Best practice for Users?” I asked on the OSGeo lists if anyone knew of something that user organisations could be pointed at, and I drew a blank, so what follows is my first shot at a draft of ‘Good practice for organisations using OSGeo software” Since this is a personal project that hasn’t been endorsed or supported by the OSGeo community I have posted it here to kick the discussion off and hopefully people will suggest improvements to a point where possibly the OSGeo community adopts it and we move it to the OSGeo wiki.
Good practice for organisations using OSGeo software
If your organisation has decided to make use of OSGeo open source geospatial software you will already appreciate the product capabilities, flexibility, support for open standards and cost savings that open source software delivers but have you considered how your organisation can contribute to the community that builds and supports the software that you are using? The open source ecosphere of companies, individual developers and volunteers needs to be fed, supported and encouraged, if your organisation benefits from using open source software then here are a few ways that you can put something back and keep those developers and businesses creating the software that you use.
It’s called sustainability, it won’t work if you rely on someone else doing it.
How much should we be contributing?
When you made the decision to use open source software you probably identified potential financial benefits from savings on licensing, implementation and ongoing support costs. How about setting a small percentage of those savings as a target for contributions back to the community that supports your organisation? 10% of your savings (calculated on the most cautious basis you wish) would be great but if that is too much set a percentage that you are comfortable with. [I can imagine this suggestion prompting some controversy but I think we need a starting point]
Your contribution could be a cash contribution or it could be volunteering your staff time to one of the projects or a combination of both.
Here are a few ways to contribute financially to the OSGeo projects and community:
Make a donation to an OSGeo project, they are all linked to from the OSGeo home page
- Sponsor a feature that your organisation needs – remember “You get what you pay for, everyone gets what you pay for, you get what everyone pays for”
- Sponsor the OSGeo Foundation (there’s a button on the web site) and let them work out how to use your donation
- Sponsor an OSGeo event. FOSS4G’s whether they are the big international event or smaller regional and national events all rely on sponsorship to make attendance affordable for developers, volunteers and students
- Sponsor your local OSGeo chapter
A community needs more than hard cash (a;though that is very useful) it needs participants and contributors.
Do you have the technical skills in house to make contributions to the codebase of one of the projects? If so why not allow your staff to get involved during working time or even to be seconded to a project to gel develop some capabilities that you need. If you don’t have the skills in house to write code, could you offer some of your staff time and skills to help with documentation and translation or work on a publicity group or conference organising team? There are loads of ways to get involved that don’t require code skills. You will almost certainly find that there are fringe benefits in terms of skills development and staff engagement from encouraging your staff to get involved with OSGeo.
Keep a record of the time that your staff contribute to OSGeo and tally it against your ‘10% of savings’ target but do use a fair rate to value your staff time.
It costs nothing to give a little bit of acknowledgement to the open source projects and community that are supporting your organisation, here are a couple of suggestions:
- If you have a web map or spatial data output on your web site you could could include some form of acknowledgement of the projects that helped you to deliver the project. If there are several projects that you have used you could link to a page on your site that details the open source technologies that your organisation uses (not just the geospatial ones) or you could link to the OSGeo web page
- Publish an annual open source usage report. Set out your organisation’s open source policy, take time to audit your usage of open source and the benefits and savings that it has delivered, acknowledge the projects that you have used and list the contributions, financial and time, that you have made in the past year.
Once you have done that, why not commit yourself to reaching out to other potential users to share your experiences through case studies and by speaking at events?
If your organisation uses a services company to implement, customise or support open source software then you might want to ask what they are doing to contribute to the open source ecosphere?
- Do they donate a percentage of their revenues to sponsor open source projects or the OSGeo Foundation?
- Do they contribute code to any of the projects?
- Do they sponsor functionality which everyone benefits from?
- Do they support their staff in volunteering within projects, events and groups?
In other words, are the consultants that you are using to implement open source solutions following this ‘Good practice’?
I am sure there are other ways of contributing to the open source community that I have missed off this short list, use the comments below to offer your suggestions.
Let me know if you think that this good practice guide would be useful or if it’s a waste of time.
The end of free lunches
Hopefully this first stab at a good practice guide for users will help to convince users of open source software to contribute time and money to the community that creates and supports the open source software that they benefit from. Don’t leave it to someone else to fund that feature you need or to fix a bug, step up and contribute.