News for hackers. Stuff that matters.
Re:Selling my own GPL software, part 1: a lot of hurdles by heavyset_go on Saturday December 25, 2021 @08:14PM (#29688735)
> Does looking at a pull request without a CLA "taint" me in a way that I cannot implement it again?

I'm not a lawyer, but I'm under the impression that if someone wants to sue you for IP infringement over something like this, they can. Doesn't mean they'll win, but that can still cost you time and money defending yourself.

If you do look at the code, I'd make sure your implementation is far from how the contribution was implemented.

Here's what IP Watchdog says[1]:

> Copyrights cover the actual “expression” of an idea, but not the idea itself. In other words, it covers the lines of code but not the functions that they perform. The functions can be protected as trade secrets, or they can be patented. Sometimes it’s difficult for someone unfamiliar with IP law to separate the functionality from the expression in source code. This so-called “dichotomy between idea and expression” is particularly confusing with respect to software, and was addressed in the case Whelan Associates v. Jaslow Dental Laboratory and then again in Computer Associates v. Altai.

The article[1] then expounds upon literal and nonliteral copying and how it applies to source code.

[1] https://www.ipwatchdog.com/2017/02/07/facebook-oculus-zenima...

Re:Selling my own GPL software, part 1: a lot of hurdles by eslaught on Saturday December 25, 2021 @11:59PM (#29689858)
This didn't quite answer the gp's question.

There's an idea in some software communities that you can't "unsee" code. So if you've seen the code even once, you're "tainted" and you can't be permitted to work on the clean room implementation anymore. This tends to be used most often in projects attempting clean room implementations of proprietary software where they want to maintain clear provenance of the code.

The question is, is this based on actual case law or is it just an extreme form of paranoia?

Re:Selling my own GPL software, part 1: a lot of hurdles by eesmith on Sunday December 26, 2021 @01:00AM (#29690130)
It's not an extreme form of paranoia. I see it as a cost-analysis. It's cheaper to defend any copyright infringement criticism or lawsuit when using a pure clean room design.

We know that modified derived software can be sufficiently distinct from its base that the original copyright no longer applies. Quoting https://en.wikipedia.org/wiki/Clean_room_design :

> In NEC Corp. v Intel Corp. (1990), NEC sought declaratory judgment against Intel's charges that NEC's engineers simply copied the microcode of the 8086 processor in their NEC V20 clone. A US judge ruled that while the early, internal revisions of NEC's microcode were indeed a copyright violation, the later one, which actually went into NEC's product, although derived from the former, were sufficiently different from the Intel microcode it could be considered free of copyright violations.

However, such a lawsuit will be much harder and therefore more expensive to deal with.

It's much cheaper to make the argument that none of the developers had access to the original source or reversed-engineered design, so any similarities must be result of functional constraints or general knowledge.

Re:Selling my own GPL software, part 1: a lot of hurdles by swiftcoder on Sunday December 26, 2021 @04:51AM (#29691022)
Keep in mind that many of these "cleanroom" implementations are aiming to dodge patents, not just copyright
Re:Selling my own GPL software, part 1: a lot of hurdles by eesmith on Sunday December 26, 2021 @04:23PM (#29696516)
Clean room design cannot dodge patents.

If you have a patent then that protects your invention, even if I unknowingly and independently come up with the same invention.