One idea covering both
The trunk , 5.2 and beyond is the master
Each person start forking and have his own .image
The changes each person have was saved somewhere
And the number is

Edgar 1.cs
David 1.cs
Nicolas 1.cs
This way,  each squeaker become his ruler
And any could have changes of others.
Could have some stats of owner.nnnn.cs
And kind of competition of popular ones.


> On 23 Jul 2018, at 09:51, David T. Lewis <lewis at mail.msen.com> wrote:
> 
> I would be happy just to see UpdateStreamDownloader get a good class comment
> that explains what it is, and that clarifies the difference between our current
> Montecello based update stream and the older change set based stream.
> 
> An update stream is not a version control system. The update stream that we
> use today happens to be built on top of Montecello, but if we ever wanted
> to decouple the update stream from the version control system (for example,
> if someone wanted to use git for version control), then it might be important
> to have a simple change set based mechanism that works independent of the
> version control systems.
> 
> I can also imagine a scenario in which we would want to provide some kind
> of "mirror" of Squeak trunk on GitHub in order to make the system more visible
> and accessible to the world at large. In that case, it might be helpful to
> have a change set based update stream that follows the real one in Montecello.
> 
> Dave 
> 
> 
> We do not currently use the UpdateStreamDownloader mechanism, but I think it
> is import

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180723/01becc59/attachment.html>