Dilbert goes Open Source

In case you missed it…

Open Source Dilbert

–jeremy

Open Source: Locked Into Uncertainty

At times it seems like parts of Microsoft are legitimately trying to change. It’s hard to believe anything they say when you see things like this though.

The ad takes you to case studies from Microsoft, including one showcasing the State of Illinois’ email consolidation project. Utah did something similar back in 2002. Believe me, it’s not an easy job.

As you’d expect since it was a Microsoft case study, Illinois chose to consolidate an Exchange/Active Directory solution–they had different agencies using Exchange, GroupWise, and Notes. We were luckier–almost everyone was usin GroupWise and Novell directory–although there were lots of servers with out of date versions that had to be updated before we could install a meta-directory.

I wouldn’t fault any CIO for choosing Exchange. It’s the dominant email platform at this point and clearly the safe choice. What I do find a little interesting is that Illinois officials would go out of their way to help Microsoft create an anti-open source propaganda video. The two stars are Paul Campbell, Director of CMS (Central Management Services) and Tony Daniels, the agency’s Deputy Director. At one point, Daniels says:

“People say that open source doesn’t lock you into any one company, but when you think about it, it locks you into uncertainty.”

Daniels also says something about not having time for “science projects.” Did Microsoft write the script? Sadly, probably not. That’s probably what he really believes. When I became CIO for Utah, I found a culture that was ignorant and, in some cases, scared of open source. That’s probably not just true of state government, but any old-line business.

This brings up a good point. Microsoft is so pervasive in some places and spends so much money on FUD that some people actually think this way. But they think these things not based on reality, having tried Open Source or even factual information. It’s just a matter of what they know and are comfortable with. The work ahead for us is going to be long and arduous. It’s going to be a war of attrition. Changing a mindset, especially one not necessarily formed of facts, is not an easy thing. That being said I wholeheartedly think it’s a worthy challenge. Sure, Open Source has it’s flaws. Everything does. The pros still vastly outweigh the cons. Open Source truly has the power to open doors many didn’t even know existed. Education is going to be one of the keys here. I see that as one of the reasons we’re on the right track. When a more educated and more informed evaluation inexorably leads you in one direction, it’s in that direction I want to be headed.

–jeremy

Massachusetts Falls to OOXML as ITD Punts

From Andy Updegrove:

In a not unanticipated move, Massachusetts announced today that Ecma 376, the name given to the Microsoft Office Open XML formats following their adoption by Ecma, would be acceptable for use by the Executive Agencies of the Commonwealth. The announcement was made even as it appears more questionable whether the National Body members of ISO/IEC JTC1 will conclude that the formats are in suitable form to be granted standards status, and despite the fact that the ITD receive comments from 460 individuals and organizations during the brief comment period announced on July 5.

Most of those comments, “addressed revisions made to the Data Formats section [of the proposed changes to the Enterprise Technical Reference Model, or ETRM], specifically the inclusion of Ecma-376 Office Open XML as an acceptable document format for office applications along with the Open Document Format (ODF).” That number is several times the input received in connection with the original draft of the ETRM in August of 2005 that originally included ODF but not Microsoft’s OOXML.

The decision was posted today at the Information Technology Division’s Web site in a statement attributed to Henry Dormitzer, Undersecretary of Administration and Finance, Interim Commissioner, Department of Revenue, and Bethann Pepoli, Acting Chief Information Officer. That statement read in part as follows:

The Commonwealth continues on its path toward open, XML-based document formats without reflecting a vendor or commercial bias in ETRM v4.0. Many of the comments we received identify concerns regarding the Open XML specification. We believe that these concerns, as with those regarding ODF, are appropriately handled through the standards setting process, and we expect both standards to evolve and improve. Moreover, we believe that the impact of any legitimate concerns raised about either standard is outweighed substantially by the benefits of moving toward open, XML-based document format standards. Therefore, we will be moving forward to include both ODF and Open XML as acceptable document formats. All comments received are posted on this web site.

The “Fair and Balanced – let someone else decide” decision by the current administration and interim CIO Bethann Pepoli stands in sharp contrast to the positions taken by predecessor CIOs Peter Quinn and Louis Gutierrez, backed by then governor (and now-presidential hopeful) Mitt Romney. Both Quinn and Gutierrez insisted on including only “open standards” in the ETRM, and withstood significant pressure from Microsoft to give ground and accept OOXML prior to its adoption by ISO/IEC JTC1.

He ends the blog post with:

Massachusetts – or, more properly, a small number of courageous public servants – did something important two years ago when they took a stand for open formats. It is regrettable that their successors have seen fit to abandon that principled stance, even to the expedient extent of waiting a short while longer to see whether Microsoft’s OOXML formats will be found to be sufficient or lacking under the microscope of the global standards adoption process.

