Mar
12
Imagine if the Declaration of Independence was written in “Word 1776.” What are the odds that we’d be able to open that original document today?
Great quote by David Egts, Principal Solutions Architect at Red Hat, Inc., in a interview on the WashingtonPost.com web site Viewpoint. He was highlighting the importance of not only Open Source but Open Standards in everything from business to government. There is a lot of talk of companies that are struggling through these rough economical times and the Open Source road maps that can help them through. Those exact “road maps” are also being explored for government implementation which I personally think is long over due.
The discussion with David Egts was a great forum that allowed the public at large to ask direct questions. David Egts covers a wide range of topics. It’s a good read. Suggest you go over to the web site and check it out.
http://discuss.washingtonpost.com/wp-srv/zforum/05/dlt.htm
Jan
28
Ok, sensative subject I know. It can be tough to mention Microsoft and Open Source in a positive sentence that doesn’t talk about one hammer on the other. However that is where we find ourselves today. In a blog post on MSDN blogs, Sara Ford the Program Manager for CodePlex which is Microsoft’s open source project hosting site, talked about the CodePlex websites growth over the past year.
In just about every category Sara touches on shows an increase of over 100%. This includes things like visits, unique visitors, and new projects. Maybe this will inspire Microsoft to invest more into their open source initiatives. Yeah, that was probably pushing it a little.
CodePlex Weblog : CodePlex 2008 – A Year in Review.
Jan
25
During this time of financial “belt tightening” we are all feeling the pinch and probably no one more than the IT organization budgets across the corporate map. IT is typically the first to get hit, and hit hard, by cut backs. It’s during this time that CIOs and VP’s who wouldn’t have given Open Source Solutions much of a look start to turn to Open Source as some sort of magic bullet to allow them to get what they need and stay within budget. I wish to throw out these words of warning to both the afore mentioned group and the Open Source enthusiast who have been working to get Open Source into their environments and might be thinking this is the opportunity they were waiting for.
Yes, there are financial benefits to having an Open Source architecture and those people who have one will be able to manage the rough waters moving forward a lot easier but if you have not already established this environment then chances are you’ve already missed the boat this time around. It should be made very clear that there is a cost to implement any environment, including an Open Source environment, and more so if you are attempting to replace an existing environment.
For my fellow Open Source brothers (and sisters) who long to hear the phrase “let’s move our environment to Open Source” please proceed with a great deal of caution. Make sure the spirit of the initiative to move to Open Source is one of genuine architectural decision making and not one of financial desperation. In the latter scenario, organizations have already conceded to needing to “cut corners” and see Open Source as a way of doing this. The message should be made clear that Open Source is not a corner cutting solution. Furthermore, there are no substitutes for best practice and common sense, so do not sacrifice your architecture for the opportunity to implement a piece of Open Source you’ve wanted to put in place, make sure it’s put in place correctly. It will do more harm to your environment, and the efforts to establish Open Source as a better solution, if your implementation is done poorly and without enough forward thinking and ultimately fails.
Final suggestions:
Where Open Source fits, IMPLEMENT! Accept there will be cost.
Where Open Source needs to replace another solution, plan out the implementation carefully and try not to sacrifices any current functionality you may have now.
Nothing replaces best practices and having clear, well defined standards.
Good Luck!
Jul
03
I posted my first question on Linkedin Q&A service and I have to say the speed and quality of the replies are wonderful. So the question went like this;
Is a closed source solution with good APIs a better approach than an Open Source solution?
I went on to explain;
Would you rank a “closed source” solution with a great set of easy to use APIs on the same level as a good Open Source solution?
So for example, let’s say your company needed a blog. You could go and download any number of Open Source blogs and customize it to your company’s needs, or you might spend money on a proprietary blog system that forces you to do things a certain way, or would you rather a closed source (still a proprietary) solution that “out of the box” had you do things a certain way but also offered APIs that allowed you to build you own interface or feed your blog to another solution?
Here are a couple of the great replies I got back:
Having access to the source code is fantastic, since it gives you a great way to – in theory – take matters into your own hands and diagnose any issue, and extend with any feature, you so wish. If you’re in a large corporate environment and you need to build in a custom extension to make it acceptable to your users (eg. integrate with your company’s proprietary SSO solution) then this can be invaluable.
I think most times the decision will come down to supporting the application and overall cost. Sometimes bigger business needs to have an expert to call when things go south. In smaller businesses, sometimes you wing it.
Each solution has its place. You just have to make that decision in the best interests of your business and your goals.
Its not a question of open or closed and its definitely not a question of Hosted versus SaaS. Its about whether the solution is component based, tailored, scalable and replaceable.
For instance if you opt for a closed solution with really great APIs – that works so long as everything you need to do has been anticipated by the API provider. Unless you use a standardized api (like open-social) or an api that is so dominant that the market provides good adapters to standards (like Facebook ) you will always be dependent upon the development and deployment plan of the closed system you’ve selected.
I think you actually answered the question yourself, Eric. In my experience, the answer to this always comes down to the two main points you mentioned. Do you NEED the flexibility of an OSS solution? If you have the resources, and the need for true customization, then OSS is always a great option.
Regarding patches and security, a well maintained OSS project with an active community and a wide install base is generally going to be ahead of the curve when it comes to bug fixes, etc.
You can see the question hosted here
Jun
24
I think it goes without saying that I am a huge supporter of Open Source but believe it or not I am also a big fan of Bill Gates. You’ve got to respect what he did for the industry and what he does for the world through his charities. The guy is a geek’s version of Michael Jordon. I don’t agree with everything the man does obviously but I think the guy has a great mind and he will be missed in the computer industry when he finally moves on.
Anyways, I enjoy watching Bill Gates talk but I kind of caught something interesting in this last interview I was watching.
Here is a link to the interview:
http://news.bbc.co.uk/1/hi/business/7462156.stm
At about 1.45 Bill talks about how finding the source code for an operating system took him and Paul Allen to the next level on tinkering. I thought to myself how fortunate we were that he had that oppurtunity to look at and study an operating systems source code. It would have been a real shame if the ability to look at source code was deprived from Bill Gates. I wonder how many great thinkers Linux has or will inspire by offering them a similar opportunity.
