Port 25: The Open Source Community at Microsoft : sam ramji, Industry Conferences

The Linux Foundation's Collaboration Summit

Peter Galli — Thu, 23 Apr 2009 14:00:00 GMT

A lot has been written by the press and blogosphere since the Linux Foundation's annual Collaboration Summit was held earlier this month, particularly about the panel that included Microsoft's Sam Ramji, Sun Microsystems' Ian Murdock, and Linux Foundation executive director Jim Zemlin.

The panel was entitled "Why Can't We All Just Get Along," which struck me as not only divisive, but also a little outdated given the level of collaboration that already takes place between proprietary and open source software vendors alike.

For example, Microsoft and Sun already have a long-standing working collaborative relationship; Microsoft also has a technical collaboration agreement with Novell, an agreement with Red Hat to test and validate our respective server operating systems running on one another's hypervisors, and a number of arrangements in place with other open source companies.

The panel discussed this in greater depth, looking at how collaboration, cooperation and competition exist: not just between proprietary and open software vendors, but also between Linux and open source ones.

This prompted panel moderator Zemlin to suggest that the three make an even greater effort come together and collaborate where it makes sense.

Interestingly, the Summit also spurred renewed discussion about whether there need to be more critics in the Linux community, with one blogger taking Zemlin to task for what he described as the "tall claims" he made at the Summit.

Ramji, the Senior Director of Platform Strategy at Microsoft, also used the panel to remind the Linux and open source communities of his offer for them to reach out to him and others within Microsoft and share their frustrations, problems and issues, so that they could be better educators and advocates on this front across the company.

Ramji also, again, stressed that Microsoft's customers want interoperability with open source software, including for PHP on Windows, but that making this happen sometimes took time.

Sun's Murdock seconded this, talking about internal inertia and how Sun also had had to deal with hearing from customers and developers that they wanted interoperability with technologies other than their own.

At Microsoft, there are cross-group, company-wide open source discussions and initiatives underway, with each group given the autonomy to decide for itself how this plays out with regard to their product set and business model.

While Port 25's mission is to be the voice of the open source community at Microsoft, it is far from the only voice on this topic. There have been blogs across the company on open and interoperability initiatives, from groups including security, Live and the Mac Business Unit, to name just a few.

It is also important to remember that Ramji and other executives like Bob Muglia, the president of Microsoft's Server & Tools business, have often said that open source is a journey that Microsoft is on and that much more needs to still be done. Many groups across the company are already responding to that call.

Open Source Interoperability Projects

Jean Paoli — Fri, 07 Nov 2008 07:21:00 GMT

Interoperability has always been a focus area at Microsoft. Being a platform company, Microsoft has engaged in interoperability at many levels - product features, participation in standardization bodies, publishing many technologies under open licenses and working closely with customers, governments and partners to understand the heterogeneous IT landscape and discuss practical interoperability solutions.

Earlier this year, these activities were formalized under the Interoperability Principles for all of our high-volume products.

I am the General Manager of Interoperability Strategy at Microsoft, and I have worked across the company on many interop initiatives. I am happy to see many interop projects now coming out of Microsoft and, personally, having many of them based on XML makes me doubly happy.

My team has built several bridging technologies and solutions for many of our products to enable interoperability. These are being run as open source projects and released under a broad BSD license so that our customers and partners can use them in many open and broad scenarios.

Interoperability has been getting enhanced attention at a lot of conferences lately and Microsoft has also upped its participation at many open source conferences such as OSCON, the Eclipse Conference and ApacheCon.

At Microsoft's Professional Developer's Conference last month, the interoperability story was part of almost every announcement and keynote address. As Sam Ramji writes in his latest blog, Microsoft is also participating at ApacheCon and highlighting the interoperability work we are doing. These are indeed exciting times!

On the interoperability front, my team has been working with the WSO2 since the TechEd 2007 Conference to demonstrate interoperability using our StockTrader reference application.

This week, the WSO2 proposed a new Apache incubation project, known as Stonehenge, to further this work. The aim of this project is to set up sample applications to demonstrate interoperability with multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We look forward to working with WS02 on the scope of this project, and having discussions with the community.

I also want to highlight some open source interoperability projects that my team has been working on with third parties, companies and members of the community at large, which may be very relevant to the readers of this blog.

Eclipse Tools for Silverlight

