OpenNMS and Fluke Networks

Having started out in the telecom industry (back when it was different from datacom – yes, I know, I’m old) I was always a fan of Fluke test gear, so I find it kind of amusing that they’ve decided to pick on OpenNMS to promote their latest commercial network management tool, OptiView.

I didn’t even know Fluke was in the network management business, so I was surprised when someone sent me a link to their website in which they feature part of an OpenNMS screenshot as their “wrong way” example.

I’m pretty certain they just grabbed this image off of the web because the text of the page could read as an advertisement for OpenNMS. They obviously didn’t do their homework. I thought it would be a fun exercise to examine their claims in the context of our project.

Lack of Proper Perspective

In this paragraph they state “Central polling misses performance from the user’s perspective”. This is true, and it is why OpenNMS has a remote poller that performs synthetic transactions from the point of view of remote end users and integrates with most popular mapping software so that engineers can easily pinpoint problems. This is in use at nearly 3000 sites worldwide for Papa Johns Pizza – it would be interesting to know if Fluke has an install on that scale, and if so, how much it would cost.

A False Sense of Security

They lost me a little on this one, but they seem to be saying “our monitoring is better than your monitoring”. OpenNMS has multiple levels of monitors, from simple ping/port checks up to capturing the full user experience with the Page Sequence Monitor and the Mail Transport Monitor. When OpenNMS polls for service assurance, it is, for all practical purposes, a user of network services and it reports back what a user would experience.

Lack Troubleshooting and In-depth Analysis

This section states the need for root cause analysis and “packet-level ‘on-the-wire’ visibility.

Well, as for root cause, OpenNMS duplicates the functionality of such classic management products as Netcool/Omnibus and Netcool/Impact, so I’m pretty certain it can address whatever it is OptiView claims to do.

As for packet-level inspection, this is one area that OpenNMS does not cover. One of the reasons is that with today’s large and distributed networks, it is not feasible to monitor every single packet on the network. What OpenNMS does do is indicate areas where there are problems, and then engineers can take their packet sniffer and investigate further. We often use Wireshark in diagnosing customer issues, once OpenNMS determines the part of the network needing attention.

Risks of an Incomplete Picture

This list of bullet points is pretty valid, but the assumption that tools like OpenNMS provide “an incomplete picture” is patently false. I tried to download their “NMS Risks & Shortcomings” white paper but got an error message “This area of the site is temporarily unavailable.” Heh.

This is typical FUD from a commercial company trying, and failing, to differentiate itself from other underpowered and overpriced commercial software tools.

But I must say I’m somewhat flattered by this since our goal with the OpenNMS project is to make every decision about a network management solution to include the question “Why aren’t you using OpenNMS?”

I’m hoping than everyone who might find this site asks themselves the same thing.

Infidel

This is one of my more navel-gazing posts (well, more than usual) with little open source or OpenNMS content, so if you don’t like this sort of thing, please skip it.

I am not very politically savvy. I’m a geek and I studied to be a scientist so the unvarnished truth is pretty much my goal. It’s one of the reasons I like open source – everything is out in the open, including the code and bugs. This is at odds with traditional software since there was always a much greater focus on marketing. The goal was to sell as many licenses as possible, not necessarily to solve problems in the best way. Open source has no license cost, so one can be more honest. I frequently recommend that certain people who contact us check out Solarwinds, since they are either too small or don’t have a qualified person on staff to get the full advantage of OpenNMS. As a provider of services, my margins are built on a certain level of effort per client, and if there are bad matches, one or two clients could sink those margins.

Yet it seems that certain people in the open source software business can only understand selling commercial software, and so I often feel like an outsider when I try to explain that it is possible to make money without compromising the open source nature of a project.

I feel similarly disenfranchised when it comes to politics. I belong to no political party, although many, many years ago I was a registered Republican (back when they were the fiscally conservative and pro-technology party, so a long time ago). It seems that both parties have been so overtaken by extremists that there is no room for someone like me: a moderate who is willing to compromise and engage in honest debate over the issues.

