GNU CLISP does not get any resources, human or otherwise, from the GNU project. If Sam stops working on CLISP, he's not going to start working on GNU Emacs or gdb instead.
>But my general impression is that GNU is already critically understaffed anyway, so it might actually do them some good, and avoid having dead-weight like this steal resources from their remaining projects.
GNU is not an organization that employs or assigns people to work on specific projects (with very few exceptions).
This is how you smell a future dead project.
If only one person has done anything significantly, with nobody around to "pick up the chops" and learn the code-base, chances of anyone willing to pick up 147MB of sources and claiming responsibility for it is pretty slim.
On the flip side, we do have a gazillion free Common Lisp implementations around. If this one falls dead, will the Common Lisp community have lost anything of significance?
From what I can tell, the only ones "losing" something here would be GNU losing a thing they can claim being made by them, a feather from their highly featured hat.
But my general impression is that GNU is already critically understaffed anyway, so it might actually do them some good, and avoid having dead-weight like this steal resources from their remaining projects.
Opinions?