> This would mean, probably, these steps:
>
> - We adopt the reorganization changeset from iSqueak as the first
> packaging changeset to go into the 3.9 stream
> - We include Monticello and Impara's MonticelloConfigurations as base
> packages in 3.9
> - We set up an initial repository (probably based on SqueakSource) for
> the resulting Squeak packages, which anyone on this team can commit
> to, and start committing the results of any further partitioning work
> to it
> - We hack the repository as needed to support whatever kind of
> maintainership model we want for the Squeak packages.  Tweak lives in
> a fairly closed world, where it's reasonable for everyone to update to
> the latest version everyone has posted, but Squeak (probably) can't do
> that.  So instead of "upgrade all packages in a well-defined order to
> their latest version", we probably need "to their latest
> maintainer-approved version", and have a harvesting process that turns
> submitted versions to approved versions.  We may find that the
> "blessing" mechanism I developed for the UnstableSqueak project is a
> good step in this direction, but we should talk about it more.
>
> Thoughts?
>

I totally agree. Who start to do that?
I said to doug that we would really like to have that setup.

Stef