Archive for the ‘Open Standards’ Category

Meet the team that is collaborating on open source projects at the MS Open Tech Hub

July 19th, 2012 No comments

From Jean Paoli

Since we launched Microsoft Open Technologies, Inc. (MS Open Tech) as a subsidiary, project ideas have poured into our team from inside and outside the company as we shipped many open source projects and participated in many open standards activities.

After a few months of existence I want to provide you some insights on how we are functioning internally: we are working on many projects and are hiring ten full time employees: we are hiring developers, technical program managers, standards professionals and  technical evangelists! We will be posting the jobs descriptions in a few weeks (and will update this blog with a link to apply).

We have also been thinking about how to scale in order to be able to work across the many projects that could be interesting to MS Open Tech, Microsoft, and to the industry as a whole.

I am pleased today to introduce the MS Open Tech Hub (the Hub):

We created the Hub as new engineering program for MS Open Tech engineers: It is a collaborative place to build open source projects, exchange and evolve open source engineering best practices, and marshal and temporarily assign resources from Microsoft to MS Open Tech (in addition to MS Open Tech full time employees) based on the needs of specific projects.


As the photograph above shows, the entire MS Open Tech team is excited and energized around the announcement of the Hub.

The number one goal of the Hub is to build, accept contributions or contribute to open source projects. Based on the needs of open source projects, engineering resources from Microsoft teams may be temporarily assigned to MS Open Tech to participate in the Hub, where they will collaborate with the community, work with the MS Open Tech full time employees and contribute to MS Open Tech projects. This collaboration will further help us exchange and evolve open source engineering best practices for open source.

The goal of the MS Open Tech Hub is to create a pool of talent where developers, testers, architects and others push boundaries, explore the toughest questions, and advance our investment in openness. The Hub brings together some of our best and brightest engineers to join together, work with the open community and toward the ultimate goal – building, accepting and contributing to interoperability, standards and open source projects.

For example, the Entity Framework team joined the MS Open Tech Hub, and brought today’s open source Entity Framework project to life. This team was able to quickly organize engineering and open development resources to be ready to start collaborating with the open source communities. EF will join the other open source components of Microsoft’s dev tools and frameworks – MVC, Web API, and Web Pages with Razor Syntax – to help increase development transparency for this project.

Get to know our team and find out what they like about collaborating in the Hub.

We’ve learned through the years that great ideas happen when smart, passionate and creative people come together in a collaborative environment that enables new ideas to flourish.

A few photos of a typical day in the MS Open Tech Hub






Jean Paoli
Microsoft Open Technologies, Inc.
A subsidiary of Microsoft Corporation

Announcing one more way Microsoft will engage with the open source and standards communities

April 12th, 2012 No comments

In case you missed it, I just wanted to flag this blog from Jean Paoli:

I am really excited to be able to share with you today that Microsoft has announced a new wholly owned subsidiary known as Microsoft Open Technologies, Inc., to advance the company’s investment in openness – including interoperability, open standards and open source.

My existing Interoperability Strategy team will form the nucleus of this new subsidiary, and I will serve as President of Microsoft Open Technologies, Inc.

The team has worked closely with many business groups on numerous standards initiatives across Microsoft, including the W3C’s HTML5, IETF’s HTTP 2.0, cloud standards in DMTF and OASIS, and in many open source environments such as Node.js, MongoDB and Phonegap/Cordova.

We help provide open source building blocks for interoperable cloud services and collaborate on cloud standards in DMTF and OASIS; support developer choice of programming languages to enable Node.js, PHP and Java in addition to .NET in Windows Azure; and work with the PhoneGap/Cordova and jQuery Mobile and other open source communities to support Windows Phone.

It is important to note that Microsoft and our business groups will continue to engage with the open source and standards communities in a variety of ways, including working with many open source foundations such as Outercurve Foundation, the Apache Software Foundation and many standards organizations. Microsoft Open Technologies is further demonstration of Microsoft’s long-term commitment to interoperability, greater openness, and to working with open source communities.

Today, thousands of open standards are supported by Microsoft and many open source environments including Linux, Hadoop, MongoDB, Drupal, Joomla and others, run on our platform.

The subsidiary provides a new way of engaging in a more clearly defined manner. This new structure will help facilitate the interaction between Microsoft’s proprietary development processes and the company’s open innovation efforts and relationships with open source and open standards communities.

This structure will make it easier and faster to iterate and release open source software, participate in existing open source efforts, and accept contributions from the community. Over time the community will see greater interaction with the open standards and open source worlds.

As a result of these efforts, customers will have even greater choice and opportunity to bridge Microsoft and non-Microsoft technologies together in heterogeneous environments.

I look forward to sharing more on all this in the months ahead, as well as to working not only with the existing open source developers and standards bodies we work with now, but with a range of new ones.