Furthermore, the big-ticket items like Windows and Office available under Shared Source for government are unlikely to be re-released under the new licenses. A Microsoft spokeswoman told The Register this would be a decision for the individual technology groups.

Instead, Microsoft is aiming relatively low on what it releases. The spokeswoman said Microsoft's Bluetooth wrapper for Windows CE and eight starter kits for Visual Studio 2005 will be released under Ms-PL. The latter, for example, to add the ability for applications to keep track of new film releases on Amazon.com.

That's a continuation of existing policy. Microsoft released its Windows Template Library, Windows Installer XML and FlexWiki to SourceForge to SourceForge last year.

There is an upside. Ms-PL allows developers to view, modify and redistribute source code for commercial and non-commercial without paying Microsoft royalties. Ms-CL stipulates that where Ms-CL is used in a particular file then the entire file must be re-distributed in source code form with a "per-file reciprocal term".

Hurdles

Microsoft is clearly taking something of a"copy left" approach to Shared Source, an approach that is used widely in the real open source community.

Microsoft is - and always was - notoriously obsessed with detail when it comes to licensing.

The shenanigans around Microsoft Communications Protocol Program (MCPP) proved it was more than happy to release code while putting up just enough bureaucratic hurdles to make obtaining that code by developers too complicated and time-consuming for them to bother.

These latest changes should be seen in this context and will come as little surprise when you remember how Shared Source started life: as a response to increased concerns among customers to the security of its products in light of numerous worm attacks, and the growing success of open source and Linux, particularly in the government sector.

The five licenses represent another shift in Microsoft's journey closer to the open source community and development methodologies. While welcome, the changes give the community just enough of what it wants while leaving Microsoft in the driving seat in terms of what code it releases and the conditions it uses. ®

Page:

• ← Prev
• 1
• 2

Related stories

• MS targets developers with familiar integration and scale pitch (7 November 2005)
• Microsoft to digitise 100,000 books (4 November 2005)
• Visual Studio and SQL Server '05 step closer (28 October 2005)
• OpenOffice challenges Microsoft on XML standards (20 October 2005)
• Cautious welcome for new MS shared source licences (19 October 2005)
• Defendant: Microsoft source code sale was a setup (12 November 2004)
• Whatdya mean, free software? (2 November 2004)
• Let's Parlay over Open APIs (19 October 2004)
• Microsoft opens up Office - to governments (20 September 2004)
• MS expands WinCE 5.0 'shared' source licence (28 June 2004)
• Public sector urged to think Microsoft (25 May 2004)
• Microsoft sees Judge, looks busy (21 April 2004)
• MS preps new Shared Source challenge to OSS? (31 March 2004)
• Why Microsoft ‘Shared Source’ can never be trusted (17 March 2004)
• Opinion Microsoft's Shared-Source defeats Trustworthy Computing (18 February 2004)
• MS Windows source code escapes onto Internet (13 February 2004)
• Microsoft to convert world to “shared source” – by 15,625 AD (23 January 2003)
• Microsoft exposes more Windows code (6 August 2002)
• Microsoft welcomes UK govt open source policy (29 July 2002)
• Microsoft aims ‘shared source’ spoiler at Java (28 March 2002)
• Microsoft releases CE source code (23 July 2001)
• GPL Pacman will eat your business, warns Gates (20 June 2001)
• Readers: "MS is the cancer" (3 June 2001)
• MS on Trial Judge's helper Lessig rejects MS breakup solution (24 February 2000)