Or create a Jabber server that has rooms for class categories, and a
Jabber client that automatically enters for you all the rooms that
you're looking at, so that you see who else is working on the same
stuff, and can exchange comments/questions.

Make Squeak code into a space where you might meet people...

Daniel

Avi Bryant <avi at beta4.com> wrote:
> 
> On Wed, 25 Jun 2003, Jim Benson wrote:
> 
> > Another interesting concept is to link 'persistent' chat with Wikis, which
> > combines two ideas: the synchronous communication of the chat world
> > (augmented by making the chats persistent) and the asynchronous mode of the
> > Wiki. Creating a Squeak based server would facilitate a much tighter
> > coupling between the two, placing them both in the same 'space' as it were.
> 
> Yes, I've had this idea in the back of my head for a while.  I'd like to
> combine this with two things:
> - multiple feeds into the wiki: not just chat but also mailing lists,
> commit logs, issue tracking, etc
> - a simple markup system so that you can, during a chat, say something
> like "topic: foo", and have the rest of the chat logged to a particular
> wiki page.  Of course, this same markup would be recognized in any of the
> other feeds as well.  Ideally it would also have conventions for referring
> directly to certain revision numbers, bug numbers, etc (see CVSTrac for a
> nice example of this).
> 
> The problem with having all of this data streaming into a wiki is that you
> then need to spend a lot of time editing it - you want a "refactoring wiki
> browser", which is an interesting problem in itself... ;)
> 
> </ramble>
> 
> Avi