Mark,

I think Philippe means both e-mail for persistent store and jabber for the
so inclined available per their preference.

I look forward to the day when one subscribes to the development projects
one is interested in.

Say, everyone's (public code) SUnit tests' results are published in RSS.
When the developer gets green on the important SUnit tests, you get the
notice in your aggregator (and a copy of code if its not too big, otherwise
get a link to it).

Then, if you want to, you import the code to a safe copy of what you are
working on and run your SUnit tests on the integrated code and
programmatically post the errors in your own RSS feed. If the developer
really cares, they could subscribe to your results feed. The aggregator
helps mitigate interruptions and disruptions to programmer thought process.

This sort of closes the loop nicely and more tightly and programmatically
than public broadcasts alone. Seems a natural for the collaborative nature
of Croquet. Big code compatibility breakage lights-up the net like a
Christmas tree.

Beyond "incremental compiling" ... it's "incremental code integration", more
fine grained than any project or .cs file making the rounds. It's also
loosely coupled like the net itself. Unsubscribe anytime. This also lets the
developer know how popular their projects are. It also makes it easier to
share popular project development code subscription "sets" between "friends
of friends" automating it rather than just passing along a link to a site
homepage or a copy of outdated code..

This might even be a nice hosted service if open source folks care to post
minute slips of changed code that passes their Unit tests to the service.

Cheers,
Darius
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20060225/4722ac48/attachment.htm