In deference to @shentino, we should make it clear where to find 'old SkotoS' - I'm not removing stuff from the Git history, but we should document how to get it. I think this is a light, fun way to describe, document and expose that functionality.
He has a good point that some of the stuff I'm removing or changing has value, both historically and practically. And even where my changes are good, something is always lost.
So: let's leave stuff in the Git history, as we planned, but let's also document where and how to find it. And that way, as I make other large-scale changes (e.g. pulling the Shared system out into a new repo, removing older Bilbo-based ur-objects, separating The Gables game-specific code into the gables_game repo) the old stuff isn't lost.
It would be possible to copy this repo so there's a "historical SkotOS" repo sitting around. But once we have the Git tag that's easy, so I'll just do this for now.
In deference to @shentino, we should make it clear where to find 'old SkotoS' - I'm not removing stuff from the Git history, but we should document how to get it. I think this is a light, fun way to describe, document and expose that functionality.
He has a good point that some of the stuff I'm removing or changing has value, both historically and practically. And even where my changes are good, something is always lost.
So: let's leave stuff in the Git history, as we planned, but let's also document where and how to find it. And that way, as I make other large-scale changes (e.g. pulling the Shared system out into a new repo, removing older Bilbo-based ur-objects, separating The Gables game-specific code into the gables_game repo) the old stuff isn't lost.
It would be possible to copy this repo so there's a "historical SkotOS" repo sitting around. But once we have the Git tag that's easy, so I'll just do this for now.