Alright, here it is. I’ve chosen GitHub and set up a profile, an organization and a public Repository under the GPL 3.0 license. This is where FRONTIERS’ code is going to be made available for modders and enthusiasts.
Now what? Organizing this is… daunting.
First off, I won’t be uploading the entire project to GitHub because there are third-party libraries that I can’t redistribute (yet). Instead I’ll be uploading the pieces that I know for sure are free and clear. Over time I’ll add dependencies as I secure permission from the authors.
That means people won’t be able to compile something that, you know, runs. They won’t even be able to supply the missing dependencies from a third party because in most cases I’ve modified the middleware I’m using. They’ll just be able to look at pieces. Does this break some kind of GitHub code? Are repositories for projects expected to be complete? I dunno.
Then there’s the problem of how to incorporate other people’s changes back into the main project. (I’m assuming someone, somewhere may actually want to change something.)
Right now I’ve got a local project. I edit that, then commit my changes to a remote CVS repository. Given that setup, what to do if someone out there sees fit to commit a change to GitHub, and I see fit to incorporate that change into my local project? Is it even possible to mix and match two svn repositories at once? If not, what happens if I slip up and don’t commit my local changes to GitHub for a week and that person has now altered an outdated version of a class?
Alright. Well. I’ve created the repository. First step: complete.
Read more here: 11/16/2014 – GitHub: Now what?