Port 25: The Open Source Community at Microsoft : Codeplex, ~FeaturedPost

Part 2: Lessons I Learned as a Project Manager Converting to Agile

saraford — Tue, 20 Oct 2009 21:11:00 GMT

In my first post for this series, I stated that "Agile is the single greatest things a team could do to significantly improve the user experience and quality of their website" and "not designing the full 100% is a true blessing in disguise." By putting these two concepts together, you can fully embrace the power that is Agile: Course Correction.

Making Design Changes in Waterfall

In the traditional waterfall, a Program Manager writes a specification, in which all members of the team and the associated business owners review and approve. Then, the development cycle begins to code to the specification word for word. Once code complete, the test team takes over reviewing the code to ensure it matches the specification.

But, what if half way through, someone on the team realizes the specification is wrong? Or more practically, what if the requirements change sometime during development? In my Microsoft experiences, this is called a Design Change Request (or a DCR), and it is extremely costly. New designs need to be made and reincorporated with the rest of the specification. Dev needs to re-code the feature. And the test team has to restart any prior testing, especially for regressions. In other words, DCRs are not good things.

Making Design Changes in Agile

One of the light bulb moments for me on CodePlex.com was accepting the fact that Agile is really just a series of mini waterfalls. Instead of designing a waterfall release cycle that will span the course of several years, you're only designing for a waterfall process of a few weeks. There's a Planning Phase, a Development Phase (which encapsulates the Test Phase, but is beyond the scope of this blog post), and the Deployment Phase. It's waterfall, but waterfall moving at an incredibly fast pace.

Now let's reconsider those Design Change Requests, but on an Agile team. The work is very, very scoped, which implies less ambiguity. (Yes, you could have a perfect specification that isn't ambiguous at all, but if that spec is 60 pages, the risk of human error is higher. Trust me, I've seen this, where I was the human in error.) And, recall that you're only doing 80% of the work. The cost of the design change is already accounted for in the remaining 20% of the development cycle. In other words, it's in the spirit of Agile that you're going to make changes along the way to better the product, or "course correct," as it was initially described to me. In agile, DCRs are good things.

Regardless whether you discover that you need to make a course correction during the Development Phase or the Deployment Phase, it's okay because Agile by its very nature can adapt and respond to these changes quickly.

An Example of Course Correction

Below is a screenshot from the original ratings and reviews designs. Notice how I circled the downloads count.

During implementation, a developer realized that the download count could be confusing. Did it mean total downloads for the entire project, total downloads for the release, or just recent (past 7 days) downloads for the release? We realized that given these designs we couldn't really convey the information we felt necessary to provide the right user experience to our visitors. So, we went back to the design and made a few tweaks. Again, we weren't trying to completely redesign the project directory. Even if we wanted to, there was no time to do anything radical. At the time the developer noticed this issue, we were going to finalize the build for deployment in a little over a week.

