Earlier quoted context omitted.
Any company past circa 2002sh or so, and definitely by 2005, is intimately aware of their intellectual property responsibilities, and, it's the opposite problem that I've run into - in which tons of strawmen are thrown up as to the danger of infecting products with open source licenses makes it dangerous to touch the code. One of the reasons why BSD licenses are so attractive to corporations, is that they run the low…
> GPLv3 is obviously a non-starter for most companies "Non-starter" is a gross mischaracterization for GPLv3 for most companies , even most software companies, considering there is quite a bit of GPLv3 software in a modern GNU+Linux distro that they likely rely on.
Our lawsuit against ChessBase
71–80 of 261 posts
Re: Our lawsuit against ChessBase
#72I bet it’s next to impossible to prove copyright in this case. You would need to track down every last contributor and create a legally valid authorship evidence that is recognized under German legal doctrine. I would bet that having a email or even full name in a git repository is certainly not enough. This is exactly why for serious open-source projects that big companies depend on, they always creat a legal body,…
I don't see why they would need every last contributor. They only would need the contributors of the specific code that they allege was copied. That Stockfish contains other code by other contributors that may or may not have been copied would not be relevant.
Re: Our lawsuit against ChessBase
#73Earlier quoted context omitted.
Stockfish has an opportunity to make money here. No?
It will be interesting, depends where jurisdiction falls and how that jurisdiction interprets any alleged damages since GPL content is normally released free of charge.
Re: Our lawsuit against ChessBase
#74Re: Our lawsuit against ChessBase
#75https://sourceforge.net/projects/scidvspc/ http://caissabase.co.uk/
Re: Our lawsuit against ChessBase
#76Re: Our lawsuit against ChessBase
#77Earlier quoted context omitted.
Absent a license, ChessBase has no right to distribute any of the Stockfish code. This simply reverts the code to copyrighted content, much like a book.
Revert is not the correct term. GPL-licensed code is still and always copyrighted, even when GPL-licensed. The GPL is itself a copyright license. Only CC0/WTFPL/Public Domain are renunciations of copyright.
Also, when it comes to code dedicated to public domain it is good to consider what wikipedia says about implied warranty: "The licensing process also allows authors, particularly software authors, the opportunity to explicitly deny any implied warranty that might give someone a basis for legal action against them." It is always good to include a clause saying that there is no warranty, implied or otherwise (unless of course you provide a warranty, which you probably should not do without restrictions on OSS code).
Re: Our lawsuit against ChessBase
#78Earlier quoted context omitted.
I think they've revoked even Chessbase's license to use the code. So, not like a book, where if you have the physical copy you can generally read it, but more like a pirated copy of Windows or Oracle, where you owe license fees per user, per core, per day.
I'm not sure if it's settled law on whether or not you need to license to use code...
Re: Our lawsuit against ChessBase
#79Earlier quoted context omitted.
It will be interesting, depends where jurisdiction falls and how that jurisdiction interprets any alleged damages since GPL content is normally released free of charge.
Copyright infringement can have large statutory damages that have nothing to do with the actual financial damage from the infringement.
Re: Our lawsuit against ChessBase
#80The current title is "Our lawsuit against ChessBase – Stockfish – open-source Chess Engine", which I found confusing. Is Stockfish being sued? Does it belong to ChessBase? I suggest sticking with the simpler title from the blog, "Our lawsuit against ChessBase".
Looks like OP didn't clean up the url while submitting, it defaulted to page title.