Eclipse4sl allows Java developers to develop code for the Silverlight platform within the Eclipse development environment, and contains both an advanced project system for creating Silverlight applications and media experiences as well as a compiler for packaging Silverlight applications for deployment.

Interoperability with the Azure Services platform

Announced at PDC recently, the Azure Services Platform is an internet-scale cloud computing and services platform hosted in Microsoft data centers. It provides an operating system and a set of developer services which can be used individually or together. Microsoft .NET Services is a key component of the Azure Services Platform that offers a set of Microsoft-hosted, highly scalable, developer-oriented services that provide the key building blocks, like, Access Control, Service Bus, and Workflow service.

The Azure Services Platform, built from the ground up to be consistent with Microsoft's commitment to openness and interoperability and in that spirit, we have built two cross-platform SDKs for .NET services - for Java and Ruby.

Information Cards Interoperability

Windows CardSpace is Microsoft implementation of Information Cards on the Windows platform. Information cards are a core part of Identity Metasystem and help both site owners and visitors to manage, control, and exchange digital identities more safely and consistently.

We have also built four open source projects that help Web developers support information cards on diverse platforms:

OpenXML-ODF translators

The goal of this project is to provide translators to allow for interoperability between applications based on ODF (OpenDocument) standard and Office Open XML standard. The translator is based on XSLT transformations between two XML formats, along with some pre- and post-processing, and is available on Sourceforge under a BSD-like license.

OpenXML-UOF translators

The goal of this project is to provide translators to allow for interoperability between applications based on UOF (Uniform Office Format) standard and Office Open XML standard.

UOF is an emerging standard, which is being developed by the Chinese Office Software Work Group (COSWG), led by the China Electronics Standard Institute (CESI), the Ministry of Information Industry (MII), major suppliers of Chinese office software suites, and other academic institutions.The translator is based on XSLT transformations between two XML formats, along with some pre- and post-processing. It is available at SourceForge under a BSD-like license

I would like to hear your comments and feedback on these projects and also welcome open engagement on what Microsoft should be doing for interoperability. Tell us what other interoperability scenarios we should be looking to address.

I also want to thank the multiple third party companies and the community members we cooperate with, as well as the members of my team: Vijay Rajagopalan, Sumit Chawla, Kamaljit Bath, Claudio Caldato, Jean-Christophe Cimetiere and many others for working on these projects and building technical solutions for interoperability with key Microsoft products and technologies.

struct.new("future", :open, :microsoft)

Sam Ramji — Thu, 06 Nov 2008 08:49:00 GMT

I delivered the keynote at ApacheCon in New Orleans today, where I talked about some of the new milestones we have chalked up on the journey inside Microsoft towards greater participation and growth with open source communities, and our strategy of "architecting for participation."

This strategy focuses on four significant themes: community; contribution; partnerships; and choice. Microsoft believes that the next ten years of software will be a time of growth and change where both open source and Microsoft communities will grow together.

We also believe that in an increasingly interconnected world, where more people have a greater opportunity to use more technology to do more things than ever before. We support those choices and are expanding interoperability between open source technologies and Microsoft technologies.

So, on the interoperability front, we have been working with the WS02 since our TechEd 2007 Conference, to demonstrate interoperability using our StockTrader reference application. Today, the WS02 announced they would build an open source version of the sample application under "Project Stonehenge," which hs been proposed as a new Apache incubation project.

WS02 will use the project to set up sample applications that demonstrate seamless interoperability across multiple underlying platform technologies, using currently defined W3C and OASIS standard protocols.

My team has been working closely with that of Jean Paoli, the General Manager of Interoperability Strategy at Microsoft, whose team is driving much of this interoperability work. You can read more about all this in Jean's blog post.

Microsoft has also decided to move the development of protocol parsers for Microsoft Network Monitor - a free protocol analyzer and network sniffer - to an open source model, on CodePlex, which will host the development of parsers for public protocols and for protocols described in our Open Protocol Specifications for Windows.

An updated parser package has been released and a source tree created on Codeplex. We want Netmon to be the best-of-breed tool for network monitoring at Microsoft, not just for Windows.

Microsoft also recently joined the AMQP Working Group as a participant, with the goal of contributing towards the development of the specification and to enable greater customer choice in the marketplace.

At the request of community members, we have now committed to participate in the Apache Qpid project, a widely adopted open source implementation of the AMQP specification that addresses the customer need for choice and improved messaging interoperability.

