To be clear: I am not arguing against rebasing the trunk on Cuis. I'm just not clear on what we gain by doing so, rather than by continuing to make packages unloadable, and by settling on a mechanism to reload them on demand, while keeping reasonable safeguards in place to make sure they'll work with a particular release. 

Andreas, Juan? Care to comment?

I appreciate that Cuis really does keep with the spirit of ST-80, whereas Squeak has seen some design drift in it's use as a research environment. 

My biggest concern is: has Cuis seen the same scrutiny that went into Squeak 4.0 with regard to licensing concerns? Have we run this idea past the SFC?

One thing that I do think might be interesting: what might we learn by merging with a fork? I'd hope we might learn a lot about merging forks in. Could come in handy when it comes time to (hopefully) rebase Etoys on Squeak; possibly other things. 

In any event, you will have my support to the extent that I'm able to be of service.