Microsoft Puts SourceForge Clone Into Beta
M$ Mole writes "Microsoft is working hard to build their .NET community and has released the beta of an online software project management site. The service being provided is very similar to SF.net, but problems are arising around Microsoft's license, which (originally) granted all rights to the software place on the server to Microsoft. MS has back-pedaled a bit since their 'beta' license and is working on a new, more "acceptable" license."
Look here.
Looks like they worked pretty fast to smooth that little PR gaffe over.
Mark my words, in 5-10 years, MS will be talking about how they rescued Linux/OS from ravenous hippies like RMS and ESR. Look how slowly they've been admitting their faults without ever really giving credit where it's due. Just recently, they've said that "Linux is a threat". Eventually they'll "buddy up", and then when the OS community won't let them fork code -- probably Linux or Mach, XFree86, Mozilla -- they'll say, "Look, those meanies won't share their fun toys!" And the media (already owned by MS and Disney anyway) will eat it up. This is a game that will probably play more in the public eye than in a court room, so now's the time to be asking ourselves, "What can we do to let everyone know what we're really about?" The only way OS can beat MS is if we plan far, far ahead.
Emacs: for people who just never know when to
Wow is this old news day, or what?
/., usually anti-MS news is posted quickly, and the good stuff, like the release of Visual Studio .NET, is ignored.
This controversy erupted nearly a month ago.
A number of us in the Windows community balked at the initial licensing. The lead developer of the GotDotNet workspaces actually joined into the conversation trying to defend the team's lawyers. It appears that the initial licensing was written with a heavy emphasis on CYA, without much thought to whether or not people would agree to it.
Microsoft listened to our arguments, and adjusted the licensing to be friendlier within a day or two. I still think it's rather ridiculous language but it is similar to that found at sourceforge.net and even such places as yahoo, etc. Why lawyers feel they need permission to redistribute stuff that you obviously uploaded with the intent of redistributing is beyond my ability to rationalize.
Anyway, I'm surprised it's taken this long for this to hit
the submitting user grants SourceForge.net the royalty-free, perpetual, irrevocable, non-exclusive and fully sublicensable right and license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, perform and display such Content (in whole or part) worldwide and/or to incorporate it in other works in any form, media, or technology now known or later developed, all subject to the terms of any applicable approved license.
( Perpetual?? Does this bind someone to a timeframe that even Disney would drool over? At least it doesn't say "throughout the universe".)
First, I think (NBAL,YU (Not Being A Lawyer, You Understand)) that most open source licenses give users approximately the rights listed there in general - and since they are saying that their rights are still subject to the terms of an "applicable approved license" so I'm not sure (AIAAL (Again I Aint A Lawyer)) that they're claiming that much. And I suspect that a part of that license (reproduce...publish...display...) is really there to cover them in the case that someone puts something on sourceforge and then wants to take it back and then sue sourceforge for having shown it around. (BAISIANNBALA (you figure it out this time)).
I'm still staring at the MS license (interesting that its not clear right up at the top of the gotdotnet site pages that MS is actually gotdotnet) and the "explanations" offered to see if I can figure out what it might actually be saying (BAISIANNBALA). It does look though like you're giving MS a whole lot more power over your work than you're giving sourceforge.
It looks like the gotdotnet web site had died. You'd think that MS could put up a site that could handle a little slashdotting.
The dogcow says "Moof!"
Nope, under their old terms (at least what I saw posted here on /.) they wouldn't be bound by the terms of the GPL. They are only bound by their own terms, since those are the only terms they will accept your code under. The copies YOU give out (or people download) would have the GPL on them, but the copies THEY give out could have any license whatsoever, and it would have nothing to do with your code (except for the inconsequential fact that it's a copy of your code).
Sorry for the hack job on the quote, but it's all there in black and white and legalese.
So if you sued them, they would turn around and sue you for violating their license. It's their server, after all.
---snip---
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
---snip---You are suggesting that MS taking code and using it as their own without granting credit is equivalent to that?
It also doesn't give everybody these rights, just MS. So if I were to release something as GPL, it would be GPL for everyone except MS, who can do with it what they please. No thanks.
You're looking at the wrong site. The topic of discussion is gotdotnet.com, and yes that t makes all the difference. Naturally it runs the OS you'd think it would.
It's usually instructive in situations like this to consider the historical context of the issues. Here's the original 'Open Letter' from Bill Gates to the hobbyist community
The background here is that a lot of people pirated Bill's Altair BASIC program, and Bill wanted to know where good software was going to come from if people didn't get paid for it.
It may not have been legal or ethical for hobbyists to pirate Altair BASIC back in 1976, but very soon thereafter, Free Software gave us an answer and an alternative: share the source, and the software grows even in the absence of monetary incentive. It is immune to the type of 'theft' that Bill was whining about. 26 years later, we have seen that Free Software isn't just surviving, it's thriving.
Now, along comes GotDotNet, which looks suspiciously like an emulation of Open Source practices... except that the AUP includes a few serious distinctions. One is the assignment of certain important rights to Microsoft that basically let them do whatever the hell they please with the sweat of your brow. Here's a quote of (what looks like) the original license from the discussion at Activewin.com: (Link to the full thread)
Note the specific lack of compensation for the original programmer (unless you consider the use of GDN itself to be sufficient recompense, but I'm pretty damn sure that GDN isn't going to be buying your groceries and paying the rent). One must ask - if nobody pays the users of GDN, where will the good software come from? Nothing about GDN sounds like hiring programmers to 'flood the hobby market with good software'. It sounds ripping off the community to serve MS's shareholders (eg, Bill).
So what's the point?
I propose that the fundamental corporate culture of Microsoft embodies Gate's attitude as reflected in the 1976 'Open Letter'. This culture is allergic to piracy, because a consumerist revenue cycle is necessary to improve the software.
The Free Software movement has thoroughly refuted Gate's thesis, by making itself independant of the revenue cycle (and therefore is not harmed by 'piracy' as it is usually understood).
Microsoft's obsolete culture cannot change to adopt Free Software practices - the assumptions that Free Software threaten are the very core of their business. If the company were rebuilt from the ground up on Free principles, the entire culture would have to change - essentially resulting in a totally different company that happens to have the same name.
Since Microsoft cannot adopt free software practices, Microsoft can only regard Free Software as a competing producer of software, taking market share away from them, and therefore, a deadly threat.
Since Microsoft itself regards Free Software as a threat, it seems to follow that nobody else who depends on revenue streams to survive, would ever want to use a system that resembles a Free Software ecology (like GDN), as they would deprive the producer of that stream.
Producers of free software should similarly be suspicious of a system governed by a legal agreement written by someone who considers them to be a deadly enemy.
Therefore, Microsoft's own pseudo-Free intiatives (such as GotDotNet, the Shared Source license, and the Software Choice initiative) are probably (a) Shams that will perpetuate Microsoft's revenue stream at the expense of the rights of members of the community, and/or (b) exceedingly stupid mistakes on Microsoft's part.
In the absence of further evidence (especially since GDN is slashdotted and I can't read the text of the new license), it is impossible to tell to which degree GDN (or any other pseudo-Free effort by Microsoft) will be (a) or (b). In either case, it seems imprudent for users or programmers - whether they produce in open or closed software - to place their trust in these intiatives.
I wonder, as an aside, if Bill himself ever paid anything to the original inventors of BASIC, a pair of researchers at Dartmouth University. So I wonder if Bill's logic reflexively implies that he stole BASIC from Kemeny and Kurtz. Gee. Where will the good ideas come from? Oh, wait academia has been going as a not-for-profit institution for centuries. You may have heard of some of their other 'products' - the theory of universal gravitation, electricty, the rabies vaccine...
he service being provided is very similar to SF.net, but problems are arising around Microsoft's license, which (originally) granted all rights to the software place on the server to
Microsoft.
SourceForge has changed the license terms long ago. Not sure if they got changed back
However: if you host a project on SF you grant SF to use your code for any purpose. Without the need to message you, to contribute or whatever.
Just read point 6 of the license: http://sourceforge.net/docman/display_doc.php?doc
angel'o'sphere
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
And the last time I checked Sun's JVM does not include an Application Server(ie like ASP.NET).
.NET from a development standpoint.
.NET CLR. Granted installing it is trivial, but when the number of workstations is in excess of a few thousand, this becomes a pretty big headache. Also to take note of is that if you've already got a Java devel squad, why switch to .NET? Learning C# wouldn't take that long, sure, but the entire point of .NET is that you can maintain a heterogenous project composed of different languages. If you're not taking advantage of MSIL (MSIL, bytecode, what's the difference?), then why switch to .NET? Ubiquitous runtime environment? Yeah, Java has that. Plus the JVM is ported to other platforms that .NET is not yet. Even when [if] Mono hits primetime, it will be a while until [if] they get Windows.Forms working. Slower runtime than native compiled code? Yeah, they both got that.
Agreed, but the openness of the language and the Java community allows for others to come up with even better solutions. Downloading the J2SE sdk and Tomcat is cheaper than buying Visual Studio
I agree with your first statement, at my work though, we're all running Win2k with IE 5.5, and certainly no
So while we're talking Java, where's the gain?
--- What
Hmmm.that seems against what RMS originally designed the GPL for.
The GNU General Public License was designed to allow Emacs to work on Solaris and Windows operating environments. That's why the operating system clause is in there.
If I wanted to compil VB code, I need to use a NON-free (+$100 compiler) to use it.
Not for long: check out GNOME Basic.
Will I retire or break 10K?
The code they used in ftp.exe (and a few other TCP/IP programs) was licensed under the BSD license and not under the GPL.
C# is "Java"-ish. VB.net is nothing like java
.NET libraries, which is analogous to the way Java works. They're both identical in most everything except syntax and C#'s ability to escape from .NET and compile into native code, as an option.
Stop thinking in terms of syntax. VB.net and C#.net have access to all of the same
The global economy is a great thing until you feel it locally.
Corrections gladly accepted. :)
By the way you guys are about a month late reporting this. This was orginally released on 9/20/2002. and here is a link to what they actually said instead of what the guy reported in the orginal post.
/ Thread.aspx?id=40466
http://www.gotdotnet.com/community/messageboard
To clear everything up here is the actual e-mail that was sent out
"By posting Your Stuff, You grant to Microsoft, under all of Your intellectual property and proprietary rights the following worldwide, non-exclusive, perpetual, irrevocable, royalty free, fully paid up rights: (1) to make, use, copy, modify and create derivative works of Your Stuff; (2) to publicly perform or display, import, broadcast, transmit, distribute, license, offer to sell, and sell, rent, lease, and lend copies of Your Stuff (and derivative works thereof); (3) to sublicense to third parties, including the right to sublicense to further third parties; and (ii) You agree You won't commence any legal action against Microsoft or any Participant or Visitor for exercising any of these rights."
We want to be clear that our intent was never to assume ownership of your code. In order to maintain a copy of your project on our servers and make it available for download by authorized users of your Workspace, we do need certain permissions from you (in legalese, we need licenses for certain of your intellectual property rights in your project). Based on your comments, we see that we were not sufficiently clear in conveying the intent of this section of the license. We apologize for the miscommunication in the license and hope the below changes will better represent our intent. The new section becomes:
"By posting Your Stuff to a Workspace, You understand and agree that you're giving a license under your intellectual property rights to all authorized users of the Workspace, including the rights to download, copy, modify, distribute and repost. In addition, you're giving Microsoft all the necessary rights to make Your Stuff available as part of the Project."
See unlike all the poor open source developers out there Microsoft actually has to cover it's ass leagelly so jackazzes from slashdot don't sue them.
In the original text, the key word that makes it unacceptable is that Microsoft would have the ability to license, as in "distribute, license, offer to sell". That could be construed as allowing MS to take, say, BSD-licensed source, and make it available under some other license. That they later say they had no intent to do so doesn't mean squat when you are in court arguing with them about it.
Well, apparently, you only have to fool the majority of people for a little while.
I work in the .NET & Developer Group at Microsoft UK. For the record, there is no UK version of GotDotNet - this is just someone cybersquatting. Check the whois record at Nominet.uk. There's no need for a UK version of course - this is a worldwide community site.
:-)
Interestingly, I notice that someone's registered slashdot.org.uk...
Tim
IANAL, but looking carefully at section 3.1, it seems you're not allowed to use MSVC's C runtime or several of their other libraries in "any software that requires as a condition of use, modification and/or distribution of such software that other software incorporated into, derived from or distributed with such software be (1) disclosed or distributed in source code form; (2) be licensed for the purpose of making derivative works; or (3) be redistributable at no charge.". That seems to be pretty squarely targeted at the GPL to me.