Open Source Pragmatism...


First off, to my few readers, I didn't die... :) I had a very interesting couple of weeks, plus a vacation. The short version of my interesting weeks is that I've left Motorola and taken a job as an Open Source Community Manager at CollabNet, where I'll be working to help build the communities of CollabNet's current and future customers interested in Open Source development practices. When and if I end up doing a corporate blog, I'll post the link here.

Now, on to today's topic - Open Source Pragmatism. I was having a conversation with some new colleagues, and I mentioned that I sometimes get a hard time from hard line Open Source folks about my use of a Macbook Pro. I look at software very pragmatically, and quite frankly, while Ubuntu has done a great job of getting the Linux Desktop to where it is, it still cannot compare (for my needs as a consumer) with OS X. Now, that doesn't mean I don't believe that Open Source (and Linux) have made great strides on the server side, and even in embedded.

I do strongly believe that more folks need to take a pragmatic view of Open Source in general, and understand how to get customers to use software (i.e. - meet their needs) instead of playing the religious card (yes, that means you Mr. Stallman).

Open Source needs to realize it has to start approaching things from a pragmatic, as well as a passionate point of view. Doing this will ensure that more folks see the advantages of using Open Source where it makes sense and meets their needs.

Comments

Post a Comment

Popular posts from this blog

Great Panel Discussion!

Thanks to Gwyn Firth Murray , Larry Augustin , and Jeff Luczcz for a very entertaining panel discussion around Open Source at the recent eBig meeting . I was a bit nervous about how this panel would come together since I was the 'rookie,' whereas Gwyn had worked with Larry and Jeff separately before. However, the commonality of the passion for Open Source brought this panel together nicely and there was an excellent exchange of ideas between and amongst the panel (as well as our audience). I think we had someone in the audience comment on the fact that it seemed like we had all known each other a long time! :) The areas we covered during the talk were: licensing, community development, and reasons for using Open Source. I think the panel all agreed on good reasons for using Open Source, with all of us giving cogent examples of what the value proposition for using Open Source is (taking advantage of the huge amount of R&D and work that goes into good Open Source project...
Read more

Community Management is a Career, Not a Job

'Community Management' is a hot topic, & a hot job field , but I think it's important to articulate that it's not a role which should be approached as a 'job'. What do I mean by that? Community Management should NOT be: A role you 'settle' for because you can't do other things Something you do as an ancillary part of your 'real job' Something you get into 'because it's hot right now' A position that you can perform in isolation, without constant upgrading of your skills/knowledge I've talked in the past about what kinds of skill sets I believe are necessary to be an effective community manager, and as I thought about my own career path, I realized that early on in my community management career, I considered myself an engineer doing community management, whereas I now think of myself as a community manager with an engineering background. It is a subtle, yet hugely important difference - one that allows me to draw on a...
Read more

The Power of the Open Source Periphery

Like a lot of people in the tech world, I try to read a variety of publications (both online and physical versions) to keep up with what is going on in the dizzying world of technology. Recently, I read a great article in a recent issue of Wired entitled Accept Defeat: The Neuroscience of Screwing Up . This article explains in some detail, with examples, the problem of 'failure blindness' in scientific research. This phenomenon causes scientists and researchers to ignore anomalies in their results they didn't expect, which are therefore categorized as 'failures'. The article goes on to state that one of the best ways of overcoming this bias is to involve other people from outside of your immediate speciality in discussions about your results. For me, this triggered the thought process of why it's important to encourage participation in your communities (Open Source or internal) from folks on the periphery of your project - non-specialists who have somethin...
Read more