It's easy - just select the desired access level, copy this link and send it via email, instant message, etc.Link: Just a link to your wiki. Post this anywhere and people can ask you for the invite key.
Namespaces TODO list.
Things to do next:
Make Kernel, Collections namespaces.
Be able to upload packages to a HTTP server.
Store files using easily readable filenames.
Include an index file to map package UUIDs to URLs.
Refactor source code management so that source code is stored in a PackageVersion.
Change file-out format to be better: include meta-info, include fault-tolerant loading, include loading source only so it can be fixed up first (cf: "Refactor source code management" above).
Make MethodProperties or method source store license meta-info.
Expose BitBlt, so that a Canvas can be implemented on it later?
Eventually:
REPLServer cannot handle MessageCaptures.
Allow Namespaces to store things other than classes (i.e. update stateOn: and stateFrom:).
Lifecycle stuff:
Services (domains?) should react to OS-level stuff in an OS-independent manner. E.g. startUp, shutDown (when the image is shutdown, killed by the OS, etc).
Design the concept of a service, maybe modelled after KomServices.
Logging system built in. Also able, somehow, to log VM-level events such as GC info.