Hi,
In short: you can now download Castle Game Engine and PasDoc source code
from GitHub, from
https://github.com/castle-engine/castle-engine
https://github.com/michaliskambi/pasdoc
Some larger games/tools using Castle Game Engine have also their
separate repository, see
https://github.com/castle-engine/view3dscene
https://github.com/castle-engine/darkest-before-dawn
https://github.com/castle-engine/demo-models
and other repositories listed on https://github.com/castle-engine .
Clone us, fork us, submit pull requests, and have fun:)
Longer explanation:
- These repositories mirror (are synchronized on an hourly basis)
appropriate SVN repositories on SourceForge. The synchronization scripts
run on my private server ( http://michalis.ii.uni.wroc.pl/ ) using
sync2git (see my fork of it on https://github.com/michaliskambi/sync2git ).
- Castle Game Engine SVN repository is split into multiple GIT
repositories, because having a large GIT repository is not comfortable
(GIT "sparse checkouts" are not as comfortable as checking our a
subdirectory in SVN). Using "GitHub organization" for this was natural,
to group multiple CGE GIT repositories as one project.
- For now, we treat all these GIT repositories as read-only, and commit
through SVN. But this will change as soon as we see people contributing
through GitHub (pull requests and such)!
So fork and submit pull requests as you like --- I'm anxious to see
some activity on GitHub related to our engine:)
- One reason for doing this was to not depend so much on SourceForge
(seeing it's recent downtime of ~10 days for SVN).
Another reason was to just encourage more contributors. Many
developers (including me:) are accustomed to GIT (and GitHub) workflow
and like the ability to fork / submit pull requests. I was working on
the SourceForge<->GIT mirroring even before SF downtime:)
So, let's see how this works:)
Thanks for reading, and have fun!
Regards,
Michalis
|
