stéphane ducasse <ducasse at iam.unibe.ch>  wrote...
>I have the impression dan that you should invent a term for these new modules because module is connoted
>This is why we invented classbox. So islands or safe could be a good candidate.

Yes, you are right.  However during this early phase, I *want* it to be ambiguous and overlap with all the other connotations.  Is this a package mechanism or a security mechanism?  Is it an interface to imageSegments, or a name space solution?  Yes!  I want us to be thinking of all these things because I believe there is a place where they all come together.

When we have finished compiling the little summaries of these related areas, *then* we come to discuss what substrate would give us the most leverage for all these areas.  Then we can decide what is the layer for packages, and let the package folks concentrate on that.  Then we can decide what is needed for security in the VM and let VM people focus on that.  Then we can decide what is the interface to ImageSegments, and let someone work on that.  And the kernel design that remains at the center?  When we see what that is, then we can give it a good name.

But for now, I want us all to be thinking that this is *everything* anyone ever thought of calling a module because, when we are done, I want it to fit well with every aspect of modularity in Squeak.

	- Dan