Currently my domain lifefeed.com points here as well as others. I have way too many domains so am currently going to be putting lifefeed.com up for auction.
Click here for details.
Making a dent – somewhere
Currently my domain lifefeed.com points here as well as others. I have way too many domains so am currently going to be putting lifefeed.com up for auction.
Click here for details.
Gartner have recently published a press release, outlining the eight mobile technologies to watch in 2009 and 2010. This is from a report available at a cost from the Gartner website.
Reading the list makes me want to start an my own research business, as the topics they list are – to quote Simon Judge – pretty arbitrary. They seem to list most of the mobile buzz words currently circulating and nothing in the list is surprising. I would agree with Simon that there are a few other topics they could have listed – but would be inclined to extend “Open Operating Systems” from his list to “Open Source on both mobile client and server”.
Mobile will be one of the main areas where we will see disruption through Open Source in the coming months – and that won’t just be limited to the mobile device itself, as I’m sure Fabrizio would agree. In fact he would probably tell you that you should have started “watching” that particular trend some time ago.
The first step an organization needs to take in establishing an Open Source strategy is to baseline the current landscape. Now to be perfectly clear: many people will jump on this step and “pooh pooh” about how unnecessary it is because they
However, regardless of what they think they may know – they probably don’t. And if the corporation has carried out a prior assessment – that was probably in 2003 or 2004 when they were benchmarking Linux usage. At least I’ve had enough of those reports waved at me, together with a remark as to the fact that “and we have a few Apaches and MySQLs running”.
So what are the typical goals of this first step? Well it’s to pull together enough information about the internal adoption of Open Source that you can present the complete picture to the various people and departments you need to engage on the next step.
The result of asking these questions is that people within the organization will begin to understand that there is more to it than just knowing about the odd Apache installation.
When I go into a corporation or other organization to establish an internal Open Source strategy, the work generally follows the following steps (although they obviously need adapting to each additional organization). I talked about the steps during the Open Source strategy workshop earlier today:
I’ll talk about each point in more detail during additional posts.
It was interesting to see Ingo Schwarzer, CTO of DB Systel talk about the similar steps they are beginning to take to establish an Open Source strategy during this afternoon’s keynote at OSMB.
By chance I’ve spent some time recently consulting with OSS Watch in Oxford, UK. Ross Gardler and his team provide Open Source advice and guidance free of charge to UK higher and further education organizations. Apart from the chance to visit Oxford a couple of times (and loving it more each time), it has allowed to me to gain insight into how Open Source is viewed within the UK education community.
In particular it has been interesting to see how efforts in the UK are growing to provide children in schools and students in universities with the knowledge they need to understand Open Source and have the qualifications many companies now require when recruiting new employees. It is still proving difficult to make sure young people have enough knoweldge (both practical and theoretical) around Open Source and OSS Watch are constantly looking for additional ways of doing this.
So, now I would be interested in hearing about similar initiatives in other countries – or indeed people interested in establishing or building out similar initiatives as I think this will become increasingly important as we see Open Source adoption growing everywhere.
Later today, I will be participating in a workshop at the Open Source Meets Business conference here in Nürnberg. The title of the workshop is: “Open Source as part of an IT strategy” and I will be one of several panel members.
My input will focus mostly on the steps that need to be taken to build up an Open Source strategy within a corporation or large organization. Most of this collected from the exeprience I’ve gathered over the past years in helping corporations understand and engage with the “Open Source way”. Hopefully the audience will jump in with their thoughts and it will be a lively discussion.
I’ll post after the workshop with some additional thoughts around the steps that need to be taken.
The keynote that stuck with me today at OSMB has to be that of John Lilly, CEO of Mozilla. His keynote stuck out from the rest because it was a refreshing and insightful look at some of the philosophy that is driving Mozilla today. He will be uploading his presentation to Slideshare soon, but here are some of the quotes I took away and some added comments.
Lots of Open Source projects are successful, but there is no clear model on how to get there.
This is something I sometimes feel needs emphasizing over and over again. Especially when I talk to companies interested in going Open Source and building a community. There is no “game plan” on how that may or may not work. It is an individual process that needs to take all the parameters of the underlying Open Source project and the company(ies) behind it into consideration. If there was a single way for an Open Source offering to become successful, then someone would be making millions.
40 % of the Mozilla code is contributed by non-employees
Again, another interesting point if you are trying to build a community around your Open Source project – how much of it has been developed from people outside your organization?
The strongest open systems are “Chaords” – with distributed decision-making, nodal authority and ways to route around
Look at successful open systems that adhere to these principles – Wikipedia or the Apache Software Foundation and the underlying projects for example.
Make it easy for your community to do important things
The best citizens [of a community] challenge the status quo
I would add to the last point that you also need to provide ways for members of the community to actually challenge what goes on inside the community and how the Open Source product is shaped.
In all a good presentation and I hope many of the attendees took away the key points.