Unlike so many days before as the saga of ODF and OOXML has unfolded, this is not a day to be proud in Massachusetts.

I do find it odd that the ITD didn’t wait what is probably about a month or so to see how the ISO approval process went. Massachusetts defines an Open Format as follows:

“The Commonwealth defines open formats as specifications for data file formats that are based on an underlying open standard, developed by an open community, affirmed and maintained by a standards body and are fully documented and publicly available.”

It seems clear to me that OOXML does not meet this definition, arguably in multiple ways. Matthew Aslett points out some of the revisionist history that seems to be taking place at this point. As Andy points out, this is not an unanticipated move. That doesn’t mean it’s not disappointing though.

–jeremy

Email Call to Action

Mozilla recently made this announcement regarding Thunderbird.

Mozilla has been supporting Thunderbird as a product since the beginning of the Foundation. The result is a good, solid product that provides an open alternative for desktop mail. However, the Thunderbird effort is dwarfed by the enormous energy and community focused on the web, Firefox and the ecosystem around it. As a result, Mozilla doesn’t focus on Thunderbird as much as we do browsing and Firefox and we don’t expect this to change in the foreseeable future. We are convinced that our current focus – delivering the web, mostly through browsing and related services – is the correct priority. At the same time, the Thunderbird team is extremely dedicated and competent, and we all want to see them do as much as possible with Thunderbird.

We have concluded that we should find a new, separate organizational setting for Thunderbird; one that allows the Thunderbird community to determine its own destiny.

Mozilla is exploring the options for an organization specifically focused on serving Thunderbird users. A separate organization focused on Thunderbird will both be able to move independently and will need to do so to deepen community and user involvement. We’re not yet sure what this organization will look like. We’ve thought about a few different options. I’ve described them below. If you’ve got a different idea please let us know.

I agree with this post by glyn the more I think about it:

What’s worrying about this is that it seems to demonstrate a tunnel vision, where Firefox (and making money from it) are foregrounded above everything else. The fact is, email is a critical application, even if more and more people use Web-based mail (as I do – but I still use Thunderbird too). Moreover, Mozilla is a foundation, and that implies looking at the bigger picture, not concentrating – as a company might – on the success of its main “product”.

The open source world needs Thunderbird – indeed, the wider software community needs it. Although I accept that it lacks the community that Firefox has generated, that is not a reason to jettison it, and hope for the best. On the contrary: the very difficulties that Thunderbird has in firing up a community and in moving forward are precisely why the Mozilla Foundation should keep it under its wing.

It’s not the Firefox Foundation, but the Mozilla foundation. The Foundation having a big picture view is an important thing. It’s clear that Firefox and Thunderbird are much different beasts. The email space has way more competition than the web browser space. Add in the proliferation of web-based email and things get even more complex. It’s still not clear to me that completely dropping the project from the foundation is the best course of action though. It seems like something a corporation would have to do, not the Mozilla Foundation. Mitchell has outlined several options in her blog post. It will be interesting to watch which way the community leans as this moves forward.

–jeremy

Microsoft to Submit Shared Source Licenses to OSI

From a Radar post:

In his keynote at OSCON, Microsoft General Manager of Platform Strategy Bill Hilf announced that Microsoft is submitting its shared source licenses to the Open Source Initiative. This is a huge, long-awaited move. It will be earthshaking for both Microsoft and for the open source community if the licenses are in fact certified as open source licenses. Microsoft has been releasing a lot of software as shared source (nearly 650 projects, according to Bill). If this is suddenly certified as true open source software, it will be a lot harder to draw a bright line between Microsoft and the open source community.

Bill also announced that Microsoft has created a new top level link at microsoft.com, microsoft.com/opensource to bring together in one place all Microsoft’s open source efforts. Bill sees this as the culmination of a long process of making open source a legitimate part of Microsoft’s strategy. Open source has survived Microsoft’s process of “software darwinism” and is becoming an ever more important part of its thinking.

To expand on the announcement, it’s the Microsoft Permissive License (Ms-PL) and the Microsoft Community License (Ms-CL) that will be submitted, as the other Microsoft shared source licenses are fairly closed. I vaguely remember the FSF saying that these two licenses appeared to satisfy the four freedoms, so it’s at least a possibility that they will be approved by the OSI. So, what does this all mean? I’m still digesting it myself. It would seem that at least part of Microsoft is willing to accept the importance of Open Source in the future of software. It also means that at least parts are willing to join the conversation in a legitimate way. By going to the OSI for approval, Microsoft can no longer point at Open Source and say it’s cancer or will eat babies. I’m sure it took a lot of work internally to get this accomplished. Kudos for the effort. Will it matter? That remains to be seen. If they continue spreading patent FUD, then moves like this have far less impact than they otherwise would. It’s impossible to trust a company, even one that uses an OSI-approved license, when the other hand is doing many harmful things. It also remains to be seen how some developers will react if these get approved. Will either license get any usage outside of Redmond? If they don’t, then what’s the point of yet another Open Source license? More questions than answers in my mind right now, but this will be really interesting to watch play out. Stay tuned.

