Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Patents Open Source Software Your Rights Online

Tridgell Recommends Reading Software Patents 173

Posted by timothy
from the you-may-read-the-article dept.
H4x0r Jim Duggan writes "Andrew Tridgell rejected the common fears about triple damages: 'If you've got one lot of damages for patent infringement, what would happen to the project? It's dead. If it gets three lots of damages for patent infringement, what happens to the project? It's still dead.' Tridge then explains the right way to read a patent and build a legal defense: 'That first type of defence is really the one you want, it's called: non-infringement. And that is: "we don't do that. The patent says X, we don't do X, therefore go away, sue someone else, it's not relevant for us." That's the defence you want. [...] Next one, prior art: [...] Basically the argument is: somebody else did that before. It's a very, very tricky argument to get right. Extremely tricky, and it is the most common argument bandied about in the free software community. And if you see it in the primary defence against a patent, you should cringe because it is an extremely unsafe way of doing things.' There are even some tips in the talk specifically for Slashdotters."
This discussion has been archived. No new comments can be posted.

Tridgell Recommends Reading Software Patents

Comments Filter:

Promising costs nothing, it's the delivering that kills you.

Working...