On Mon, 20 Dec 2004 14:05:57 -0500, Mark Guzdial <guzdial at cc.gatech.edu> wrote:

> But it's hard to grok Squeak these days.  There are lots of "code
> words" out there that are hard to decipher.

I think that's partly due to the decentralized nature of development
these days - nobody is in a position to assert that their vision of
something will be the standard one for all Squeak users, so they pick
names like "Monticello" (which is a version control system) rather
than just calling it "Version Control System".  Maybe we should adopt
a policy of generically renaming things once they become widely
used...

>  It took me a long time to
> figure out that "Mantis" has something to do with bug-reporting (and
> I'm still not sure what yet), and I'm still not clear on the
> relationship between "Monticello" and "SqueakMap."
>  (And now there's
> something called "SqueakPeople" that I have no clue about.)

For people that are familiar with the wider open source world, I find
these metaphors are sometimes helpful:

- Monticello plays the role that CVS does in most open source
projects; it's a version control system, aimed at making team
development of Squeak source code easier.
- SqueakSource is like sourceforge.net; it provides a place to host
collaborative development of projects.  Just as sourceforge.net
provides a CVS repository (so that you don't have to know how to host
your own), SqueakSource provides a Monticello repository.
- SqueakMap is like freshmeat.net; it provides a central location to
announce and to find Squeak packages.  Unlike Monticello and
SqueakSource, which are meant to help development, SqueakMap is for
final, released code.
- SqueakPeople is like slashdot (or more directly, but more obscurely,
like advogato.org); it's a place to discuss Squeak by posting articles
or diary entries, and a sort of algorithmic "who's who" (read up on
its ranking system to see what I mean).

Cheers,
Avi