As Craig said, we (SqF Board) are going to discuss various approaches with Dan Ravicher July 5th. We'll have a more informed idea of what is possible after that conversation, I hope. However, at the moment I think there are two realistic approaches:
- Take Squeak 1.1 and declare that the new main line of development;
- Do a license check on the Spoon code and declare that the new main
line of development. In both cases, we'd start with a "deficient" Squeak and work upwards. The third option, sort out the mess that's 3.9 (licensing-wise), seems to be not very viable. It's a lot of work to start with, and the outcomes are unsure.
You don't expect that's possible to take bootstrapped 3.9 kernel image (http://www.squeaksource.com/KernelImage.html) and make it clean from the licensing perspective? I don't think that it's more complicated than Spoon checking.
-- Pavel