Microsoft has had some exceptional people driving its open-source strategy over the years.
Now, with Sam Ramji, senior director of platform strategy and Microsoft's point man on open source, officially leaving for a Silicon Valley-based start-up at month's end, Microsoft has the opportunity to select someone who will ramp its open-source engagement to the next level.
Should Microsoft choose a pragmatist or an anarchist?
Sam Ramji
It's a provocative question, but one that becomes easier to answer when you consider the state of open source at Microsoft and how its various open-source leaders have managed it.
Initially, it was Jason Matusow who took the bullets for Microsoft (and protests/pickets) as it cut its teeth on open-source engagement. Later, Bill Hilf took the reins and moved Microsoft's open-source involvement from discursive engagement to practical deployment: the company opened its open-source interoperability lab, and Hilf lobbied to partner with a variety of open-source companies.
Then came Ramji, who brought open-source credibility to his role at Microsoft, having used it extensively at a previous start-up. Ramji helped to kick off CodePlex, Microsoft's open-source code hosting site and has actively educated Microsoft on open source as much as he has worked with the open-source community to understand Microsoft. (Ramji is also becoming interim president of Microsoft's newly created CodePlex Foundation.)
Microsoft, as Hilf explained Thursday in announcing Ramji's departure, is far more advanced in its open-source activities than it once was, which suggests the ideal replacement for Ramji:
The perspectives on OSS at Microsoft have evolved to the point where Microsoft's open source strategy is no longer just locked in a single 'lab' on campus - now OSS is an important part of many product groups and strategies across the company. We have become increasingly clear on where we work with open source - development methodologies, projects, partners, products and communities - and where our products compete with commercial open source companies or platforms. Today, there are engineering and business leaders across the company, myself included, looking at how to drive interoperability for customers and as a lever for new growth.
Open source is, in other words, increasingly part of the standard fabric of Microsoft's technology and business strategy. As such, it doesn't need a missionary so much as a diplomatic, pragmatic messenger to discover areas within the company where open source can take greater root and to engage with the community outside Redmond.
Microsoft doesn't need a talking head, someone to fill panels at every open-source conference and pontificate on the immaculate conception of open-source code. Rather, it needs someone to help motivate Microsoft's rank-and-file to get involved in such events and to intelligently explain Microsoft's diverse and sometimes seemingly contradictory positions on open source--a fact that shouldn't be surprising to anyone who has worked at a big company.
Microsoft doesn't need a Che Gates, someone who believes open source is The One True Way and is afflicted with the unhealthy and unhelpful Microsoft-hating disease. Such a person will never be heard within Redmond and rightly so: the world has already figured out that open source is a powerful means to develop and distribute software, but it's not the cure for global hunger.
Rather, Microsoft needs a thoughtful mediator to deepen its engagement with the wider open-source community while continually reminding its employees to consider open source in product and business decisions.
In short, Microsoft needs someone who can credibly advocate for open source without being consumed by mindless rhetoric. Someone, in other words, very like Matusow, Hilf, and Ramji, but probably with a shorter Microsoft tenure (similar to Ramji). Any ideas? Send them to Hilf.
To end on a personal note...Sam, you have been incredibly generous to me, usually when I least deserved it. You have been patient and forbearing. I think the world of you. Your new start-up is lucky to have you. The only area in which you failed is I can't remember a single Arsenall ticket being sent my way. But we all have failings. :-)
Follow me on Twitter @mjasay.
(Credit:
Microsoft)
Microsoft, long the bastion of proprietary thought, is increasingly adding open-source DNA to the fold. And it's adding to its roster of open-source veterans: Dick Hardt, founder and CEO of Sxip Identity and ActiveState, announced on his blog earlier this week that he will be joining Microsoft:
I will have the title Partner Architect and will be working on consumer, enterprise and government identity problems. My open source, open web and digital community experience will continue to guide my thinking. For me, this is an opportunity to work on the identity problems I have been toiling over for the last six years, but now with massive resources.
Hardt insists that this isn't a sell-out move (He likely doesn't need the money, having sold ActiveState to Sophos a few years back), arguing that he "was recruited to Microsoft because (he is) an independent thinker." He's probably right. Microsoft has been seeking to bring more contrarian outside counsel into the company in the past year or two. The fact that Hardt won't "fit right in" is probably a big selling point to his hiring manager.
As noted above, Hardt won't be alone. Microsoft now employs Bill Hilf, former Linux technical strategist for IBM; Sam Ramji, a former executive at Ofoto which was a heavy user of open source; Bob Duffner, another IBMer who worked with its open-source Gluecode acquisition; Rob Conery, founder of MPL-licensed SubSonic; Tom Hanrahan, former technical lead at the Linux Foundation; Daniel Robbins, former chief architect of Gentoo Linux; and more.
It's a clear trend, though clearly these hires constitute a tiny minority of total Microsoft employees. Even so, "a little leaven leavens the whole lump," to quote Paul's words to the Galatians. Here's hoping that Hardt and the others will continue to make headway within Microsoft on open-source issues.
News on Hardt first found via Mary Jo Foley at ZDNet.
Steve Ballmer may not have anything better to say than "blah" and "Google" in his analyst meetings, but his open-source group came up with a doozy today.
The flawed Open Specification Promise (OSP) just became whole. Or close to it. Microsoft has opened up its Open Specification Promise to make it meaningful and usable to a wider group of people. Even Groklaw, which sets a high (and generally fair) bar for Microsoft is impressed.
Microsoft's OSP has been controversial in part because it's basic covenant not to sue developers was crippled by its application only to noncommercial developers, as well as other ambiguities that have been resolved. With this update to the OSP, this restriction is gone, as Sam Ramji, Director of Microsoft's Open Source Software Lab, confirmed:
Microsoft is putting a wide range of protocols that were formerly in the Communications Protocol Program under the Open Specification Promise (OSP). This guarantees their freedom from any patent claims from Microsoft now or in the future, and includes both Microsoft-developed and industry-developed protocols.
... Read More
When I texted Sam Ramji to let him know about Sandcastle, and he quickly texted back that he would look into it, I figured that a) it hadn't yet hit anyone's radar at Microsoft and b) that he'd fix it.
Fix it, he did. As Mary Jo Foley notes, it was "doubtful [that] Microsoft was willing to risk the wrath of the OSI over a documentation compiler." I'd go one step further. Once alerted to Sandcastle's violation and to the importance thereof, it was doubtful that Microsoft's Sam Ramji and Co. would be interested in the code, however important/non-important it might be.
Sam gets open source. He's not always supported in this understanding by the larger Microsoft entity, but Sam gets it. His apology to the OSI is direct, concise, and appropriate:
This is unacceptable and represents a violation of Microsoft's Open Source policy. I take it extremely seriously.
I have directed the project to be unpublished from Codeplex immediately, including removal of the project's use of the Ms-PL. If the team chooses to publish the source code and follow Microsoft policy, then the project may be re-published in the future. If not, we will remove all references to Sandcastle from Codeplex.
... Read More
Sam Ramji just got a promotion: Sam will now be running Microsoft's worldwide open-source and Linux team (roughly 120 people and counting).
Sam had been the director of Microsoft's open-source software lab. In this new role, he'll continue to oversee the lab but also take on a more strategic role within the company (and, by extension, within the industry).
I've known Sam for a few years now, and both like and respect him. We've had enough disagreements for me to know that while he's an active open-source proponent, he's not easily swayed by anemic reasoning (for or against Microsoft). He's a guy who recently told me that he has run Office 2003 and World of Warcraft on CrossOver (WINE) on Ubuntu (verdict: performance "not too bad"). He has an open-source-friendly background.
Sam's promotion is good for Microsoft. It's also good for open source, as I see him as a credible, earnest advocate for open source within Microsoft. He has earned his stripes within commercial and community-based open-source projects. I've heard some of open source's oldest advocates praise his name.
Let the constructive dialogue begin (or, rather, continue).
- prev
- 1
- next
