So, if these commits were private and squashed together before 7.0 was published there would be no violation?
replyThe commits being public or not does not change the fact the developement was made as a derivative work of the original version.
replyThey would be concealing the violation.
replyConsider TCC relicensing. They identified the files touched by contributors that wanted to keep the GPL license and reimplemented them. No team A/team B clean room approach used. The same happened here, but at a different scale. All files now have a new author and this author is free to change the license of his work.
replyDid they eventually remove/replace all the LGPL code?
reply