I said nothing about R1 (not beta).bob wrote:Sorry but that is naive. I have sold commercial rights to other programs. They included the standard disclaimer in the contracts that made it clear that any copyright issues would be mine and mine alone. I just did one of these 6 months ago with a company in the UK in fact. They don't have the time to do this kind of analysis, taking an executable from a competing program, disassembling it and comparing it to the source they are buying. It just doesn't happen.chrisw wrote:What you would do is not relevent. You are not commercial. Commercial software has to be clean without danger of challenge. A company with shareholders will be hit by a double whammy if it asserts it owns or licences assets which it knows are of dubious legality. Whammy one - get sued by the real owner. Whammy two - get sued by the shareholders forbob wrote:If you believe that, fine. Personally, I don't rewrite code that is working, that is functional, and that does exactly what is needed. I rewrite the parts that are being improved. That is a basic tenet of every software engineering book on the planet, AKA "code reuse". It is _the_ reason languages like C++ were developed, to make reuse even easier.chrisw wrote:_If_ R1 beta contained GPL code then the probability that R3, a commercial release through a publisher, contains any of that code is extremely low, not high. The simplistic assumption via the naming does not apply.bob wrote:Did you read what I wrote? I wrote (and rewrote) "blitz" 7 times. _major_ changes. But big chunks of code were reused. Who needs a new opening book format, new PGN parser, new move input/output code, etc? I then rewrote Cray Blitz three times. Major changes. 20,000 lines of assembly language added. over a Period of several years. Yet each had at least 60% of code re-used. I have rewritten Crafty 3-4 times as it was time to clean up and re-do. And again, 50+ % (if not more) of the code was kept. The most recent rewrite where I eliminated all duplicate code was a big change, but tons of reuse.chrisw wrote:You say "_if_" above, and then go on to "probable connection".bob wrote:It is not much of a stretch to believe that R2 has much of the same source as R1. And that R3 has much of the same source as R2. So _if_ R1 is a partial or complete copy of fruit, R1 is automatically GPL code. And unless R2 was 100% rewritten, R2 would also be GPL. Ditto for R3.Enir wrote:Some programmers found code similarities between Strelka and Fruit; Vasik said that Strelka was R1 beta; Fabien told Corbit that he didn’t mind about Strelka. When was all that?chrisw wrote:It's a bit convoluted, but the argument of the "Rybka 1.0 beta might be a clone camp" goes like this ...Enir wrote:Hi Chris,
[snip]
Where did Fabien say it? This is of key importance in the whole issue.chrisw wrote:Fabien says he has no problem.
Enrique
Strelka is a reproduction of Rybka 1.0 beta.
Strelka resembles Fruit at a programming level
Therefore Rybka 1.0 resembles Fruit.
The "Rybka 1.0 beta protection society" argues:
Fabian has no worries with Strelka.
If other side wants to argue Strelka = Fruit
then Fabian by extension also has no problems with Rybka.
Bob wrote:
Didn't Vas clearly post "Strelka is a reproduction of Rybka 1.0 and I am claiming it as my own code now"??? I saw that specific comment (probably not those exact words, but semantically _identical_ posted by him when the Strelka / clone issue first broke.
Dan Corbit wrote:
This is what Fabian said about Strelka:
"No worries as far as I am concerned.
Ideas are not a legal property.
The code was rewritten so it's OK with me.
Tournament organisers might think differently.
I cannot say a definite yes or no ..."
I’m asking because I would like to know why these accusations take place now and not in the old times of Rybka 1 beta. And whether they are related to other accusations here last week about Rybka giving R2 for free and not showing the true node count. I’m not saying it’s a campaign, but it might very well look like it, with these three simultaneous accusations against Rybka just before China 2008 and immediately after the huge lead of Rybka 3.
By the way, when Vasik said that Strelka was R1 beta, was he referring to the whole program or to parts of it? If to parts of it, the whole accusing syllogism (part of Str = Fr, part of Ry = Str, therefore Ry = Fr) is false, because Strelka could have copied parts of Rybka code different than Fruit. Possible? I'm asking you as programmer. I'm lay.
As for your "Tournament organizers might think differently", Rybka 3.x will play in China, not R1 beta, so I don’t see on which grounds the organizers could object.
Enrique
So we end up with a direct connection from fruit -> strelka -> rybka 1, with the probable connection of Rybka 1 -> Rybka 2 -> Rybka 3.
I have not been involved in discovering this, I have followed the discussions, and have stated several times that based on the evidence that has been presented, things appear to be a bit off-color. Since the Rybka group are offering no arguments or evidence to the contrary, it would be hard to draw any other conclusion.
Methinks you should be extremely cautious before alleging a connection between R1->R2->R3 and then asserting a problem with R1.
Do you have evidence that R3 has R1 beta code contained within? If not, the comments above are exceptionally dangerous.
I wrote above "It is not much of a stretch to believe that most of R1 source was retained and used in R2, and that most of R2 would be reused in creating R3." I see _zero_ danger there and if someone would want to challenge me on it, suits me. The university has a team of lawyers to handle such nonsense. I did not say "absolutely, R3 contains part of R1". I said "it most likely does" and I'd stake my software engineering reputation on such a statement any day of the week... The probability is _HIGH_ that if R1 contains GPL code, R2 and R3 also do. But even if not, if R1 contains GPL code, that could be a significant legal issue for someone if the FSF folks get interested.
not informing them, not putting aside money in the accounts for the risk, and positing untrue asset value statements.
No commercial company with half a brain will publish software claiming total rights over it if not true. That's the overpowering evidence one that R3 is clean. Chessbase won't licence it unless absolutely certain it's clean. That's overpowering evidence two. Say anything else and you play with fire. imo.
I will also point out that some disassembled Rybka 1 (not beta) code has been posted, so this beta to release rewrite for version 1 is not based on reality.
Naive yourself. Who "owns" the copyright issues if hypothetically there were any would not be up to a contract or licence between you and the other contracting party (the publisher).
Anyone who decided their rights were being infringed would choose themselves who to sue, you or the other party to the contract, both or either. The best the other party could get from you would be an indemnification for their costs. And, if you had insufficients funds, such an indemnification would be useless anyway.
Those indemnifications are in licences broadly to demonstrate the contracting parties have taken the appropriate safeguards.
People behave and perform for contract because the clauses are to the effect this:
if you warrant something that is not true, you can then place your right arm on the table to be chopped off.
the idea being we don't offer our right arm as hostage if there's any chance it gets hacked off. hence we do what we say we're going to do in the contract, including being truthful when warranting ownership of rights.
That's the assurance that R3 is squeaky clean.