Juan Vuletich wrote:
> How do you see Projects trying to maintain their own changes? I removed 
> Projects from Cuis because I don't like them trying to look as if they 
> could isolate changes when they can't. Perhaps some Monticello magic 
> here? Or simply to make Project _not_ to carry any code with them? Then, 
> some indication of what they require from the host image would be in 
> order...

I'm not sure. My gut feeling is that the entire notion of "changes" is 
depending on context. What changes mean in Etoys (scripts represented by 
S-expressions) is different from what changes mean in Smalltalk hacking 
and is different what changes could mean in Wonderland scripting.  As 
such I'd say that the notion of changes is something that one needs to 
deal with at a different level.

 From a practical perspective however I'd say that having one change set 
per project (and the ability to switch between them when changing 
projects) is quite handy. But if someone were to say let's nuke change 
sets in projects and require people to switch them manually in the 
change sorter, I would probably be fine with that, too.

Cheers,
   - Andreas