With the upcoming elections, never before have I felt such distaste over my choices. In my congressional district I can vote for Bob Etheridge, an incumbent who has such little self control that he assaulted a student who was holding a camera, or Renee Ellmers, who is the kind of insane conservative that caused me to leave the Republican party in the first place. Seriously, the biggest threat to our country right now is whether or not to build a mosque near ground zero? C’mon – if you want my vote tell me in concrete terms what you’d do to make things better and stop playing on emotions and fear.

My general frustration with both the politics of business and the politics in government caused me to fall in love with my latest T-shirt acquisition.

It says “Infidel” in both English and Arabic (well, the Arabic word is actually kafir). It was given to me by Robert Neill when I met him at the Linux Link Tech Show booth at SELF, and if you like it you can order one from his website.

I’m thinking about wearing it to the “Rally to Restore Sanity” at the end of next month in DC. I can’t decide on it or one from the “I’m Voting Tea Party” site since both seem to resonate with me.

Oh, as someone who has spent time in the Middle East (both in Syria and the UAE) I was asked if I would wear this shirt in, say, Dubai. The answer is no. Though I am certain my friend Yunus (a devout Muslim) would find it amusing, some people there would obviously think that I am making fun of their beliefs and would find it insulting. That is not my goal at all.

My goal is to insult those within business who think there is only one way to make money, or those with in politics who are so inflexible that anyone who disagrees with them, even in part, is the enemy.

I am proud to be an infidel in their eyes.

GPGMail 1.3.0 – Open Source In Action

Yes, I use a Mac. Yes, I hate freedom. Yes, I use Mail.app.

And I am a bit of a security nut.

One of the most useful pieces of software I’ve used over the years is a plug-in for Mail.app called GPGMail. It was originally written by Stéphane Corthésy and released under an open source license, and it allows one to easily decrypt, encrypt and sign GPG messages right from Mail.app.

The problem is that Apple doesn’t really have an API to make such an integration easy, so with every new release of Mail.app it would usually break the plug-in, and Stéphane was responsible to fix it.

Well, after awhile Stéphane wanted to move on to other things, and with the advent of Snow Leopard GPGMail was broken – seemingly for good.

Stéphane writes:

I’ve just read the latest emails on the list, without participating. Actually I haven’t participated to the project since a very long time, for personal reasons. Situation will not change in the future, I guess.

It’s been now 10 years since I started GPGMail. At that time we were working on Rhapsody, the ancestor of Mac OS X, the link between Mac OS 9 and Mac OS X. gpg had just gone 1.0. I started the project because it might have been a critical piece of code for us at Sen:te in the near future, and it was really fun to develop 🙂

Plugin was then made public, and received some interest in the Mac community, though it was still for geeks. Interest in PGP became bigger, the MacGPG project was born a year later, thanks to Gordon Worley. This encouraged me to go on with GPGMail development, and also MacGPG sub-projects. I spent many week-ends and nights coding for those, and have been very happy to see interest growing more and more.

Then time passed, it became hard to find people able to help on MacGPG development, and very few people were able to spend time to understand the underpinnings of (GPG)Mail, except me, unfortunately. By making the project open-source I had expected that people would come in and make the project go further. I was rather deceived by this, I must admit. There was no real momentum.

On my side, I wanted to explore also other projects, and became tired of working on GPGMail. I wanted something new. It was getting boring, I had less time to reply to user requests, and code had got very messy. GPGMail development quite stalled from that time, I spent time on it only after major system updates. I was still hoping some people would enter and help on the project in the long-term, not only for a single patch. Thus I opened up the project by putting it on SF, with a real OpenSource license that would’t prevent people from working on GPGMail.

To be honest, I waited a rather long time to upgrade to Snow Leopard specifically because GPGMail support was important to me. When Stéphane backed out of the project, the list was abuzz with people wondering about its future. Luckily, a number of people stepped up to take it over. The project launched a new website, the code and bug tracker was moved to github, and various patched versions started to come out.

Stéphane continues:

When Snow Leopard arrived, I was already spending no time on coding during spare time, and was not really willing to. Finally people entered into the dance and started coding, not only whining. And I must admit I’ve been really surprised by the results they obtained (congrats Lukas and others!). I kept telling myself I would update the project, and make a public release, when I’ll find time to, but the fact is that I cannot, for several reasons.