–jeremy

Open Source and the Future of Network Applications

There’s a lot to see at OSCON, so it should come as no surprise that you won’t be able to personally see everything you’d like to. I seem to have missed one of the most talked about events though.

“Tim has a television show under production where we get told in advance what we are going to say and how it will reflect Tim’s underlying idea,” Moglen told us. “I decided not to go with the program.”

Moglen’s performance turned into the stuff of legend.

Regrettably, we missed the assault. Stories needed to go out, and we assumed the chat would follow familiar, boring lines. After about ten people later asked if we caught the spectacular show, The Register contacted the OSCON audio staff to obtain a recording of the session. “No problem,” they said, “It will just take a couple of minutes, but you need to get O’Reilly’s permission first.” O’Reilly corporate refused to release the audio, saying it would cause a slippery slope. (We’re still trying to understand that one.) They, however, did add that Moglen appeared to be “off his meds.”

So what exactly happened?

Moglen attacked O’Reilly for wasting his time promoting Web 2.0 darlings, when he should be focusing on the core issues crucial to free software.

“I decided to say that we’ve reached a stage where we ought to be able to tell the difference between daily business news – X is up, Y is down – and the stuff that really matters, which from day-to-day is not racehorse X is running faster than racehorse Y.

“I think what time has done with this forum in general is to emphasize the trivial at the expense of the significant.”

According to published reports, Moglen described O’Reilly’s current approach to open source software as “frivolous.” He also chastised O’Reilly for chasing money, billionaire chums and “thermal noise” like Facebook.

“We still have serious problems to correct in public policies made by people propping up business models that were dying and wasting time promoting commercial products,” Moglen said, during the session.

As Stephen O’grady points out, you may not agree with the tactics Eben used (I also don’t), but the conversation is an extremely important one.

First and most obviously, this is a call to arms. Join us, pleads Joyent, before we trade one dictatorship for another. Underlying the recruiting attempt, however, are a set of implicit assumptions worth extracting.

1. Microsoft’s desktop dominance is threatened
2. The primary source of the threat is free but non-open source SaaS offerings from Google, MSN, Yahoo
3. The predicted outcome will see users forced to trade one dominant provider for another
4. Open source is the last, best defense against that future

Speculative and reactionary though these comments may be, they are reasonable enough in my opinion to be warrant further debate. But not here, and not now.

Suffice it to say, for time being, that the Joyent folks are not the only ones concerned by the prospect of future technology landscape dominated by the likes of Amazon, Google, eBay, Yahoo, et al. As evidenced by developments like Joyent’s decision and the GNOME Online Desktop efforts, it’s increasingly apparent that open source and Web 2.0 are on a collision course.

While these two dominant technical trends or directions have much to learn from each other, the convergence is likely to have its painful moments if OSCON is any indication. Indeed the talk of the conference was the somewhat shocking public swipe at Tim O’Reilly by one of the GPLv3’s chief architects, Eben Moglen. As documented elsewhere, Moglen absolutely dropped the hammer on Mr. Web 2.0, arguing that “that the FSF has ‘done the heavy lifting’ and ‘carried your water’ for the last decade, and that the era of Web 2.0 distraction (buzz about who is making money, who will get acquired, etc) will need to be replaced by a serious conversation about freedom.”

We’re still in the early stages of this discussion, but it’s encouraging to see that the right people are paying attention and the issues are slowly being iterated through. The right questions are starting to be asked. There’s still a lot to decide and much debate will surely follow, so if this is a topic that interests you (and it should be), make sure to join the conversation.

–jeremy

OSCON Executive Briefing II

(live blogging, so forgive the grammar and lack of proof reading)

Always Better

Matt Asay (Alfresco) and Mike Olson (Oracle via SleepyCat) discuss the value of source code. Mike argues that zero cost frictionless distribution is more disruptive than source access. A response from the crowd asked why he doesn’t close BerkleyDB. He didn’t get a chance to answer the question, but did give Matt a book.

The Path to IPO

Marten Mickos discusses how he hopes to grow MySQL AB to a billion in revenues. He covered how much the company has matured in the last few years (including items like: “we now invoice customers and have prices”). MySQL really aligns with PHP, but is “promiscuous when it comes to programming languages”. “Moore’s law will continues, but doesn’t apply to people” – MM. “The company you keep matters in Open Source” – TO. MySQL data seems to once again confirm that many people test OSS on Windows and deploy on Linux. Open Source will accelerate what is already happening to a product – bad ones will die quicker and good ones will get better faster.