What we did instead was "course corrected" by making slight changes to the project metadata on the left-hand side to finish the current feature (or user story, if you're more aware of that terminology). Circled below is the metadata we added. We also added the * next to the number of page views and downloads, where we state at the bottom of the page "in the past 7 days."

Aside: CodePlex shows past 7 days data as a way of reinforcing release early, release often, which we continue today in the project directory. The screenshot below was taken at the time of this writing.

Conclusion of Part 2: Course Correction

This concludes my second post on Program Managing an Agile team.

If you like what you see, let me know! And if you don't like what you see, please don't hesitate to let me know. Seriously, I love discussing my Love / Hate Relationship with Agile development, as depicted on my personal blog.

Up Next: Putting it All Together - How the CodePlex team Builds Software

Sam Ramji is leaving Microsoft

billhilf — Thu, 10 Sep 2009 17:47:00 GMT

It's been a while since I made an appearance on Port25. I felt it was important to provide some thoughts to the Port25 community on Sam Ramji's impending departure from Microsoft.

After many years helping to carry the open source software banner for the company, Sam is leaving Microsoft at the end of this month. You may have also heard that he has accepted the position of interim President of the CodePlex Foundation as well as a leadership position at a startup in California. (I'll let Sam and his new company share more details there.)

Sam joined my team three years ago to drive open source technical strategy. I have eagerly supported him as he passionately articulated a vision that Microsoft could coexist - and even thrive - in a heterogeneous IT world.

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.

And, because we recognize the importance of having that strong internal advocate for open source, we are actively seeking someone to fill Sam's shoes at Microsoft.

We will not waver in our commitment to open source.

To my friend Sam: Best of luck to you and your family as you move on to your next great adventure, and THANK YOU for all of your efforts and passion.

The CodePlex Foundation Debuts

Peter Galli — Thu, 10 Sep 2009 16:30:00 GMT

Many of you will, by now, have heard about the formation of the CodePlex Foundation. In order to give you an in-depth look into the thinking behind Microsoft sponsoring the Foundation, I talked to Bill Staples, the General Manager for the Web Platform and Tools Team at Microsoft, a member of the interim CodePlex Foundation board and whose engineering team builds the Microsoft Web platforms.

"Before we dig into the details of the CodePlex Foundation, it is important to note that the Foundation is completely independent from Microsoft. The Foundation's mission to help the exchange of code and understanding between software companies and open source communities is really interesting to Microsoft. To help the Foundation fund its first year of operations, Microsoft is donating U.S. $1 million," Staples told me.

One thing that Staples was very clear about during our conversation was that the CodePlex Foundation will be complementary to the software ecosystem and is not designed to compete with any of the existing open source foundations. He hopes that the CodePlex Foundation will bring commercial and open source software development communities even closer.

"We need the community's involvement to make the CodePlex Foundation a success. We don't have all of the answers today. With today's soft launch, we hope to get critical input that will ensure the Foundation is a respected, neutral party that can enhance collaboration between participating companies, industry partners and open source communities. Over the coming weeks and months, we will be reaching out to many folks to get their feedback and to ask them to get involved with the Foundation," he said.

As such, an interim board has been established, with participation by both community and Microsoft individuals, and the plan is to work together with the open source community and other software companies over the next 100 days to really shape and define the foundation, he said. The intention going forward is to find the best candidates for the full-time board, with the expectation that the Foundation will be run by a combination of representatives from software companies and open source communities.

The interim board will also be creating a project governing process by which projects can be nominated and approved as part of the Foundation.

Microsoft's support of the Foundation is really the next logical step in our work with and engagement of open source software communities, and does not signal a shift in Microsoft's open source strategy, Staples said.

Over the past few years we have become increasingly supportive of open source, including sponsoring the Apache Software Foundation, contributing to the PHP Community, participating in Apache projects - including the Hadoop project and the Qpid project - and participation in various community events such as OSBC, OSCON, EclipseCon, PyCon, and the Moodle Conference.

"Our hope is that new opportunities will emerge for Windows and .NET developers to more actively participate in open source development through the CodePlex Foundation," Staples said.

You can read more about the new CodePlex Foundation at http://www.codeplex.org/.

Real Mission Critical

Mark Stone — Mon, 01 Jun 2009 16:15:00 GMT

The 1.0 release of WinBioinfTools might seem like a modest event; as of this writing, the project has
44 downloads. High Performance Computing (HPC) is a small community, granted, and the number of HPC
applications for bioinformatics is a small subset of that. Let's not confuse popularity with importance,
however.

We use the phrase "mission critical" very frequently and somewhat casually within software development. In
talking to a friend about the swine flu outbreak, I was reminded that the phrase has its origin in
military history: an aspect of a mission so critical that failure in that aspect would result in the
loss of life. In the developing world where medical infrastructure can be a fragile thing, information about
the origins or genetic makeup of a virus can be vital. It can be mission critical.

Historically, the developing world has been dependent on developed western countries to do their research for them.
Open source is beginning to level that playing field, though. Using a cluster environment and software
projects like CoCoNUT for gene sequencing and comparison, even university research centers with modest x86
server environments can play in the HPC space. This is important because the research priorities for a
university in a developing country may be very different from the research priorities of a major western
research university. At its best, this is exactly the kind of lowering of barriers to entry that open
source should facilitate.

For all its value, CoCoNUT has two significant limitations. Its license is an academic license, not a fully
open source license. And it runs only on Linux/Unix systems. The latter is particularly important. Research
scientists are not IT professionals, and they should not have to care about the underlying platform on which
their software runs. The spirit of open source is to make software as widely available as possible, and there
is no way to meet that spirit without including Windows Server among the target platforms. Mission critical
demands no less.

So WinBioinfTools makes important steps forward on both fronts. The team at Nile University has released a
GPL-licensed project that "contains a number of programs for Bioinformatics running over Windows Cluster running
Windows HPC server 2008. The current version includes the CoCoNUT system for pairwise genome comparison,
parallel global sequence alignment, and parallel BLAST."

This is a great example of a local software community using open source to make their needs a priority,
and delivering a project that will benefit local software communities in other developing countries with
similar needs. WinBioinfTools puts us one step closer to making scientific computing software platform
neutral, and closer to making Windows Server a first class citizen in the open source world of HPC.

Microsoft Teams up With Black Duck Software

Peter Galli — Mon, 18 May 2009 20:30:00 GMT

Microsoft and Black Duck Software this morning announced an agreement under which projects from CodePlex will be fed automatically into Black Duck's open source KnowledgeBase repository, and which will also will be searchable through Koders.com, a search engine for open source and other downloadable code.

This means that those customers who use the Black Duck KnowledgeBase to leverage, manage and detect the use of open source components in software application development projects, will now get comprehensive coverage of CodePlex-hosted projects, many of which are Windows .NET based.

Developers will also now be able to use Black Duck's Koders.com search search engine for CodePlex projects. While not all of the 9,000 CodePlex projects will be searchable in Koders as of today, most are expected to be by the end of June.

You can read the news release here.

Given that Black Duck's KnowledgeBase is a useful resource for development managers tasked with managing open source code in mixed-source development environments, the addition of CodePlex projects makes this a more powerful development resource, said Sam Ramji, Microsoft's Senior Director of Platform Strategy.

Black Duck, which is a Microsoft Visual Studio Industry and Windows Embedded Partner, scours the Internet, collecting open source and other downloadable code into its KnowledgeBase, a searchable repository of more than 200,000 open source projects collected from more than 4,100 Internet sites. More than 40,000 new projects have been added to the KnowledgeBase since January 2009.

As CodePlex is one of the fastest-growing open source hosting sites, this agreement will make it easier and faster for Black Duck to manage the steady stream of new projects on the site, said Peter Vescuso, Black Duck's Executive Vice president of marketing and business development.

CodePlex currently hosts 9,000 projects and adds about 100 new ones each week. "By teaming with Microsoft, we are assured of comprehensive, ongoing coverage of CodePlex projects in the KnowledgeBase," Vescuso said.

Announcing the PHP SDK for Windows Azure

Peter Galli — Wed, 13 May 2009 00:29:00 GMT

Vijay Rajagopalan, a Principal Architect here at Microsoft, is at TechEd India, where he will demo later this week a new set of interoperability projects related to PHP.

These projects include the PHP SDK for Windows Azure, an open source effort for which Microsoft has provided funding, with development by RealDolmen, whose goal is to provide high-level abstractions that enable PHP developers to interoperate readily with Windows Azure.

The PHP SDK for Windows Azure focuses on REST and provides PHP classes for Windows Azure blobs, tables and queue, helper classes for HTTP transport, AuthN/AuthZ, REST and error management, as well as manageability, instrumentation and logging support.

Rajagopalan will also announce the launch of a series of projects that offer samples and a toolkit that enable PHP developers to include Silverlight controls, Microsoft Virtual Earth maps and IE Webslices and Accelerators in PHP web applications; as well as automatically generated a simple "Create, Read, Update, Delete (CRUD)" PHP application from a table in SQL Server.

These projects, for which Microsoft has provided funding and which are available on Codeplex under a BSD license, are yet another proofpoint of the company's commitment to interoperability, and developers will be happy to know that the first batch of these have already been developed by Accenture.

Read Rajagopalan's full blog here for all the details.

The Azure Services Platform has been designed to be open, standards-based and interoperable, and its support for XML, REST and SOAP standards means that any of the Azure services can be called from other platforms and programming languages.

Microsoft has provided funding for two other SDKs that support third party programming languages: Java SDK for Microsoft .NET Services and Ruby SDK for Microsoft .NET Services so as to facilitate interoperability between the Azure Services Platform and non-Microsoft languages and technologies.

The inclusion of FastCGI in Windows Azure's hosting environment was announced at MIX 2009, and the protocol enables developers to run web applications on Windows Azure that were written using third party programming languages, including PHP. This opens up new options for PHP developers to deploy their applications.

A Technology Preview of the PHP SDK for Windows Azure will be released under a BSD license, while a functionally complete version of the SDK, which will support tables and queues, should be available for download by this fall of 2009, but the team is calling on developers to provide feature requests, test the toolkit, and join the user forum.

So, stay tuned, as there's a whole lot more to come!

Helping Facilitate Open Government

Peter Galli — Wed, 06 May 2009 19:03:00 GMT

Microsoft will announce on May 7 an initiative to help government agencies and developers publish and interact with their data in Windows Azure, the company's cloud computing platform.

One of these is the Open Government Data Initiative (OGDI), a cloud-based approach to housing public government data in Windows Azure, making it accessible in a programmatic manner via open standard protocols and application programming interfaces.

The source code for OGDI is being made publicly available through CodePlex, Microsoft's open source hosting site, so that developers may reuse it and provide feedback. Sample code is also being provided for technologies widely used on the Web, including PHP, Python, Flash, JavaScript, and Silverlight.

This initiative helps to provide government with tools focused on increasing responsiveness and access to critical services, streamlined processes and services.

For their part, Microsoft and its partners have developed a robust enterprise architecture approach that enables agencies to meet the technology requirements of government mandates with a familiar set of tools - built on an enterprise-ready, scalable, and easily-managed software-powered architecture.

So, in short, the goal of ODGI is to reduce the cost of publishing government data, and simplifying data access by leveraging cloud computing and open standards.

More information on Microsoft's Open Government Data Initiative can be found here.

To see an implementation of a data service in Windows Azure, using a sample of publicly available government data, visit this reference beta site.

These moves are part of Microsoft's ongoing open government efforts aimed at helping government organizations meet goals of transparency, participation and collaboration, particularly as an ever increasing amount of data becomes necessary and available.

As such, new methods need to be opened up to allow interaction with that data, and Microsoft's OGDI is designed to help public sector entities meet these goals.

This software, which underscores the importance of programmatic access to government data rather than having to download it, will give developers the ability to write programs that access data via Web-friendly programming methods without having to download or host the data; and let them write applications using any technology via open standards.

It also provides easier access to a broad array of government datasets, enabling the building of new and unique applications, while governments will be able to automatically refresh data without having to buy and maintain servers.

Cloud computing is the ideal platform for government data, and the technology is finally available to make it happen, says John Miri, Senior Fellow at the Center for Digital Government.

"The qualities that government looks for in an information management platform - things like flexibility, scalability, security, performance, and cost efficiency - are all better in a cloud model. As we see demands for government to become more transparent, collaborative, and interactive, a shift like this in technology architecture just has to happen, " he says.

For governments to become truly open, citizen access to public data in standards-based and interoperable ways is essential at all levels of government.

Given that most federal, state, local and education entities implement the American Recovery and Reinvestment Act (ARRA), they can meet open government goals of oversight, transparency and accountability through cloud and on-premises solutions such as Microsoft Stimulus360, which helps public sector agencies track, measure, and share information about federal stimulus programs through graphical dashboards and maps.

Better Windows Development Environments - One project at a Time

Mark Stone — Fri, 10 Apr 2009 14:45:00 GMT

Discussions of the PC market usually break down into "desktop" vs. "server", as if these are the only platform categories. However, the developer's dev box -- call it a "workstation" to distinguish it from desktop -- is really a separate platform. Remember, when Linus Torvalds created Linux it wasn't because he needed a better
desktop operating system, or a better server operating system. What he wanted was something that could run the gcc compiler. He wanted a developer workstation he could use at home.

Of course the developer workstation market influences other markets. Developers who develop on a platform are more likely to develop for a platform. So winning developer mind share is often about giving them what they want in the way of development environment. And in this regard, open source developers are something of a
different breed.

Microsoft has a great set of developer tools; I've certainly known developers who swear by Visual Studio. But there's something of a disconnect between graphical tools favored by Windows developers and then command line tools favored by traditional open source developers; I've also known developers whose first order of business
with a new Windows workstation is to GNU-ify it.

Ironically, the Internet has a convergence effect, drawing these two camps together. Put developers online, and they can collaborate. Put developers online, and they can not only develop, but they can build, deploy, and test. The workstation has become not so much a computer as an environment. The developer's toolkit includes version control, build management, automated testing, and the need to do all these things as a team rather than an individual. Developer environments have evolved rapidly to adapt to these changes.

The Apache Software Foundation (ASF) seems to understand this evolution as well as anyone, and a number of ASF projects focus specifically on tools for the developer environment (Ant, Buildr, Continuum, Gump, and Maven come to mind as a few examples).

What's interesting is to see the .NET developers following suit, and wanting these same sorts of tools for their development environment. What's surprising is that this .NET effort is very grass roots driven.

"Panday" is a Filipino word meaning "blacksmith", and can also be a reference to the graphic novel super hero of the same name (the graphic novel is also originates from the Philippines). This provides an appropriate metaphor for the name of the NPanday project on Codeplex.

The NPanday project is one of several affiliated with Microsoft's Open Source Lab in the Philippines, and is part of the effort to bring to .NET some of the capabilities found in other open source development environments. The aim of NPanday is integrate Apache Maven into the .NET development environment.This would enable .NET
developers to take advantage of Maven-compatible development infrastructure.

Projects like NPanday are important because they offer developers more choice of tools in a Windows development environment. The more familiar those tools are to open source developers, the more open source development will be done on and for Windows. NPanday is also an important project for interoperability, making it easier to integrate .NET development with other development done using Maven.

Because It's Fun

Mark Stone — Mon, 30 Mar 2009 21:15:00 GMT

We should never forget that a key motivator for open source developers is fun. For student developers -- where open source really starts -- this is especially true.

We’ve been looking at several potential student projects in Croatia, and for the past several months have been lending some support to the PlugBlog project.

In many ways this is a classic open source story. Croatia is not a large country (population 4.5 million), nor does it have as highly developed a technology sector as, say, Scandanavian countries of comparable size. Combine that with a distinctive language of Slavic origin, and you have an environment in which there is very little motivation for commercial software providers to offer Croatian localization. Thousands of languages and dialects world-wide struggle with this same problem: they simply lack the critical mass and market opportunity to warrant commercial software localization.

Into this breach steps open source. Several local blogging sites in Croatia do, of course, post blogs in Croatian. But bloggers would like to have the client tools to compose in Croatian as well. Given the popularity of Windows Live Messenger as an instant messaging client, there was a natural opportunity for open source development to create a localization pack enabling Live Writer composition in Croatian. This is precisely what PlugBlog aims to do.

One of the interesting twists on life in the era of Service Oriented Architecture (SOA) is how enabling SOA is of open source. Plugins for Live Writer can easily be open source independent of the source code status of Live Writer itself, because these plugins need only make web services calls to the Live Writer API. Indeed, a quick search of Codeplex shows more than 60 open source projects dealing with Live Writer. This is the kind of thriving little sub-community that SOA makes possible.

The developers working PlugBlog are students, and they are doing this work as a student project. As such, it has a clearly defined project plan and specific milestones for the project. The work they are doing will provide a valuable localized tool to Croatian bloggers, but it will also serve as an example of how other languages could integrate localization with Live Writer. This is all great, but you can’t stop developers from doing something just because its fun.

So I was surprised to see a check-in on this project that creates a connector for passing data from Skype to Live Writer. This wasn’t on the project plan. Talking to project coordinator Boris, he mentioned this was an extra they threw in in their spare time. Given the huge popularity of Skype in Eastern Europe this shouldn’t have been surprising, and indeed if anyone had mentioned it during project planning it almost certainly would have been part of the original design.

But this too is part of the beauty of open source: user-driven innovation fills the gaps overlooked originally. I look forward to more Skype integration and more pleasant surprises from the Croatian team.

Brazilian Students Set Their Own Course

Mark Stone — Mon, 16 Mar 2009 19:05:00 GMT

I’m going to tell a story that starts in Indiana, but really it’s about Brazil.

Once upon a time “scientific computing” was nearly synonymous with “Fortran”. Today, though, just about any high level language can be used to write High Performance Computing (HPC) applications. These days that language choice also includes C#.

At Indiana University, the Open Systems Lab has pioneered work to implement Message Passing Interface (MPI) support for .Net, so that MPI applications can be written in C#. The project is MPI.Net, and you can find it on Codeplex. It is open source, about three years old, has reached a 1.0 release, and is compatible with two other important open source projects, OpenMPI and Mono. The principle developers behind the project are Andrew Lumsdaine at Indiana University and his former student, Douglas Gregor, who is now on the faculty of Rensselear Polytechnic Institute.

This is the kind of open source work that’s really exciting to see because of the way it expands choices for the developer and the end user. A C# developer should not be closed off from writing HPC applications if that’s what they want to do. And a research scientist should not have to think about whether their lab is running Linux or Windows Server. Both of these individuals are working enough layers above the operating system that somebody else’s operating system choice should not be a constraint.

So I was very excited to learn that students in Brazil at Federal University of Rio Grande do Sul were doing work on MPI, and excited to talk with them about their work. One of their projects is MPI#, also open source and also hosted on Codeplex.

MPI# builds on top of the work of MPI.Net, adding some functionality not yet present in MPI.Net. Specifically, quoting from the project description:

The goals of this project would be to build upon MPI.NET in order to complement it with the features that are missing, mainly regarding collective communication. Either they could benefit from C# native support for such communication, either they could be programmed on top of the provided MPISend/MPIRecv encapsulations. C# and .NET features such as fault tolerance or dynamicity support would be studied, in other to turn the MPI# implementation robust in large, dynamic and heterogeneous platforms.

Two of the students working on MPI# are Ismael Stangherlini and Fernando Afonso. They are graduate students in computer science, working on projects affiliated with the Brazilian Interoperability and Open Source Software Development Nucleous. When I talked to them about their work on MPI# I was curious what their communication with Indiana University had been like. Their response: they had never been in contact with Indiana University; they simply downloaded the code for MPI.Net and started working on their own.

That’s the magic of open source: that they can, in fact, just download the code on their own and start coding against it. They may make an important contribution to MPI.Net. Or their code may be entirely disregarded. Or they may move on to other projects and somebody else may or may not pick up where they left off. At this stage it’s too early to tell. But the fact that all of these scenarios are possible demonstrates why, as a methodology, open source is so nimble and adaptive. A top-down product development process, or a top-down standards development process can only execute on the innovations envisioned by the few at the top, and at the speed of the slowest decision-makers in the process. But a bottom-up open source process enables every innovation that anyone at the grass roots level can see.

CodePlex: A Year in Review

Peter Galli — Tue, 27 Jan 2009 00:52:00 GMT

CodePlex, Microsoft's open source project hosting Web site, has grown by leaps and bounds over the past calendar year. Visits to the Website more than doubled to top 19-million in 2008, while new registered users were up more than 70 percent to over 66,000 and the number of new projects more than doubled to 4,542 over the year.

That brings the grand CodePlex total to more than 120,000 registered users and 7,500 projects.

According to a blog by Sara Ford, the Program Manager for CodePlex, there were 12 new releases of the CodePlex software over the year, with new features including Subversion client support; an upgraded UI; Silverlight hosting; an AJAX Source code browser; and Search improvements.

The top five Open Source projects created in 2008, by page view count, were WPF, the main site for updates on the WPF roadmap and the portal for accessing the WPF Toolkit and the WPF Futures releases; the Silverlight Toolkit, a collection of Silverlight controls, components and utilities made available outside the normal Silverlight release cycle; the CompositeWPF, designed to help users more easily build enterprise-level Windows Presentation Foundation and Silverlight client applications; MVCSamples, prototype and sample ASP.NET MVC Sample applications; and the Unity Application Block, a lightweight extensible dependency injection container with support for constructor, property, and method call injection.

Also, earlier this month, DotNetNuke Corporation, the creator of the industry-leading DotNetNuke development framework, decided to leverage the CodePlex infrastructure for its core product distribution. DotNetNuke said it would utilize CodePlex for download infrastructure, bandwidth, and metrics reporting for its core product offerings. Until now, DotNetNuke had been leveraging services from SourceForge.Net.

So, what's next you may ask? Well, Sara and the team are eagerly waiting for your feedback and suggestions.

DotNetNuke Moves to CodePlex

Peter Galli — Wed, 07 Jan 2009 22:31:00 GMT

DotNetNuke Corporation, the creator of the industry-leading DotNetNuke development framework, has decided to leverage the CodePlex infrastructure for its core product distribution.

DotNetNuke will utilize CodePlex for download infrastructure, bandwidth, and metrics reporting for its core product offerings. Until now, DotNetNuke had been leveraging services from SourceForge.Net. DotNetNuke is also currently the second most commonly downloaded project on CodePlex.

Last February, DotNetNuke Corporation announced the availability of the DotNetNuke Forge, the prime destination for open source collaboration on the DotNetNuke platform. The DotNetNuke Forge has grown in breadth and popularity over the past year and now represents a vital part of the DotNetNuke ecosystem.

The DotNetNuke Corporation researched the many open source project hosting services available, and decided that CodePlex provided the "most reliable and dependable infrastructure, cleanest user experience, most advanced project administration tools, and highest commitment to future innovation," said Scott Willhite, its Co-Founder and Community Director.

CodePlex Program Manager Sara Ford says Microsoft is excited about having DotNetNuke join the CodePlex community and, as the leading open source web application framework for ASP.NET, the CodePlex team is looking forward to partnering with them to promote open source development on the Microsoft platform.

The team is also looking forward to hearing the feedback from the DotNetNuke community for improving the open source development experience on CodePlex.

Oxite: an Open Source Content Management Platform

Peter Galli — Tue, 09 Dec 2008 19:40:00 GMT

I'm on the road with Robert Duffner, our Senior Director of Platform Strategy, talking to tech press in New York, Boston and San Francisco this week.

So, imagine my surprise when top Microsoft blogger Mary Jo Foley ran an article about a new open source content system known as "Oxite."

The alpha code for Oxite, which is an open source, standards compliant, and highly extensible content management platform that can run anything from blogs to big web sites, and which already runs MIX Online, was recently released on CodePlex, our open source project hosting site.Oxite is licensed under the Microsoft Public License.

While we were surprised by Mary Jo's blog, this is a great thing as it shows just how many open source projects are taking place under the covers here at Microsoft. Having a range of our developers across Microsoft working on a variety of open source projects targeted at different communities of users, is exactly the goal of our group.

Stay tuned, as I expect to be surprised a lot more going forward and, as I do, I'll bring these projects to your attention, however they come to my attention.

Network Monitor to Open Source Parsers on CodePlex

Paul Long — Fri, 07 Nov 2008 16:49:00 GMT

Today I am excited to announce that the development of protocol parsers for Microsoft Network Monitor is moving into an open source model, hosted on CodePlex. This site will host development of parsers for public protocols and for protocols described in our Open Protocol Specifications for Windows.

Network Monitor is a free protocol analyzer and network sniffer. It allows you to capture and view network traffic in a format that is easier for humans to read. It is often used as a troubleshooting/development tool or to validate that a protocol is behaving as you expect.

We've started the ball rolling by releasing an updated parser package and creating a source tree on Codeplex. While this process will take time, we hope to have all bugs filed on the site within a few months, as well as having all parser development taking place directly on CodePlex.

Every month we'll post a new installer package that Netmon users will be able to install, so as to benefit from the latest changes.

As we continue to evolve, we hope that the community will get involved by filing bugs and suggestions, contributing code and new parsers, and helping us improve how information like summaries and field descriptions are displayed.

At some point we also anticipate that some of our committed users will manage subsets of the parsers.

We are also really excited about the impact of making our parsers open source. The force of the community should help us keep up with the quickly changing world of new protocols and updated documentation.

If you want to contribute, please join the community on CodePlex and start giving us feedback.

For historic background, Network Monitor 3 was a complete re-write of the Network Monitor program that previously shipped in Windows Server and SMS.

One of the major design changes is that the parsers - code that describes how network packets are decoded - are written in a custom language and included with the product.

Most industry protocol analyzers include parsers as static compiled code, or DLLs, which make them harder to update and maintain. By contrast, because the Netmon parsers are run within our execution environment, they can provide a layer of protection against overruns and therefore help protect the user from poorly written code which can expose security vulnerabilities.

At the same time that Network Monitor 3 was being developed in 2004, the product teams were in the process of creating the documents for the Microsoft Open Protocols.

So, at that point, we were able to partner with our document writers and get parsers written for these open protocol specifications for Windows. Not only did this help us verify the documentation, but it also provides a strong base of parsers for Network Monitor that makes troubleshooting network traffic very transparent.

For the latest version of Network Monitor, visit our download page.

For more information and tips on using Network Monitor go to our blog.

Thanks and enjoy!

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!