Right, that's definitely not good. I'd like us to be able to gather all of the work everyone's done so far as well as ongoing projects in repositories there. If you'd like to be able to create a repository within our github organization or be able to modify an existing repository within, let me know and I'll add that access. Once we're a bit more organized, I or someone else can create the repositories for the "official" parts of the project that are intended to lead to production versions.
For now, I have three repositories that I think of as work areas: CoreDataProcessing, which so far just has the Python code I wrote to parse .csv and .wpt files last week, and MapGeneration and Web, where I propose we put work toward, well, map generation, and web-facing parts of the project (maybe a new Highway Browser).
But for now, drop me a note about what level of access you want to have within the organization and I'll set it up. I want to make sure that at least two or three people can do pretty much everything so we don't end up back in a bad situation. I'll add people to teams and give teams appropriate levels of access to repositories (and would like to make at least one person, probably two, also an "owner").