Our customers are telling us that they would like to see the Apache Qpid project extended to interoperate with Windows, so the next few months of participation will be focused on understanding the community's effort to build Windows based AMQP software.

Participation will give us the opportunity to learn from other project participants, so that we can be in a position to consider making a valuable contribution. But it is important to note that the Apache Qpid project is just one of many AMQP specification implementations, and we are open to supporting additional projects.

You can read an interesting technical research paper from Ohio State University analyzing the performance of the Qpid implementation of AMQP here.

Microsoft also announced, at PDC 2008, our commitment to include "Oslo" - an upcoming set of technologies for modeling - in the Open Specification Promise. This will ensure that the "Oslo" declarative modeling language, codenamed "M", is interoperable with prominent industry standards such as WS* specifications, XML formats, industry protocols, and security standards.

Two of the core focuses for Oslo are integration and interoperability. As such, it will integrate with next-gen Microsoft technologies, including System Center, Visual Studio and BizTalk Sever. We also plan to work with partners and the industry, so as to make Oslo interoperable with important standards and industry protocols.

One of the key ways we think customers will achieve customization for their platforms is through the use of textual and visual DSLs, which can be written uniquely by the developer for vertical industries and specific domains, or they can use pre-existing DSLs in these same scenarios.

The hope is that we will establish a broad and open ecosystem around "M" that will enable customers to bring the power of model-driven applications and systems to their heterogeneous environments.

Finally, on the Live Search front, the Powerset team recently resumed its participation with HBase, which is elated to infrastructural storage technology enabling large scale data processing.

The HBase project receives significant lift from the active community that supports the project, and Powerset's continued participation on HBase could allow us to accelerate the integration of Powerset's technology into Live Search, resulting in improvements to the end-user experience.

So, stay posted. There's a lot more to come!

Supernova

Sam Ramji — Wed, 19 Mar 2008 16:22:00 GMT

I’m writing this from EclipseCon in Santa Clara, California, where I’m going to announce the beginning of Microsoft’s collaborative work with the Eclipse Foundation.

This started about a year ago when I met Mike Milinkovich at an open source event (the Open Source Software Think Tank 2007) where we were seated at the same table, and assigned to discuss “key issues inhibiting the growth of open source”. We found we had pretty similar ways of looking at problems – I found Mike to be very pragmatic and straightforward in his thinking. That discussion led to a conversation about what we could do to help Eclipse developers building software for Windows.

At the same time, the CardSpace team at Microsoft was already working actively with the Higgins Project to establish a secure, interoperable framework for user identity on the web – an architecture known as the Identity Metasystem. Since the inception of Higgins, the CardSpace team has worked very closely with the Higgins team, providing them the protocol documentation they needed to be able to build an identity selector that is interoperable with CardSpace, as well as placing those protocol specifications under the OSP so that they knew that it was safe to do so. We share a commitment to building a user-centric, privacy-preserving, secure, easy-to-use identity layer for the Internet.

Currently, Higgins, Microsoft, and dozens of other companies and projects are in the midst of the third OSIS-sponsored user-centric identity interop, where we all try our code together, providing the data needed to improve both our implementations and the interoperability between them.

Among a range of other opportunities (which we’re still working on), we discovered that Steve Northover (the SWT team lead) had gotten requests to make it easy for Java developers to write applications that look and feel like native Windows Vista. He and a small group of developers built out a prototype that enables SWT to use Windows Presentation Foundation (WPF). We’re committing to improve this technology with direct support from our engineering teams and the Open Source Software Lab, with the goal of a first-class authoring experience for Java developers.

This is exciting to me – as a Java developer in my prior life (as well as the first technical marketing manager for BEA’s WebLogic Workshop, now Apache Beehive) it just makes sense to enable Java on Windows. We started a collaborative effort with JBoss two years ago that continues to this day. At the end of the day, it’s all about the developer. There will be more to come from the conversations that Eclipse and Microsoft have begun, and I look forward to announcing those in the future as we have demonstrable technology results.

Cheers,
Sam

Gapingvoid Got It Wrong

Sam Ramji — Thu, 19 Apr 2007 18:18:00 GMT

