Maybe we're using two different meanings for the word 'repository'.
I'm using it in a version control system sense: a place where you can
look at different versions of the source files and create patches,
test local changes, etc.
When you create a project on codeplex/github/google code/etc., you
generally get a source code repository configured for a version
control system like subversion, mercurial, git, etc.
Setting up a project on a project hosting site isn't as important as
setting up version control so that you can i) isolate your changes,
ii) experiment with changes that you might want to undo should they
not work out, and iii) create patches that you can submit to the KLH10
maintainers.
With mercurial, its easy to create a local repository and share it
with someone (i.e. me) without going to the trouble of creating a
project on a hosting site like codeplex.
I honestly don't understand why the SIMH folks don't have a publicly
accessible source code repository and only have tarballs. It makes
contributing source code changes harder than it should be.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>