Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Tridgell recommends reading software patents

H4x0r Jim Duggan (757476) writes | more than 4 years ago

Patents 1

H4x0r Jim Duggan (757476) writes "In a recent talk, 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."
Link to Original Source

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

But the claims are in a write-only language (1)

bersl2 (689221) | more than 4 years ago | (#31572822)

We read enough write-only code out there. Now we're expected to read write-only legalese?

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>