For so many years I’ve been hoping to find people helping me on the project in the long-term, without finding any, but now that time has come, project can fly without me. I hope there will always be enough people to take care of it. Till now, project was organized by only one person, and depended only on me. I took care of every details. It’s time to change that model and let the project be managed more flexibly. The bazaar model, as I would say.

So please, move the project out of SF, leave it opened to developers, designers, writers, aficionados of all kind. It’s no longer dependent on me, it will depend on all of you. I will close the SF project (and mailing list), and redirect the Sen:te web pages to the new site, once you completed the migration, then I’ll have a glance at the project, from time to time, probably to complain 😉 . My baby’s no longer a baby; it no longer needs me.

Thanks all for your support, and now take great care of GPGMail.

Today the team released version 1.3.0 of GPGMail, the first real release under the new model. It installed for me without incident, and I am happy that this project will live on. Thank you Stéphane and thanks to the whole GPGMail team for making this happen. Plus, none of this would have been possible if GPG itself wasn’t open source and packaged by a number of groups. Score one for the open source ecosystem.

Had GPGMail been commercial software, I would have been out of luck, but because it was open source, and that there were many who found it valuable, it lives on and propers.

Awesome.

Open Core is Dead

I was wanting to take a break from Dev-Jam to put down some thoughts I’ve been having during this recent renaissance of the “open core” debate when I realized something:

Open core is dead.

At least as a business model. While I don’t expect it to go away overnight, I do expect to see very few new companies using the model and those commercial software companies that tout themselves as open source reframing their marketing to de-emphasize it.

I base this on observations of my own market. Even though searching on “open source network management” in Google returns OpenNMS as the first hit, for years the industry press omitted us from articles on open source management to focus on three VC-backed firms: Groundwork Open Source, Hyperic and Zenoss. All of these companies are what I would classify as “open core” and it is interesting to see where they are now.

Groundwork Open Source (GWOS)

This was one of the first open core companies to try and commercialize open source projects. When it started in 2004, GWOS sold commercial software “wrappers” around a number of open source projects without releasing any open source code on their own. In 2006 they started to distribute the “Groundwork Monitor Community Edition“. After four rounds of funding, they have raised $29 million (A: $3MM, B: $8.5MM, C: $12.5MM, D: $5MM) but they still come across as a company looking for a business plan. Once known for selling software licenses in excess of six figures, they now sell a “quickstart” version for $59.

Since I am pretty much known for running my mouth, people tend to contact me with their experiences with companies in this space. I received one such e-mail a few weeks ago:

Hey, I was just told that GWOS is no longer putting out a community (free) edition. I was told this by one of their support guys, was told that was the reason why they are now releasing version 6.2 while the 6.0 CE version hasn’t been updated since December. He said they were just going to quietly “let it go to the community” … Also interesting is that the $59 “quickstart” is just that, not really meant to be production, no upgrades or updates come with that, and no guarantee that you can even purchase the upgrades later

I thought this was interesting, so I did some poking around. I found an entry on their forums (which doesn’t seem to be policed for spam anymore):

Interesting, seems like all traces of the free/community version are gone from their site. Still available on sourceforge, I’d grab the latest version while it’s still there.

Not one to just publish hearsay, I sent a note to Tara Spalding, their Chief Marketing Officer, asking if the rumors of GWOS dropping support for their community edition was true, and she replied:

Thanks for reaching out. That is untrue, and the rumor mill is pretty lame.

I replied to ask her when we could expect the next community edition, but I haven’t heard back. The latest enterprise edition is 6.2, but the last community edition is 6.0. That’s pretty high number for a VC-backed firm – most have an exit between versions 3 and 4. (grin)

I was reminded of this exchange this week when I saw a GWOS ad in the Wall Street Journal (click to embiggen):



It was about 1/6th of a page, which runs around US$40K, so it must have been important to them. Note that the term “open source” does not appear at all in the ad.

So it seems, at least on the surface, that GWOS is trying to distance itself from the term “open source”. It will be interesting to see how they deal with their name. Perhaps after all that money and all that time they will find success marketing themselves as a commercial company.

Hyperic

Another open core firm that used to be referenced a lot was Hyperic. I would often use them as an example of the problems with the “feature wall” inherent in open core solutions. The difference between Hyperic and the other VC-backed companies is in the quality of the VCs. Benchmark and Accel seem to know what they are doing. Hyperic was rolled into SpringSource just before the latter company was sold to VMWare. Thus the VCs got an exit and I assume the five founders of Hyperic did okay financially.

