EULAs and Car washes: CrossOver by CodeWeavers

(Another post in the erratic series, Adventures in IT Contracting)

Proving that you can have a little fun with drafting EULAs…

CrossOver License Grant

YOU REALLY WANT TO READ THIS, ESPECIALLY THE PART ABOUT THE MANDATORY CAR WASH FOR CODEWEAVERS EMPLOYEES...

If you don't like this license grant:

a. Let us know, we'd appreciate the feedback.

b. Stop right now, and ask for a refund. We'll cheerfully do so.

The main thing we want you to know:

This is a license for one user. The license is not necessarily for a specific user, or a specific computer, but it is for one person at a time. If you need to support more than one person, please contact us for volume pricing and site licensing. We do offer educational discounts.

I like the very plain language summary provided at the beginning of the EULA, especially as it answers the very frequently asked question, around educational discounts and offers a clear opportunity to refuse the terms. As a whole, the full EULA is fairly plain language.

See, EULAs don’t have to be boring!

Posted in Adventures in IT Contracting | Tagged , | Leave a comment

Tasty links: up to 23 Feb

Stuff you might like to check out on teh internets for 21 Jan through 23 Feb:

Posted in Teh Internets | Tagged | Leave a comment

Non competes in IT software contracts

The beginning in a potential series of posts to be categorized as “Adventures in IT Contracting”, whereby your somewhat faithful blogger endeavors to post about some of the odd and downright puzzling terms found in IT software and SaaS/Cloud contracts.

Up first is a non-compete clause in a EULA:

For a period of one (1) year (365 days)[*] from the date of purchase, you agree not to create software, independent of <THE SOFTWARE>, which might directly compete with <COMPANY> products.

I’m not a competition lawyer, but this sort of thing does strike me as questionable from the view of competition/anti-trust. How enforceable is this really? I’d also be very wary of a commercial strategy that tries to rely on the effectiveness of this clause in order to keep or gain a position in the market.

What about scope? Does it cover any development — such as creating software internally to replace this licensed software, or would you read in a requirement to try to commercialize the result? If someone is developing their own “home grown” solution and keeping it wholly internal, how would you detect this development? If you can’t detect, you can’t enforce.

I think this sort of clause is also just increasing the chances your customers will want to negotiate the EULA with you, and thus eat up time and resources (for you and them) for seemingly not much gain.

[*] Incidentally, as a drafting point why do you need to highlight that a standard calendar year is 365 days? In so doing, aren’t you also creating confusion for leap years, which have 366 days? This just seems like bad drafting to me.

Thoughts and other war stories always welcome.

Posted in Adventures in IT Contracting | Leave a comment

Gender and contract drafting

I came across this clause in a legal document the other day:

Words importing the masculine gender only shall include the feminine gender and the neuter (as appropriate) and vice versa.

First, “the neuter gender”? Really? I’m not sure what a linguistic distinction on grammatical gender has to do with contract construction here. I’ve seen this sort of clause before, but never with “the neuter gender” included.

At first blush, this looks like boilerplate safely skimmed and ignored (well, except for the neuter thing, which stuck out like a sore thumb to me).

But when would putting this clause into a contract be worth it? To make an already gender-biased contract seem more palatable to the reader? To avoid what would often be a plainly erroneous construction of the contract by limiting it to one gender, when both were clearly intended despite use of “him” or “his”?

It seems to me that any competent drafter should be able to create a new document without the kind of inherent gender bias that would require this clause. Neither do I see much of a point trying to go back and add this clause to an existing contract — if you’re going for that level of detail, then you may as well chuck it out and go for a whole new (correctly drafted) agreement.

Finally, I suppose that this sort of clause could be looked as some sort of catch all to include other concepts of gender, as in the social roles, behaviour, etc based around sex. If so it does so poor a job at capturing gender identity, third gender, transgender, genderfuck, and other related issues as to not rate including in a contract.

These clauses strike me as needless surplus to modern contracts and should be abandoned. Drafting gender neutral contracts should be a given.

Posted in Legal writing | Tagged , , | 1 Comment

Public domain dedications: MD5

Another in my series of highlighting various public domain dedications. This time, MD5:

MD5 (md5.cpp and md5.h) This code implements the MD5 message-digest algorithm. The algorithm is due to Ron Rivest. This code was written by Colin Plumb in 1993, no copyright is claimed.

This code is in the public domain; do with it what you wish.

Mathematical formulae generally aren’t copyrightable, so insomuch as this is solely an algorithm and not code implementing that algorithm, copyright wouldn’t subsist in the first place. So in the case of the Rivest algorithm mentioned, it’s good to know that copyright isn’t being claimed over it despite the chances of it existing are pretty close to nil.

For the code however, it could very well have copyright. Copyright is automatic — you don’t have to apply for a copyright in order to have one. Copyright “flows from the pen to the paper”, as they say (or in this case from the fingertips to the keyboard). Since copyright subsists, I think more accurate drafting would be to say that “copyright is waived”.

In either event, the MD5 text gives a clear intent to give up all copyright, and if the copyright couldn’t be technically waived on the basis of this for some reason, then I would think a court would read in a very very broad license in its place.

Posted in Copyright, Licensing, Public Domain | Leave a comment

Tasty links: up to 20 Jan

Stuff you might like to check out on teh internets for 10 Dec through 17 Jan:

Posted in Teh Internets | Tagged | Leave a comment

New OSBR column: There is no “Creative Commons license”

… rather there are “Creative Commons licenses” (plural). My second column at Open Source Business Resource discusses why it’s important to be clear on exactly which license is meant when discussing Creative Commons licenses:

14 January 2011 – There is no Creative Commons license

Posted in Creative Commons, Licensing | Leave a comment

Public domain dedications: The sqlite3 blessing

At the most basic level, it doesn’t take much to do a public domain dedication or ultra-permissive license for copyright. Some people certainly have a lot of fun with it, while others, such as the sqlite blessing, take a much more kindly tone:

/bin/sqlite3

2001 September 15

The author disclaims copyright to this source code.  In place of a legal notice, here is a blessing:

  May you do good and not evil.

  May you find forgiveness for yourself and forgive others.

  May you share freely, never taking more than you give.

This one was for software, and could easily be modified for other content — though I strongly believe using established dedications such as CC0 or the PDDL give many more advantages than rolling your own.

If you have any interesting public domain dedications or licenses, please do send them along.

Posted in Licensing, Public Domain | Tagged , | Leave a comment

From patents to open data: Participate and shape EU digital policies

Via FFII comes this list of active consultations and surveys covering everything from patents and innovation through to privacy and open data and PSI.

Posted in Innovation, Patents, Policy, Privacy | Tagged , , , , | Leave a comment

New OSBR column: Pitfalls of Open Gov Data Licensing

I’m happy to announce that I’ll be a regular columnist with Open Source Business Resource. The first column:

November 19: Pitfalls of Open Government Data Licensing

Posted in Licensing, Open... | Tagged , , | Leave a comment