Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Microsoft Calls for Truce With GPL and Linux? 464

An anonymous reader writes to mention an eWeek article discussing Microsoft's efforts to reach out to the open source community. The company is hoping to find a common ground with softare released under the GPL, so that OSS and Microsoft products can interoperate. From the article: "The goal, from both sides, is to meet customer needs, he said, adding, 'This is just the more mature view of the way the world is evolving, and we want to make sure that if customers are choosing Linux or other open-source-based products that we have ways of interoperating and working effectively with that.'" A related article mentions Windows server Expert Jeremy Moskowitzs' call for a truce between the Linux and Windows communities.
This discussion has been archived. No new comments can be posted.

Microsoft Calls for Truce With GPL and Linux?

Comments Filter:
  • by khasim ( 1285 ) <brandioch.conner@gmail.com> on Tuesday June 13, 2006 @12:40PM (#15524986)
    This is the way Microsoft fights.

    Look for proprietary Microsoft "extensions" in the near future. All for the sake of "user friendly" and "customer needs".
  • by mpapet ( 761907 ) on Tuesday June 13, 2006 @12:40PM (#15524989) Homepage
    This is the tactic to "cooperate" with OSS as long as the money flows into MS's coffers.

    This strategy would suck the economic oxygen out of OSS.
  • by also-rr ( 980579 ) on Tuesday June 13, 2006 @12:43PM (#15525022) Homepage
    It's designed to spec, the APIs are public and the source code is out there. Step 1) Microsoft freeze and publish their APIs under a GPL compatible license so that existing interop OSS projects such as Samba can polish the last couple of percent into their products. Step 2) Microsoft adapt their software to work with established standards such as PDF, ODF, OpenGL, HTML etc etc etc. Step 3) There is no step 3. OSS stuff *already* interoperates with anything written to open standards, as well as rather a lot of closed standards. I fail to see what more they need to do.
  • Windows Networking (Score:5, Insightful)

    by rjdegraaf ( 712353 ) on Tuesday June 13, 2006 @12:43PM (#15525027)
    Microsoft, show your intention by opening Windows Networking!
  • by Solra Bizna ( 716281 ) on Tuesday June 13, 2006 @12:43PM (#15525028) Homepage Journal

    So, what do you call WINE, Samba, Cygwin? (Tons more, but I don't deal with Windows often enough to have more names...)

    -:sigma.SB

  • by cnelzie ( 451984 ) on Tuesday June 13, 2006 @12:44PM (#15525038) Homepage
    Are you posting from a different dimension?

        Open Source Software developers have been working very hard for years to create interoperatibility for working within MS Networks. Just look at OpenLDAP, Samba and a number of other systems that have been written to bring *nix and MS products into a state of being capable of communicating with one another.

        Microsoft has had a history of moving the goal posts, for no apparent reason other then to undermine the efforts of the OSS teams working on things like Samba, OpenLDAP and many others.
  • by BFaucet ( 635036 ) on Tuesday June 13, 2006 @12:46PM (#15525058) Homepage
    So they want to benefit from all the work done for OSS projects without contributing any work back?

    Am I missing something?
  • by Anonymous Coward on Tuesday June 13, 2006 @12:48PM (#15525079)
    You need to consider: since when has the Linux/FOSS community ever deliberately made something not-interoperable with Windows? There are a few times and reasons, I'm sure, many of them strictly legal reasons, or adhering to some standard instead of adopting broken behaviours... but Microsoft really has no place to complain about their treatment, at least from a software development point of view.
  • by Mprx ( 82435 ) on Tuesday June 13, 2006 @12:51PM (#15525121)
    Ignoring the blatant lie that the GPL is incompatible with "intellectual property" (the GPL *depends* on copyright for its effectiveness), this whole article is clearly designed to obscure the real issues.

    The article is correct in that "Open source is a way of building software", but the GPL is primarily concerned with Freedom, not the practicalities of building software. You'll notice Microsoft never refers to Free Software, only Open Source. Open Source *is* primarily concerned with the development methodology, and by concentrating only on this issue Microsoft implies that Freedom is unimportant. There's a great danger of thinking only of Open Source, and then ending up in a situation not much better than if you had used proprietary software. Open Source doesn't necessarily mean Free.
  • open the window (Score:4, Insightful)

    by Whammy666 ( 589169 ) on Tuesday June 13, 2006 @12:51PM (#15525122) Homepage
    If M$ wants to appease the OSS group, they need to open the windows API spec. They don't need to publish any source code. Just the specs. The old DOS api is fully spec'd, so why not windows? After all, competition is good for the consumer and promotes innovation. Isn't that what M$ claims it's trying to promote?
  • Article? (Score:3, Insightful)

    by The Z Master ( 234139 ) on Tuesday June 13, 2006 @12:51PM (#15525124)
    That wasn't a news article. It was an interview. Notice how the reporter didn't get any opinions from major open source players. The entire text was either a quote or a paraphrase of Bob Muglia. Seems a bit one-sided if you ask me.
  • by kuyaedz ( 921036 ) on Tuesday June 13, 2006 @12:54PM (#15525150)
    I couldn't have said it any better. They have bent-over-and-screwed anyone that has partnered with them when it suits their needs. They will continue to do the same. Don't trust 'em, don't listen to 'em. They have shown time & time again that they can't be trusted.
  • by harrkev ( 623093 ) <kevin.harrelson@ ... om minus painter> on Tuesday June 13, 2006 @12:56PM (#15525177) Homepage
    Or publish NTFS specs so that the open-source community can use it.
  • by Keith Russell ( 4440 ) on Tuesday June 13, 2006 @12:58PM (#15525191) Journal

    Let's see. On one side, we have Microsoft, singular colossus of the industry, abuser of monopoly power, left with naught but a nano-scale layer of public trust. On the other side, we have a great mass of Open Source/Free Software advocates, where the moderate voices are undermined by those whose rational distrust of Microsoft has turned to irrational paranoia and hatred.

    I hope there's a Plan B, because this whole "Us vs. Them" thing isn't leading anybody anywhere.

  • by Secrity ( 742221 ) on Tuesday June 13, 2006 @12:59PM (#15525206)
    "we want to make sure that if customers are choosing Linux or other open-source-based products that we have ways of interoperating and working effectively with that."

    OSS products are by definition "open", meaning that it is up to MS to make the next move by publishing its API's, stop changing API's, stop doing crappy things to the OSS community, and to change it's licensing to allow FOSS programmers to use suposedly "open" MS products.
  • Hitler and Russia (Score:3, Insightful)

    by WindBourne ( 631190 ) on Tuesday June 13, 2006 @01:00PM (#15525216) Journal
    MS needs time to focus on one threat at a time. Their single greatest threat is Google. If they can get everybody to play nice with them for a time, they can take out google. Once that is done (or perhaps even before), they will simply go on the attack for the next target. Gates has the same ethics as Hitler (try to crush your enemies and own your friends when you are able to).

    Now, is the time for the FOSS world to be more like the UK and America of old, rather than to roll over.
  • by tolan-b ( 230077 ) on Tuesday June 13, 2006 @01:02PM (#15525237)
    Er.. Open Source is generally based on open standards. It also tends to implement them without proprietary patented extensions.

    Where exactly is OSS not being inter-operable?

  • by morgan_greywolf ( 835522 ) on Tuesday June 13, 2006 @01:05PM (#15525274) Homepage Journal
    It's designed to spec, the APIs are public and the source code is out there. Step 1) Microsoft freeze and publish their APIs under a GPL compatible license so that existing interop OSS projects such as Samba can polish the last couple of percent into their products. Step 2) Microsoft adapt their software to work with established standards such as PDF, ODF, OpenGL, HTML etc etc etc. Step 3) There is no step 3. OSS stuff *already* interoperates with anything written to open standards, as well as rather a lot of closed standards. I fail to see what more they need to do.

    Remember this: Microsoft's goal is to win. For Microsoft to win, everyone else has to lose. You need to learn Microsoft lingo: 'Interoperability' for Microsoft means 'embrace and extend'. 'Truce' means no more Samba, no more OpenLDAP, no more WINE, no more Exchange connectors, no more Linux, etc. See 'everybody wins'! ('Everybody' meaning 'everybody with stock options at Microsoft').

  • by harrkev ( 623093 ) <kevin.harrelson@ ... om minus painter> on Tuesday June 13, 2006 @01:07PM (#15525297) Homepage
    Wine -- Make Windows software work on Linux
    Open Office, Cygwin,etc. -- Make Linux software work on Windows.

    Samba -- Make Windows servers work with Linux clients
    Samba -- Make Linux servers work with Windows clients

    VNC,X -- Make Windows terminals work with Linux servers
    VNC, Remote Desktop client -- Make Linux terminals work with Windows servers.

    All of these are done by open-source developers. So, tell me, what more would you like open-source people to do? And do you see ANYTHING that Microsoft has done?

    It is easy to throw blame around if you ignore the facts.
  • by Anonymous Coward on Tuesday June 13, 2006 @01:09PM (#15525320)
    "This is the way Microsoft fights.

    Look for proprietary Microsoft "extensions" in the near future. All for the sake of "user friendly" and "customer needs"."

    I don't know why this gets modded "troll." Its a simple fact that if things happened consistently in the past, its safe to say that unless something changes to affect results, they'll probably happen again in the future. Given Microsoft's history of decisions (and just about any other megacorporation in power), its safe to say they will try to protect their market share by...you guessed it...any means possible. This isn't "troll", this is most likely the simple truth.
  • I call Bullshit (Score:5, Insightful)

    by Foofoobar ( 318279 ) on Tuesday June 13, 2006 @01:12PM (#15525363)
    How does OSS inhibit Microsoft? How does making all source code available to them for viewing inhibiting their ability to integrate? How does working with open standards available for everyone to use inhibit Microsoft?

    I don't see your point. Seems like only one side is using closed standards, proprietary code and closed APIs. I don't see how open source is to blame in this matter at all.
  • by C0deM0nkey ( 203681 ) on Tuesday June 13, 2006 @01:16PM (#15525390)
    First, let me say that I agree that congress is a bigger concern than Microsoft but...

    This is not good news. This is a PR stunt and only a PR stunt. This allows Microsoft to say "See...we tried to play nice but they wouldn't play with us. It's their fault not ours; we wanted interoperability but they wouldn't have it." Bullshit. It is almost certain that the type of "interoperability" they desire will only come in terms of closed-source, for-profit products and encumbered IP. I have no problem with this, mind you, but do not delude yourself about this truce: anything they offer that is truly open will likely be end-of-life and irrelevant shortly thereafter.

    What does a "truce" with Microsoft look like exactly? Do you think MS is going to open up their proprietary protocols and data formats to the OSS community? How would that work, exactly? What exactly does OSS gain from a truce with Microsoft given that we can assume that they will not be any more likely to open their formats and tools than they are now?

    Don't get me wrong: it is perfectly within Microsoft's rights to keep their IP closed and to charge access for it but do not deceive yourself about them wanting to suddenly play nice. What happens if/when some of that proprietary stuff leaks into OSS? Could that be what they are hoping for? Hoping OSS developers, lured under the guise of a truce, think they have rights to use information that they do not - poisoning the well, perhaps?

    What about evangelism? Under this supposed truce, are we supposed to stop pointing out the weaknesses in Microsoft's products and methodologies in return for the same? Why would we do that? Who wins in that situation? Certainly not OSS which relies heavily upon word-of-mouth and grass roots efforts to spread; Microsoft wins because potentially fewer people are made aware of other choices that may exist both for operating systems and tools.

    I realize this could be taken as an anti-Microsoft rant but what it really is is a "Don't trust Microsoft" rant. These guys are convicted monopolists who have a reputation for stabbing their partners in the back and putting them out of business. Why would/should we trust them when they say they want to make nice?

  • start opening your formats and protocols, dammit... I'm sick tired of following the internet standards in my programs to see that they won't work with Microsoft Software. An example: The Microsoft "Web Folders", supposedly compatible with webdav, didn't work when connecting to an apache webdav directory. Days of research thrown into the garbage.
  • the "community" (Score:5, Insightful)

    by johnMG ( 648562 ) on Tuesday June 13, 2006 @01:21PM (#15525445)
    From the article:
    > It's time for the Windows and Linux communities to drop the religious war and [snip]

    There _is_ no "Windows community". It's just a giant company and a lot of customers.

    > [snip] until the two communities put aside the whole "religion" issue, said Jeremy
    > Moskowitz, a consultant and authority on Windows 2000/2003 Server, Active Directory
    > and SMS [snip]

    {sigh} There's no "religion issue". There's free software users who write a lot of
    code that they want to remain free. It's their work -- and they want it to stay free.
    If you don't like the terms, don't use the software. That's it. There's no religion
    there. Now, maybe the Microsoft corporation has a "religious issue" -- like, maybe
    it's their religion to dominate the software industry and they don't like there
    being anyone else supplying software to the world...

    Anyhow, this article seems to be mostly shilling for MS. The author tries to trick
    the reader into believing the author's presuppositions and also relies pretty heavily
    on quotes from this Moskowitz "authority".

    > "At the end of the day, both Windows and Linux bring things that are good, and we
    > can all get along and we should look at how we can leverage the strength of each
    > to the benefit of the other," he said.

    Bleh. What garbage. The free software community wants to get along just fine --
    they're _giving_ away their work for goodness' sake.

  • by AJWM ( 19027 ) on Tuesday June 13, 2006 @01:22PM (#15525460) Homepage
    The whole notion of a "truce" is silly. Other than writing better software, how is Linux attacking Microsoft? Nobody on the FLOSS side is, AFAIK, suing Microsoft for anything. Heck, OSS licenses don't even prohibit running so-licensed software on MS operating systems -- which is more than can be said for some MS EULAs regarding non-Windows systems.

    So, just what is it they want to stop?

    And why should we accept anything less than unconditional surrender?

  • Open source already operates according to open standards...
    All microsoft need to do, is implement and support the same open standards. This "war" they talk about having a truce in, is because their products are using proprietary formats and/or protocols, which force people to use their products.

    People like choice, whereas microsoft try to take away your freedom of choice because that's easier for them than offering a better choice in a free market.

    If they would make sure all their products complied with published standards (or help create such standards, where non already exist, and in an open way involving any interested parties), then opensource would have less of a need to compete and fight against them.

    All i want, and i`m sure many people agree, is freedom to choose. I absoloutely despise the idea of being forced to use any particular product, i want to be able to choose whatever suits my individual needs best.

    Currently i won't use microsoft products, because they seek to remove my freedom of choice... If they implement open standards and provide me this freedom i would consider using them based on the merits of each individual product.
  • by Lead Butthead ( 321013 ) on Tuesday June 13, 2006 @01:28PM (#15525555) Journal
    Microsoft offering an olive branch reminds me a lot of the cease fire right before Tet Offensive.
  • by walt-sjc ( 145127 ) on Tuesday June 13, 2006 @01:28PM (#15525564)
    When MS stops doing stupid shit like requiring a license for Sender-ID, THEN we know they are serious.

    The onus is on Microsoft's side to change - not on the GPL's side. Talk is not change.

    Why did I bring up Sender-ID? Because it's a prime example of how non-GPL and GPL applications interact, without even getting into compiling and linking issues.
  • by AJWM ( 19027 ) on Tuesday June 13, 2006 @01:32PM (#15525605) Homepage
    Which is why nobody in their right mind would use Mono for any production code.
  • by Bitsy Boffin ( 110334 ) on Tuesday June 13, 2006 @02:02PM (#15525934) Homepage
    Said the cunning Spider to the Fly, " Dear friend what can I do,
    To prove the warm affection I 've always felt for you?
    I have within my pantry, good store of all that's nice;
    I'm sure you're very welcome -- will you please to take a slice?"
    "Oh no, no," said the little Fly, "kind Sir, that cannot be,
    I've heard what's in your pantry, and I do not wish to see!"
  • by yo_tuco ( 795102 ) on Tuesday June 13, 2006 @02:07PM (#15525985)
    And when you read inbetween the lines, Microsoft's idea of a truce is that Open Source surrenders.
  • by mgpeter ( 132079 ) on Tuesday June 13, 2006 @02:35PM (#15526330) Homepage
    - Where are they whenever there is a CIFS meeting ??

    - Where did they go once ODF was being finalized ??

    - Why don't they let the Mono guys present at Windows Conferences ??

    If Microsoft wants interoperability they must realize that interoperability does not mean everyone else bending over backwards for them. It means working with other Companies/Individuals to ensure that EVERYONE benefits from it, not just Microsoft.
  • Great/NTFS (Score:3, Insightful)

    by Devil ( 16134 ) on Tuesday June 13, 2006 @02:51PM (#15526505) Homepage
    This is fantastic! So, when can we expect to see Microsoft release an NTFS API that allows users to safely read and write to those volumes?
  • by Belial6 ( 794905 ) on Tuesday June 13, 2006 @02:59PM (#15526579)
    Of course code not being free hasn't stopped MS from taking it and selling it in the past. Break out that old copy of DOS 6.0 from the garage. Do a hex search for "STACKER". That's right. Right there in MS's code is a Stacker Inc. copyright notice. They didn't even bother to remove the original authors copyright notice before they illegally used it.
  • I don't think that Linux has ever been at war with anybody. Nor has there been any license problems. The problem has been with a company like Microsoft that wants to use other people's things and close them up so no one else can use them, invoke vendor lock-in and make choice of non-Microsoft solutions impossible or nearly so. Microsoft doesn't like the GPL because they aren't allowed to take the developments of others and not share as well. Microsoft loves the BSD license because it allows them to do exactly that.

    The only thing the GPL does is that it requires you publicly redistribute, on the same terms as the stuff you got, any changes that you make. It does not stop you or in any way prevent you from independently developing the same software. Nor does it attempt to prohibit you from running other software which use other licenses or operate on other systems. Microsoft has routinely used its EULAs to do exactly that. This is Microsoft's war, not Linux's, and Microsoft is the only one that can end this war, when it chooses to stop fighting. But to do that would require Microsoft to change the way it has been doing business.

    Microsoft has become rich as a result of proprietary software and vendor lock-in, and for it to change its way of operating to no longer do this would require a complete change of outlook. (Pun unintentional)

    Paul Robinson

  • by peterfa ( 941523 ) on Tuesday June 13, 2006 @03:13PM (#15526734)
    Why doesn't the author get the facts? I have some damn proof right here: http://www.microsoft.com/windowsserver/facts/defau lt.mspx [microsoft.com] Look at all these lies.. and he has the balls to say Microsoft is calling truce?

    Yeah, Microsoft is calling a truce... I soooo fucking believe that.

  • by Odin_Tiger ( 585113 ) on Tuesday June 13, 2006 @03:33PM (#15526899) Journal
    *Dons his flame-retardant suit...

    I wouldn't say that it's totally on MS to change. The GPL makes it very scary / tricky / hard for a business which is based on proprietary software to work with anything that has the 'taint' of the GPL on it. The GPL license could certainly be more big business friendly, without giving up it's...uhm... FOSSicity ...yeah. The GPL is like the T-Virus...everything it touches gets infected.

    The problem is basically a case of 'minority rule'. A minority of code, if it is GPL, forces the entirety to be GPL. To compare to current events in the real world, imagine if allowing illegal Mexican immigrants citezenship meant that everybody in America became hispanic, or that allowing gay marriage would cause all Americans to instantly become gay. Now I'm not against gay marriage, but I'm straight and I'm happy to be that way. I think this is what MS is dealing with: trying to find a middle ground where GPL software can be GPL and proprietary can stay proprietary and still both be able to play nice together.

    The GPL does not do a very good job of respecting the wishes of the writers of non-GPL code who want to work with GPL code, and especially if you're in the shoes of such as MS, it can easily appear to have been written that way specifically out of spite towards big business. I think what MS is hoping for here is that folks who want to work with big business will begin to release under less severe licenses, or that a GPL will be written with more allowances than what currently exists.
  • by flacco ( 324089 ) on Tuesday June 13, 2006 @03:36PM (#15526923)
    What else? If they want to talk about "cooperation", then we should be able to give them a list of items that they can start "cooperating" on.


    behead everyone in senior management and put their heads on sharpened sticks lining the drive to the microsoft campus in redmond, to serve as reminder to future generations of ms managers.

  • by esper ( 11644 ) on Tuesday June 13, 2006 @03:59PM (#15527120) Homepage
    Why should the GPL respect the wishes of someone who wants to appropriate it, base commercial software on it, make money selling the commercial software that's based on someone else's GPL code, and give nothing back?

    If I release code under the GPL and you want to use it in a closed-source project, come to me and see if you can get access to it under an alternate license. Just be aware that if you intend to make money off using my code, there's a good chance that your alternative licensing will include sending some of your profits in my direction.
  • by sfjoe ( 470510 ) on Tuesday June 13, 2006 @04:13PM (#15527233)
    The suit from Microsoft continues with the company-mandated propaganda, "A commercial company has to build intellectual property, while the GPL, by its very nature, does not allow intellectual property to be built, making the two approaches fundamentally incompatible", Muglia said.

    How is this a truce? How is this even slightly different from the FUD Microsoft regularly churns out? Is this the new strategy - to portray themselves as reasonable people being unfairly targeted by the open-source community?

  • by EndlessNameless ( 673105 ) on Tuesday June 13, 2006 @04:26PM (#15527354)
    There is evidence for your point of view as well. Microsoft basically made a truce with IBM to develop a product together in order to better serve their customers. At the last moment, Microsoft pulled their support and rolled many of the technologies they developed in partnership into their own product.

    This is the (abbreviated) history of OS/2, with the resulting Microsoft product being Windows NT. While the open source community can gain a huge measure of legitimacy with the general public through this proposed truce, I would encourage open source developers of any major project to embrace the publicity but keep a close eye out on their "partner".

    I just hope that the open source folks who are moderate enough to accept a truce with Microsoft are also wary enough to avoid being shanked in the back.
  • DirectX (Score:2, Insightful)

    by mqduck ( 232646 ) <mqduck@@@mqduck...net> on Tuesday June 13, 2006 @04:29PM (#15527381)
    How about opening up DirectX? That's about the only thing I'd care about here anyway.
  • by mrchaotica ( 681592 ) * on Tuesday June 13, 2006 @05:10PM (#15527701)
    Because the GPL does not cover distribution etc. If you don't want people to use your code in commercial software, say so in your own distribution aspect of the license of the code, instead of the lazy route of not listing restrictions on distribution and just relying on the GPL to force people to GPL their code as well. The GPL doesn't just hurt proprietary software companies, it hurts -everybody- who wants to use GPL code in non-GPL software.

    What you seem to not realize, though, is that that is exactly what people who decide to license their software with the GPL intend.

  • by babbling ( 952366 ) on Tuesday June 13, 2006 @09:26PM (#15529077)
    First the FUD: "One of the things I have learned is that engineers who work on commercial software really can't work on open source on GPL and engineers who work on GPL can't work on commercial software. You really have to separate the two," he said.

    That's a load of crap, unless Microsoft is the one not letting GPL programmers also work on commercial software. Has Microsoft ever heard of Red Hat, or are they really that out of touch with what is going on in their industry?

    Ahh, and then the trick: "A commercial company has to build intellectual property, while the GPL, by its very nature, does not allow intellectual property to be built, making the two approaches fundamentally incompatible, Muglia said. Licenses like the BSD (Berkeley Software Distribution) and commercial software, on the other hand, are quite compatible with one another, he observed."

    What's the main difference between the BSD license and the GPL? If Microsoft were to use the GPL in a piece of their software, they would have to give us the code for that piece of software, and with BSD they would be able to just take the code, use it, and never have any further obligations.

    In other words, this call for a "truce" just translates to "stop using a license that would make us share our code with you if we use some of your code!"

    He doesn't understand what the Free Software movement is: The goal, from both sides, is to meet customer needs, he said

    The goal on the GPL side is to provide everyone with Free (as in 'freedom') Software that they can use and contribute to. The goal on Microsoft's side is to make as much money as possible, however they can.
  • by walterbyrd ( 182728 ) on Tuesday June 13, 2006 @10:10PM (#15529268)
    Msft is still funding the scox-scam, among msft many other backstabing, system-abusing, practices.

    It's like somebody saying "hey, let's stop fighting" while they're stopping on your face.
  • by KWTm ( 808824 ) on Tuesday June 13, 2006 @10:33PM (#15529362) Journal
    I thought we were done with this piece of FUD, as it hasn't dared show its face on Slashdot for a while now, but I guess there are people who still don't get it, so let me try my hand at making things obvious.


    So you think it's perfectly fair and reasonable to ask others, be it MS or random Joe Coder, to reinvent the wheel simply because the license on your software precludes their use of your code with theirs, possibly due to reasons outide their control. How was it, again, that you are better than MS?


    So you think that the GPL is unfair and unreasonable. So ignore it! That's right, just pretend that the GPL isn't even there! It even says right in the GPL itself that you can do this. (Paragraph 5: "You are not required to accept this license.")

    There's your answer. Act as if the GPL doesn't exist, and do whatever you want with the software (as long as it's legal, of course)! Comb through the source code. Check out how it works. Make a bazillion copies. Change it around, and make your own version of the program. Better yet, combine it with another brilliant program of yours to make a super-program. Sell it and make a million--

    Oh, wait. That's against the law --you'd be breaking copyright. You wouldn't want to do something illegal, would you?

    Fine, just bundle it for free when you sell your--

    Oh, darn. That's not legal either.

    Umm, be a nice guy in general and post it on the web for people to download? Donate the program to a charitable organization?

    Nope, that's against the law, too. Damn.

    Hmm, what to do? Well, maybe you can ask the original programmer to sell you the rights to the program, so you can use it. Or perhaps you could give royalties. With enough financial incentive, maybe the programmer would be willing to transfer the rights to you.

    But sometimes software is created by more than one person, and you'd have to negotiate with each of the authors to get the rights to the complete program. Sometimes even contacting one of the original authors can be a big hassle.

    If only there were some way for the authors to state ahead of time, under what sort of conditions they would be willing to give you the rights to their program. This way, if you didn't want to negotiate, you'd still have the option of just fulfilling their conditions, and they've already agreed ahead of time that you get their permission --without your even needing to contact them! You know, some sort of text that they could include with their program (or put up on their web site) that explains all this clearly. They could call it a "document of giving permission". Hey, come to think of it, someone should come up with a word in the English language that means a "document of giving permission".

    I'll let you take it from there. Let us know if you come up with any great ideas.

To the systems programmer, users and applications serve only to provide a test load.

Working...