What’s funny is that, although Hyperic products are owned and sold by a very commercial software company now, the interest we receive on the OpenNMS and Hyperic integration has actually gone up. It seems that framing the Hyperic products in the context of commercial software has actually made the buying decision easier, and the term “open source” does not appear anywhere on their home page.

Think about that – being honest and representing Hyperic software as commercial software with an open source component (versus open source software with a commercial component) has actually increased interest.

Zenoss

Zenoss has a very popular “core” product that they publish under an open source license, coupled with a variety of “enterprise” software offerings that they price per device per year. Their enterprise “silver” package is listed at $100/managed resource. Note that this is the subscription price – that is $100/resource/year. So if we take an average OpenNMS install of 2000 devices, that would run $200,000 a year, or $1,000,000 over five years.

It is really hard to argue that a Zenoss enterprise solution is any less expensive than, say, a solution using HP OpenView. In addition, most software from HP and IBM is licensed in perpetuity: i.e. once you’ve bought it you get the right to use that version forever. It would be hard for an enterprise of any size to base its management solution on something that must be renewed year after year, with no guarantee that the price will remain the same.

Now, this is a post proclaiming that open core is dead, so I’m not here to pick on the way Zenoss prices their software. What I want to examine is the usefulness of their business model. As a VC-backed firm that has raised around $25 million, I assume the desired exit would be an acquisition. But how would one evaluate them? A number of past Zenoss commercial clients have talked to us as an option to Zenoss, simply because their revenue structure is not sustainable. In addition, as part of the OpenNMS project we are targeting those enterprise features users of Zenoss find most valuable, and we plan to offer them for free. Heck, $200,000 can go a long way toward funding a lot of custom development, so a Zenoss user could spend that money once and get what they need under a truly free and open source license. Thus the value of the Zenoss commercial software has a very short shelf life, and since they have no revenue model based on their open source software, so does the value of the company.

I think investors are wising up to this. In their latest funding round the target was $5.2MM but they only raised $4.83MM. Thus it would appear that at least one of the investors pulled out of the deal at the last minute. That was a smart move.

[Note: our goal at OpenNMS is to produce the de facto network management platform, so I’m not targeting Zenoss specifically but all commercial software vendors in this space. Our free software will continue to erode the value of their commercial software. This is also not meant to be taken as an attack on anyone who uses any of the products listed here – if it works for you, great. This is more an examination of the business of open source.]

With the backlash hitting SugarCRM and NASA spurning Eucalyptus in favor of OpenStack, it seems that the market is wising up to open core and demanding more from companies that call themselves open source. With examples like Hyperic above, it seems to be in a commercial software company’s best interest to avoid referring to their offerings as open source. It looks like Groundwork is moving down that path and Hyperic is already there.

Open core is dead.

Monty Says: A Definition of an Open Source Company

Just a quick post as I head toward OSCON.

Monty Widenius, one of the founders of MySQL, has an interesting post where he makes an attempt to define what it means to be an “open source company“. I’m happy to say that the OpenNMS Group meets that definition, but I’m not 100% sure it is complete as the requirement that an open source company is one that “produces software” does leave out a number of companies that promote and deploy open source solutions without actually writing code. But I think it is a start.

I also hate that I missed the Community Leadership Summit due to a prior (and totally enjoyable) commitment, but we were able to at least sponsor it. If this is any indication of what went on I’ll have to be sure to make the next one.

Two Problems with Free

Things have been delightfully busy here at OpenNMS, and with Dev Jam coming up the level of excitement around the project is pretty high.

One of the people coming to Dev Jam, Matt Raykowski (OGP) send me a link today to a Slashdot article bringing up the “open source vs. open core” debate again, this time with respect to SugarCRM. Apparently some of the new features of the product are only available to paying customers.

I’ve been staying out of the recent resurgence in the “open core” debate (check out the 451 Group for a summary). If these fauxpen source vendors would simply call their product “open core” versus “open source” there wouldn’t be anything to talk about, but they need to market themselves as “open source” as opposed to “just another commercial software company with a great API” to get any traction.

