Slashdot Mirror


Is the CodePlex Foundation Truly Independent Now?

Glyn Moody writes "Microsoft created its CodePlex, 'an online collaborative software development portal,' four years ago, as the latest in a string of attempts to play nicely with open source. Well, maybe not: Microsoft saw the open source software projects it hosted there as reflecting 'the open community-building spirit of Microsoft's Shared Source Initiative.' In September last year, it tried again, launching the CodePlex Foundation, 'a forum in which open source communities and the software development community can come together with the shared goal of increasing participation in open source community projects,' and not to be confused with CodePlex.com, 'a Microsoft owned and staffed forge that encourages the development of open source software based on Microsoft technology.' The only problem is that all the funding for the CodePlex Foundation still comes from Microsoft. But the new Technical Director of the CodePlex Foundation, Stephen Walli, thinks it can become truly independent of Microsoft, open to all companies to create open source software for any platform using only OSI-approved licenses. Will the CodePlex Foundation take its place alongside existing foundations addressing this sector, like Apache and Eclipse, but complementary to them? Or is it forever doomed to be ignored by the open source world because of its origins?"

21 of 123 comments (clear)

  1. If MS was really serious... by DoofusOfDeath · · Score: 3, Insightful

    They could endow a trust fund for SourceForget.net. And if they had ideas for a better forge, they could make code submissions to SourceForge.net.

    1. Re:If MS was really serious... by DoofusOfDeath · · Score: 4, Insightful

      Why? Why can there only be one open source code repository?

      I'm not saying there should only be one public forge. I'm just saying that would be one way for MS to get away from people's distrust in anything they back. Because I think most people would trust SF.net to not be corrupted the kind of thing I proposed.

      Further, ultimately, as a developer, do you even care what repository the code comes from?

      No. But as a project contributor, maybe. If this was the MS of the 1990's, I wouldn't trust a forge they owned one tiny bit - there would almost certainly be a trap hidden in the legalese. Nowadays, I'm not sure.

      But here's another way to look at it: aside from branding, what might MS's motives be for setting this thing up? Based on their past actions, it's pretty clear that they're not angels.

    2. Re:If MS was really serious... by guruevi · · Score: 2, Insightful

      The thing with Microsoft is that nothing you create based on their 'technologies' can truly be open. The Shared Source license is likewise not a very 'open' or 'free' (both in speech and in beer) license. The problem with Microsoft is that they have used their financial and patent weight against open source in the past and will probably continue doing so. If Microsoft really want, they can revoke all their permissions and promises at any point in time and all projects based on the Shared Source License would become closed.

      What Microsoft needs to do to become open as you say is to support existing open initiatives (which SourceForge is a part of) and license the building blocks of their software (.NET/Mono) and patents more permissively. A truly good initiative would be to donate their patents in a legally binding trust fund (none of the 'we promise we won't unless it benefits us') that isn't managed by them and truly make their software more open.

      Examples:
      Active Directory: It's basically LDAP + Kerberos, please remove the proprietary shill around it so it's easier to use clients that are not Windows (for a good example: Apple Open Directory)
      SMB: We have reverse engineered it for a while. It's simple, just open it or give the specs to the Samba team and stop changing crap between Windows versions so it keeps working. .NET: Mono is an open implementation but is always behind. Open it up and release the patents on it so we can actually use Mono without fear of having it pulled within a couple of years.
      POSIX: Just do it right, you can keep Windows closed.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    3. Re:If MS was really serious... by Richard_at_work · · Score: 2, Insightful

      So could Google - but no one seems to be bitching about Google Code.

  2. Re:No it isn't. Now let's get back to work. by binarylarry · · Score: 2, Insightful

    Yep, "in a string of attempts to play nicely with open source" sounds like "in a string of attempts to nicely play open source" but it's not really the same thing.

    --
    Mod me down, my New Earth Global Warmingist friends!
  3. Let me get this straight by Monkeedude1212 · · Score: 3, Insightful

    An organization that wants to make open source products based off Microsoft will only get more Open Source Cred if they separate from Microsoft?

    It seems like Microsoft is stuck in a position to make no concession. You don't like Microsoft. You'd like it a bit more if it were friendlier to Open Source. Microsoft starts an Open Source Initiative. It doesn't quite live up to Expectations. Now, the only way this new initiative can redeem itself is to become independent of Microsoft.

    Wouldn't then Microsoft NOT have an open source initiative, and put them back at square one? Does becoming independent of Microsoft allow them to better work on Microsoft code?

    1. Re:Let me get this straight by binarylarry · · Score: 4, Insightful

      Microsoft eventually wants .NET to be competitive with the Java platform.

      They know that Java has a massive, massive advantage in terms of OSS 3rd party library availability. As mentioned in the article, this comes from high profile Java OSS projects like Apache's Jakarta, Eclipse and others.

      So Codeplex is their attempt at getting a similar ball rolling for .NET. We'll see if it succeeds, I doubt it will catch on in a similar fashion though, .NET is doomed to niche Microsoft operating systems.

      --
      Mod me down, my New Earth Global Warmingist friends!
    2. Re:Let me get this straight by binarylarry · · Score: 2, Insightful

      I assume you must be one of the codeplex people.

      Good luck and GG! ;)

      --
      Mod me down, my New Earth Global Warmingist friends!
    3. Re:Let me get this straight by MightyMartian · · Score: 2, Insightful

      CodePlex may or may not be bad, but Microsoft's history of attacks on open source over the last fifteen years means I'd never use anything they offered. Sorry, maybe that's biased, but I tend to think of it as being cautious and rational.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    4. Re:Let me get this straight by h4rr4r · · Score: 3, Insightful

      Show me the .Net for Solaris, Linux or Mac.

  4. Re:Yeah. Now we see the truth. by redbeard55 · · Score: 5, Insightful

    In other words MS fanboys are ignorant of MS's history of backstabbing any competitor including one they have partnered with. Actually, especially the ones they have partnered with. CodePlex Foundation should be ignored by the open source community until MS has absolutely no possible influence within the organization.

  5. It's A Trap by twmcneil · · Score: 4, Insightful

    While it's easy to find any number of lazy, greedy jerks who simply want to to profit unjustly off the honest work of open source developers, MS is not in that category. MS wants to kill open source utterly and completely. Do not ever forget that.

    --
    "The ferrets, they're every where I tell you!"
  6. Firefox by ubersoldat2k7 · · Score: 4, Insightful

    Maybe they should start with a proper website that works on non-MSIE browsers.

  7. Re:Yeah. Now we see the truth. by hairyfeet · · Score: 3, Insightful

    Actually it doesn't really matter a bit what MSFT has done in the past, as they like any other company has to obey the license. If all the foundation has is OSI approved licenses, like Apache, BSD, Mozilla, etc then it shouldn't matter to you, I, or anyone else except zealots who pays the bills, as they have to obey the license. Sure in the future they could decide to take any project they own and go closed source with it, but so can the writer/owner of ANY software, and they can't close the previous version, therefor you can always fork.

    In the end these projects just show that like Apple MSFT is beginning to see how they can leverage FOSS in certain situations to help themselves as well as anyone else. Nobody expects Apple to give up their proprietary bits, why should MSFT? In the end they have to obey the license or risk being sued (and the resulting bad PR) no different than any other corp.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  8. Re:No it isn't. Now let's get back to work. by Anonymous Coward · · Score: 2, Insightful

    exactly. We still see it today, if it runs on Windows and something else which Microsoft sees as a threat, then it is a threat to Windows and a threat to Microsoft. Codeplex was designed so Windows developers who liked the idea of collaborating with other developers on projects had an option other than going out to the cross platform, or even Linux only, forges. Provide a place for the Windows developers to look first in hopes they'll stay there and not wander out into learning how the other half lives and maybe find out that they like how that other half lives, works, plays and jump ship.

    Microsoft Codeplex will always be this way unless they hand it off to an open group to run. It will remain Microsoft based and tied even if they say it is not and Microsoft based people are running it.

  9. Not exactly any license. by miffo.swe · · Score: 2, Insightful

    Codeplex is utterly GPL unfriendly, i would say GPL hostile. Its also nothing more than a way to steer open source towards being something you build with Microsofts closed technologies. Its not even stealthy in that regard.

    I say fuck Microsoft until they prove they can cooperate. Why give them free ammo for absolutely nothing?

    --
    HTTP/1.1 400
  10. Why I don't like MS Hosting FOSS Projects by Anonymous Coward · · Score: 3, Insightful

    Why I don't like MS Hosting FOSS Projects ... a few reasons.
    1) Microsoft has always looked towards the bottom line first and community second.
    2) Microsoft doesn't really want any competition in platforms, so anything written that runs on many different platforms will "never behave as well" (performance, threading, resources, etc) as a 100% native application.
    3) When Microsoft does attempt to get onboard with a standard app/tool/protocol, they always extend it in a proprietary way. Sometimes they make it better than it was, but since nobody else is allowed to also get those extensions, it doesn't do any good for the original community. Just look at LDAP/Active Directory.
    4) Microsoft has had 30+ years to select, port and deliver a good cross platform scripting language, but they have not done so. I would love to have a native-from-Microsoft pre-installed version of Perl on every MS-Windows platform. Still they release wsh, cmd, bat and other similar crap. Where's the MS-Python or MS-Perl or MS-Php? Oh, because those are true FOSS projects, MS can't bastardize them. It doesn't matter how much more productive scripting would be. We know other commercial vendors that include these tools with the OS. Why won't Microsoft?

    If you want a new idea to flourish, you need these things:
    - small group of _believers_ that work on it for passion, not money
    - complete openness in the results - source code in this case
    - competition - another real player to battle against who also has complete openness in their code. It is NOT cheating to look at the competition's work.

    Examples include the robot soccer team competition where at the end of every competition, all software for every team is shared so the level of play the following year will be elevated for all teams. Basically, the best software for last year is the starting point for all teams in the next competition.

    Just a few thoughts.

  11. Re:Yeah. Now we see the truth. by fwarren · · Score: 2, Insightful

    Still all is based on Microsoft Technologies. So if you design and "Open" killer application in VB dotNet it is not a threat. VB dotNet only runs on Windows. To properly implement it in Mono, you need the odd bits that Microsoft owns the patents on.

    The idea is that you develop cool projects that the community can contribute to, but only the coolest of the cool and the best of the best will be able to run on Windows. That's what they call open source.

    I would call it a failure. How long did it take source forge to be successful? 6 months? 12 months? Even after 48 months and Microsoft pouring money into it, it is still a failure.

    But why should it not be. If I want to write real open source apps for linux or to be cross platform, I am going to use some "open" technology that makes sourceforge a better home than CodePlex. If I wanted to write something that was going to be Windows only, why not make it shareware, or a real paid for product? Which again would negate CodePlex.

    --
    vi + /etc over regedit any day of the week.
  12. Re:Yeah. Now we see the truth. by redbeard55 · · Score: 2, Insightful

    Again, look at the history of MS's dealing with their partners with which they have had contracts with. How many times have they been in court and lost. Of course you need deep pockets to take MS to court even if you are right. MS is no friend to open-source and if they can screw a software developer they will, based on past history. They are not happy with a slice of the pie if they can take the whole pie. They still have not come close to changing their spots . . .

  13. They still have leverage by pavon · · Score: 4, Insightful

    The point of codeflex is to get people to develop open source software that runs on Microsoft's Platforms - desktop applications using WPF.NET, web applications using ASP.NET, windows mobile 7 applications using Silverlight, rich web environments using Silverlight. For desktop/phone applications this make sense - free high-quality applications improve the appeal of the operating system. For web applications, the only reason they want this is to increase market share of their proprietary technology. In both cases they still control the platform.

    Developers whose sole intention is to write for Microsoft's platforms alone, probably shouldn't have any problems, because MS would be shooting themselves by hindering them. However for developers that write applications in .NET/Silverlight thinking that the existence of Mono/Moonlight means that it is a great cross-platform tool, could easily be backstabbed by Microsoft if they ever change their stance on patents.

  14. Re:Yeah. Now we see the truth. by oakgrove · · Score: 3, Insightful

    then it shouldn't matter to you, I, or anyone else except zealots who pays the bills

    Based on MS's historical disdain for open source with the current CEO Steve Ballmer even going so far as to refer to Linux as a cancer, I think it extremely naive and presumptuous to refer to people suspicious of their motives as just zealots implying that their caution is without merit. Contrarily, I think anything other than an attitude of extreme skepticism is foolhardiness approaching absurdity.

    Furthermore, any license which by its very nature being a legal document is open to ambiguity and interpretation by a court and can very well be used in unpredictable ways to damage open source and to completely downplay this possibility in general and in the case of MS in particular especially in light of their very direct statements against open source is extremely arrogant and misinformed on your part.

    --
    The soylentnews experiment has been a dismal failure.