Managing Linus Torvalds and other small challenges

Jim is covering the reasons that FSG and OSDL merged. He is also reflecting on what he sees as the future responsibility of the Linux Foundation, including what directions they should take and what pitfalls they should avoid.

Why Free Software values work for business

Mark discusses the relationship between the commercial Canonical and the non-commercial Ubuntu community. Mark sees collaboration as one of the key Open Source strengths. Launchpad is meant to take advantage of this and leverage collaboration as much as possible. Freedom of data is becoming increasingly important and Ubuntu/Canonical is committed to free data not only in launchpad (which will be Open Sourced soon), but throughout the project/company. “Driver support in Linux is probably one of the biggest reservations in Linux adoption” – MS. The following question was asked: “Can Ubuntu become bigger than Mark”. In essence, if Mark went away for whatever reason, would Ubuntu survive? This is clearly a question Mark has really thought about, up to and including Will provisions meant to ensure financial viability for the project.

–jeremy

OSCON Executive Briefing

OSCON, always a great conference, is officially underway. A few moments ago I got a sneak peak at ohlho, new open source guide of sorts. It allows you to tell it what stack(s) you use and gain valuable information from there. The amount of data displayed is already interesting and some compelling features are on the way. If you use Open Source it’s definitely worth checking out.

The radar Executive Briefing is resuming now, so expect more updates soon.

–jeremy

Microsoft development still broken, but they seem to be learning

Some recent information released by Microsoft seems to indicate that the Windows development model is still badly broke, and will be for some time, but will likely become less broken in the future. From the article:

Microsoft is planning to ship its next major version of Windows–known internally as version “7”–within roughly three years, CNET News.com has learned.

The company discussed Windows 7 on Thursday at a conference for its field sales force in Orlando, Fla., according to sources close to the company.

While the company provided few details, Windows 7, the next client version of the operating system, will be among the steps taken by Microsoft to establish a more predictable release schedule, according to sources. The company plans a more “iterative” process of information disclosure to business customers and partners, sources said.

“Microsoft is scoping Windows 7 development to a three-year time frame, and then the specific release date will ultimately be determined by meeting the quality bar,” according to the representative.

I’d have thought that Vista would have been proof that spending huge amounts of time to develop a huge product release is no longer the way to go. The fact that they will begin “a more iterative process” after the next release seems like an indication that they see the error of their ways, but that Vista just isn’t a good enough base to start from. After over five years of development, that seems a little odd. It’s also interesting to see that they are considering a subscription model, which is one of the most popular Open Source business models. Looks like Linux has quite a bit of time to iteratively improve until the next major Windows release. That’s a great thing for us, although I have to admit I’m a bit surprised.

–jeremy

The unforking of KDE's KHTML and Webkit

One of the core tenants of Open Source is the ability to fork. That being said, it should really be seen as a last resort type of option. It’s good to see that a couple of “unforks” have happened recently. A short time ago, Beryl and Compiz were able to come to an amicable resolution and rejoin as Compiz Fusion. More recently KHTML and WebKit look to be coming back together. From the article:

There is one major web rendering engine that grew entirely out of the open source world: KHTML is KDE’s web renderer which was built from the ground up by the open source community with very little original corporate backing. The code was good and branches were born as a result, the best known being Webkit. Now, after years of split, KHTML and Webkit are coming together once again.

Now, KHTML won’t be deleted right away since there are features in it that need to be ported into Webkit. For example, KHTML (in KDE 4) implements portions of the definition of the CSS3 standard, which will need to be adopted into Webkit and so forth. But the big deal is that the coders that invented the underlying layers that power Konqueror, some Nokia browsers, Abrowse, Safari, Adobe’s Air, and now Epiphany and a few other projects that are in the works, are now back in the fold. Additionally, Trolltech has announced that they are including Webkit in their upcoming Qt 4.4 release which means that a major, cross-platform toolkit now permits anyone to use the Webkit rendering engine where ever they need to render some HTML.

In open source terms, this may be as big of a deal as the gcc and egcs merger of yonder days. KHTML and Webkit are definitely coming of age. The KDE developers, responsible for the original creation of KHTML, are dedicated to seeing this unforking happen and are taking a leading role in that effort.

The uptake of WebKit has been fairly significant. The integration into QT will only serve to accelerate its adoption. It should be interesting to see how KDE deals with the component being outside their direct control, as WebKit is an Apple project (although obviously a fully Open Source one). It looks like some of the KHTML devs will be moving to become WebKit devs, which is great.

–jeremy