The Slashdot article quotes Martin Schneider of SugarCRM stating “We are an open source company and it’s why we’re better than proprietary companies” which is total crap. Just being open source doesn’t make you better, but the fact that he would sum up his pitch that way just goes to show how much the term “open source” is tied to their marketing.

In contrast, take a look at OpenNMS. OpenNMS is a very powerful, flexible and scalable network management application platform that happens to be free and open source software. For many large enterprises and carriers, that makes it a better solution (especially when the alternatives charge per managed device), but for many smaller companies they’d be better off with Solarwinds’ Orion, a commercial software product, or something similar. Just being open source doesn’t automatically make OpenNMS the right choice and better than a proprietary solution for everyone.

Personally, in the case of SugarCRM, we struggled with the community edition for six months before signing up with Salesforce. For us it wasn’t a better solution even though Salesforce isn’t open.

In looking through the comments on the Slashdot article (yes, I know, I know) it seems there is some debate over if the paid version might really be open source. If it is, that seems like a really stupid business model, since if the paid version is freely distributable (a requirement of the OSI’s open source definition which I’m sticking by until someone offers a better alternative) then they could theoretically only sell it once and that person can choose to make it available to everyone. I doubt that Larry Augustin (the dark lord of open source) would do something like that since if anyone can make a buck from open core it’s him.

Anyway, in my mind Brian Prentice of Gartner put the whole open core debate to bed with his “Emperor’s New Clothes” post, so enough about that.

What I want to whine about today is two problems I continually face running a business on free and open source software, namely that pesky term “free”. If only Richard Stallman had added three more letters to coin “freedom software” my life would be so much easier.

The first issue is that when people here “free” they think cheap or not very good. In the best case they wonder “what’s the catch?” In many of our deployments we’ve replaced OpenView and Tivoli simply because they could not do what OpenNMS can, so even though it is free software that doesn’t make it any less valuable.

The second one arises when it is time to actually spend money on free software, such as with a support contract or professional services. A common deployment scenario is that a network manager or system admin needs a tool like OpenNMS. They go to their boss and ask if they can install it, and the boss asks how much it costs. When the answer is “free” they go, “Sure, knock yourself out.”

Now once the system is installed and there is a need for services or support, they go back to their boss and ask to spend some money, to which the boss says “I thought you said it was free?”

Open core is dead – the writing is on the wall – what with companies like Compiere going back to their commercial software roots and the VC market that funds it rapidly shrinking. The challenge now is to get across the value of free software coupled with commercial services in lieu of a commercial software solution, open core or not.

Yes, I Hate Freedom – the iPhone 4

Last fall I bought an iPhone 3GS. It was a hard decision, but one I haven’t really regretted. Note that I don’t make many phone calls, so I was mainly interested in having a 3G iPod Touch, but I did have the requirement of having a GSM phone since I travel overseas a lot.

Last week, as you know unless you have been living under a rock, Apple introduced the iPhone 4. It was enough of a redesign that it triggered my “don’t by Rev 1 products from Apple” rule, so I was in no real hurry to get one. But then my wife, who is a runner, kept borrowing my iPhone for the MotionX GPS app to track her progress so I got permission to spend the extra money and get the iPhone 4 so she could have my old one.

After a week of playing with it, I have to say I’m pretty happy. The biggest weakness of the iPhone 3Gs (at least the way I use it) was the camera, and the new iPhone camera is much, much improved.

Of course a lot a press has been devoted to the “retina screen” and it is beautiful. I wear contacts that I take out every night, and one of the first things I do when I get up in the morning is pick up my phone to check e-mail. I have to bring it close to my face to see it, and it is almost impossible to make out the individual pixels. Think about it – the iPhone 4 is 640 pixels wide and the pictures I post on this blog I crop to 450 pixels.

I have also noticed much improved battery life. The iPhone 3Gs wasn’t bad and it would last me about a day of heavy use, but the iPhone 4 seems to go about twice as long.

However, the only real “wow” feature has been FaceTime. I was chatting with OGP member Mike Huot and it worked amazingly well. In fact, I think the audio quality over FaceTime was equal to or not better than what I get over AT&T with a normal phone call (FaceTime is Wi-Fi only). Another cool feature is that you can switch between the front and the back cameras by tapping an icon in the lower right side which means you can show your caller what you are looking at without having to rotate the phone.

