Sign In

    Enjoy FOSSwire's content? Have it delivered! Subscribe

    Bruce Perens on Microsoft and Apache

    You may or may not have heard that Microsoft recently sponsored the Apache Foundation, to the tune of $100,000 a year.

    While I'd love to believe that Microsoft is finally changing its tune on the open source development model and actually honestly trying to promote interoperability, it seems I am not the only one with cynical and sceptical views on Microsoft's real agenda.

    Bruce Perens, creator of the Open Source Definition and co-founder of the Open Source Initiative has written an interesting and insightful article discussing what he believes Microsoft's 'game' to be this time around.

    Just a few years ago, Microsoft exec Jim Allchin called open source "an intellectual-property destroyer, I can't imagine something that could be worse than this for the software business and the intellectual-property business." [...]

    Now they just want to interoperate, right?

    Wrong. You wouldn't have to look too far to convince yourself that Microsoft still engages in hard-edged fighting against open source. The Office Open XML standard has recently been pushed through ISO with so many irregularities in process that four nations complained. There already was an ISO-accredited office document standard called OpenDocument, created by the OpenOffice team. It was one-tenth the size of Microsoft's effort, and did the same work. But it would have put Microsoft and open source on an equal footing. Office Open XML, in contrast, is 6,000 pages long, so large that it's not possible for a programmer to learn it in his or her useful lifetime. That'll keep the open source folks from ever handling files quite the same way that Microsoft does.

    He also touches on some of the wider issues that the open source development model faces today later on.

    It is definitely an interesting read if you're interested in these sort of issues.


    The AGPL Announced

    Today, the Free Software Foundation issued a press release announcing a new type of open source license: the Affero GPL (AGPL).

    Basically, the AGPL is GPLv3 with one key addition: source must be shared to network users. This means if your favorite web application were to be released under the AGPL, any changes you make to it, even if just for your website, must be published.

    Think of this hypothetical situation: You run a WordPress blog. WordPress 3.0 is released under the AGPL, and you decide to run it on your site. But, you make a modification to it. You must now publish your source code to WordPress.

    For web applications that use this, it means that any changes can easily be shared back to the main project and possibly speed up development. The only restriction is that you must publish your changes: it can be tedious to publish every revision, taking out passwords and private files, etc. In this way, it might be discouraging to webmasters to download an AGPL program, as they would have to take care of all this. Nothing is released under this license yet, so we can not see any effects for sure.