Slashdot Mirror

← Back to Stories (view on slashdot.org)

Contracts Contracts Contracts

Posted by timothy on from the ignore-the-print-and-sign-here dept.

An anonymous reader submits: "There's an article over at CNet about all those software contracts that are out there, and what to watch for before signing the dotted line. Using California's $95 million Oracle problem, they define what the general terms are that get used in software procurement and support contracts. While mostly geared at commercial software, one can use most of this article to target open source tech support contracts."

1 of 70 comments (clear)

  1. Should have Standardized EULAs by Anonymous Coward · · Score: 5, Interesting


    In several other industries, there are "standard contracts", and I think it is well past time that became the case in the Software Industry. A specific example is the Building/Construction industry. They have "AIA" (I forget what that stands for, but it should be easy to find) standard contracts that they can call on so everyone is on the same page. A very good idea.

    One reason I love Open Source software is that there are only a few licenses that I have to know about, and just by knowing the name of them, for example knowing something falls under the "GPL", or a "BSD" license, I know EXACTLY what to expect. This is of immense value to me as a user of software.

    I think that property should be more heavily emphasized by the Open Source industry.

    Frankly, I don't know why people put up with the EULA uncertainty and why the courts let Software companies take advantage of people in that fashion. They don't for most other products, heck even "media/content" products.

    Erich Boleyn
    erich@uruk.org