On the downside, much has been made about the attenuation of the signal when the device is being held. Unlike the other iPhones, the iPhone 4 is surrounded by a metal band that is also used by the antenna. I can tell you that the problem is quite real. While this may be hard to believe, I have never had a call drop from the office, and the first call I received on the new phone dropped within the first 10 seconds. Of course I was gripping in my left hand, which is apparently a no-no.

I think it is pretty easy to figure out how Apple missed this. In all of the real word tests the phones were in cases to hide the fact that they were new. This probably helped the signal and the fact that in Silicon Valley AT&T drops calls often, so the testers probably didn’t notice. In any case, I ordered my $30 rubber band which should help. I’ll know more when it arrives next week.

I’m not unhappy with my purchase as the camera improvements mean I can leave my point and shoot at home now, but barring the fact that my wife wanted my old phone I would not have bought at this time. Always, always wait for Rev 2 if you can help it.

Of course, programming on the iPhone can be painful. I usually spend 45 minutes just sorting out my certificates, although the new Xcode makes it a little easier. I only use it to play with the new OpenNMS iPhone app, but it is considerably harder than anything I’ve done on Linux.

I do have a little bit of guilt about buying such a closed product, but my reasons for buying my original iPhone still stand. However, I saw on MacRumors that there is a new project called “marble” which may actually become Xcode 4, and it got me to thinking. Since Apple now owns it’s own chip company, it could use Xcode to be the only way to compile on it (although Ben tells me that it would be much harder than that to lock it down). Then Apple could move all of their Macs to that chip and seriously lock down those as they have the iPhone/iPod/iPad. Thus OS XI or whatever would be as closed a platform as we’ve ever seen (well, at least on that scale).

A long shot I know, but scary.

So you might be asking “why in the world did you buy another iPhone, you freedom hatin’ conformist?” In part it is because I don’t view it as a development platform like I do a standard computer. I don’t need to have access to the code in my microwave or my car, for example. And I am seriously hoping that Android is able to catch up. I think it will, eventually, but that it will take time. Apple has a larger market cap than Microsoft, so they have a lot of money to throw at the product, and it is hard for a free, distributed community to compete with that as quickly.

But with enough time and interest, all commercial software becomes a commodity.

Brian Aker on Open Core

Brian Aker and I don’t always see eye to eye, but we agree much more than we disagree. I really enjoyed his post today about the open core business model. While not as damning as the one Brian Prentice wrote about the Emperor’s new clothes, it brings home a lot of points from someone who has a lot more open source cred than me, and who has lived through it. Perhaps this will lead to an awakening of the market to the severe limitations of open core when compared to true free and open source software.

Several Random Thoughts Gathered Together in a Cave and Grooving …

It’s interesting to spend a lot of time away from home, especially in foreign countries, since the change in scenery and language can definitely get the creative juices flowing.

I’m writing this from France (I had forgotten that a) people smoke a lot here and b) people really like to have dogs, which makes walking down the street an adventure) where, since I happened to have Internet access, feels in many ways like home but in very large and important ways is not.

This weekend I was trying to catch up on e-mails and one involved filling out a long survey. One of the questions was “What advice would you give open source projects just getting started?” to which I answered they should run out and read a copy of REWORK.

REWORK is great, because if I were to write a book on business, that is the book I would write. Since I have so little free time as it is, I am happy someone else wrote it for me. (grin)

It is written by Jason Fried and David Hannemeier Hansson of 37signals. While 37signals is not an open source company, they did sponsor the development of the Ruby on Rails framework, which is used to make their own web applications as well as those of countless other projects. But they are a software company that started with little investment but a whole lot of talent and energy, and thus they parallel a lot of open source projects.

Even though it clocks in at nearly 300 pages, REWORK reads quickly. It consists of several short ideas about business as experienced by the 37signals team, and most of them are spot on. It is a book that screams to be read in the bathroom. Each point is presented in little chunks, most not more than a page or two in length, and reading it over time in the bathroom will let each one sink in between readings (all puns intentional).