A few key people in the industry (Stephen Walli and Matt Asay in particular) pointed out the flaws in Hugh Macleod’s strip on Open Source. I like the Blue Monster idea (there’s some real passion in that art) but this one missed the mark, because Hugh framed the issue wrong. Hugh is clearly a smart guy and is in the process of learning about this field of software. The resulting discussion on Hugh’s blog was quite productive thanks to multiple viewpoints – including members of the Microsoft ecosystem that we are serving today.

However, Hugh’s approach is not in line with Microsoft’s strategy.

Here is my attempt to get the conversation on the right track by providing our official viewpoint:

There is a basic problem when people frame “traditional software vs. open source software” – the assumption that there is a zero-sum game to be played and that therefore it is war.

This is a mistaken understanding. Software is technology. It can be delivered as a product or as a solution. It must meet the needs of its users. Users come in different segments as defined by their needs and their ability to communicate with each other about the technologies they are using.

This may seem obvious, but segments vary! High-level, simplistic discussions of “A vs. B” miss the reality that there are different right answers – and sometimes multiple right answers – for any given segment.

I have personally heard – among other places, at the Open Source Software Think Tank 2007 – enterprise CIOs state exactly this: “I don’t have time for science experiments.” I believe this was Max Rayner, CIO of SurfControl. You can take that quote as disparaging open source, or you can include the context of the statement, which is this: enterprise CIOs are looking for technologies that solve their problems. Their definition of the problem includes long-term viability, mission-critical support, and interoperability with their other technologies. So what this quote means is “if you have a technology for me – open source or not – you have to provide for my key concerns.” Companies like Novell, Red Hat, JBoss, and MySQL have built businesses based on meeting these needs. This is reality. It is foolish to label these companies and their customers, users, and community as playing with things that are “not proven” or “science experiments”.

This is not a war. This is about technology.

It’s only a war when we hold on to hunter-gatherer era tribal mentalities and say “Our way is good! Their way is bad!”

It turns out there’s a non-zero-sum game to be played here by working together, communicating intelligently, and thinking through the details. But it will never happen while we hold on to old, fuzzy ideas about competition and tribalism.

Socialpoint - Socialtext on Sharepoint a conversation with Ross Mayfield

Sam Ramji — Wed, 01 Nov 2006 21:15:00 GMT

I got to spend an hour with Ross Mayfield (founder of Socialtext) today. We talked about a range of things, from open source calculators (WikiCalc) to the future of Sharepoint as a platform for open source development and the shift in Microsoft's approach to open source. Ross graciously gave us an extra ten minutes to capture part of our conversation on video.

Socialtext was the first commercial wiki company, built initially on the Perl-based Kwiki and Ross has been a leader in the democratization of this collaboration technology for many years. For more on social computing, you can check out Wikipedia. By now, unless you work with a group of card-carrying Luddites, you have probably even browsed a wiki within your company run by your own IT department or wiki enthusiasts. In this case you’ve already entered the current wave of “enterprise social computing” a.k.a. “Enterprise 2.0”. Our internal wiki at the Open Source Software Lab currently runs on Plone.

About five months ago, he open-sourced part of this platform. The Socialtext Open Source Wiki has the details on this project. It currently runs on PostgreSQL and Ubuntu… but since it’s based on Perl I hope that the porting effort to SQL Server and Windows wouldn’t be too much.

Even more interesting to me given my role at Microsoft is that Socialtext has built a Sharepoint integration ("Socialpoint"). This gives Sharepoint users access to a best-of-breed wiki and blogging engine while retaining presence, Office integration, and a unified portal infrastructure. My inner geek got going when Ross described the new protocol handler they’ve built - "socialpoint:foo/bar" - for navigating within Sharepoint across wikis. I think this is a good example of how Microsoft platform software should be combined with open source applications. We continue to invest in scaling the infrastructure, and open it up to developers for innovative applications that can change as often as customers require.

Ross is thinking about releasing these modules under open source licenses. I’m hopeful that the MS-PL (BSD-like) or MS-CL (Apache-like) will prove worthwhile to him, and that Codeplex will turn out to be the right repository for the work - but regardless of the license or the community site, I'm excited to see that the Microsoft platform and open source software companies can propel great technology into broad adoption - carrying innovation into remote corners of the enterprise.

For more details on the conversation - and to catch Ross' insights first-hand - check out the video interview.

Cheers,

Sam

Video: Socialpoint - Socialtext on Sharepoint a conversation with Ross Mayfield

Alternate Video Format

-Download MPEG4 Video