One thing I don’t do that REWORK suggests I should is work less. I probably put in 60+ hour weeks with OpenNMS. Sometimes this is out of necessity but most of the time it is that the business occupies a good portion of my thoughts. Plus we now have customers all over the world and it helps to be able to answer their questions either early in the morning or late at night.

I also think that they don’t talk enough about having excellent people working with you. They do emphasize the beauty of remaining small, but I have never worked with a better team than the OpenNMS gang and that is really important. If you want to manage a geographically remote, self directed team they have to be great people. They have to really want to be doing the work that needs to be done.

The OpenNMS Group is growing during this economic downturn, so I am often asked by people for a job. My reply is to get involved with the project, show me what you can do, close a few bugs and demonstrate that you have what it takes. Rarely, if ever, does that happen, and I know that I’ve dodged another hiring bullet. The people I hire want to be there for more than just a job.

I did love the research on failure in the book. One of the reasons I dislike the venture capital community is that it seems to be made up of a small group of gamblers who have made a lot of money for themselves, and a large group of sycophants that hope to make a lot of money. This group seems to thrive on failure.

For example, I worked for one company that after I left hired a certain person as CEO. This was a pretty close knit team of 40+ people, but not only was he an outsider, he didn’t even relocate to be near the business. In less than a year he drove the company down to less than 10 people, and when the board fired him the most enthusiasm he ever showed was in his weekly calls to make sure his severance was getting paid (he left the company much weaker than when he found it and cash flow was a problem).

So imagine my surprise when the same guy gets the top job at another company where I used to work. He obviously had an “in” with various investors, and the explanation I was given was “now that he’s a failure, he’ll know how to do better this time”.

This is a myth. REWORK quotes a study showing that people who lead companies that fail have the same success rate on their next company as those without any experience at all.

The second company closed 20 months later.

And now for a digression that I promise I’ll tie back together eventually.

On this trip I became aware of the Diaspora project to provide an open Facebook replacement. I didn’t read any of the stories completely due to travel, so I actually set aside time on Saturday to close my Facebook account and switch.

I actually like Facebook (we have an OpenNMS page), but lately having to opt out of all of the information sharing they want to do has become painful. The financial value of Facebook is in all the information about you that they have, yet they can’t monetize it unless it can be sold. Thus they want to share as much of your private information as they can get away with. I wouldn’t have as much of a problem with this if this had been stated upfront, but it feels a little like a bait and switch now.

I only connect via Facebook with old and dear friends. Almost all of them I’ve known since high school, and I use it to air out random thoughts, to make rude jokes, and to feel a sense of connectedness when I’m away from home. I never post anything online that I wouldn’t say in public, but the stuff I post on Facebook is usually something I’d rather keep amongst a small group, versus, say, my favorite public social network LinkedIn.

So imagine my disappointment when I found out the the Diaspora project didn’t really exist. My guess is that it will fail to unseat Facebook.

Please, before any of my three readers gets all upset and figures out how to use the comments section of this blog, I don’t want them to fail, but now the expectation has been set so high that they won’t be able to pull it off. In order to compete with Facebook, they’ll have to quickly get up to a large number of registered users, but operating on scale is hard. It took OpenNMS years to iron out the scalability issues we found with our software (and we are still looking for ways to improve it), but Diaspora will have to do it much more rapidly.

Facebook started out with a very limited deployment and slowly built up its application. Diaspora will have no such option. With such a bright spotlight on the project they will get mired down in trying to make the application perfect. No software can be made perfect, but now that important step of iterative growth will be removed. Heck, back in the 1.0 days OpenNMS used to actually die occasionally, much less monitor tens of thousands of devices, but our organic growth and obscurity let us fix those problems until is it extremely stable now.

And here’s the promised tie-in – Jason Fried summed the whole situation up nicely on his blog: they have too much money, the spotlight is on too early and expectations are too high.

He left off one thing that was mentioned in REWORK which was “Don’t Copy”. When you base your business or project on another’s work, you lose control. For example, all Facebook would have to do to stop a potential exodus over privacy would be to tighten the default privacy settings, or make it easy to “opt-out to all” by default. Probably less than a day’s worth of code and Diaspora can’t hit critical mass.

This does not mean I want them to fail – I would love an alternative to Facebook, especially an open one – but I have my doubts. This is one reason at OpenNMS we talk about things we’ve done, not what we are going to do.