Browsing around, I see many mentions of how it would be nice to update CocoaGlk, but how there isn’t a lot of developer time. I also see mentions of how it is buggy but I don’t see an actual bug list. I wonder if it would be worthwhile to put CocoaGlk up on github with an issue list so people could at least log some issues and submit some pull requests as the spirit moves them? At least then it wouldn’t feel like a herculean burden on a solitary person to download it and wrestle with it all at once.
Wish I knew C but my career ended up focused more on Java…
Sounds like code.google.com/p/cocoaglk/source/list isn’t current for some reason? If threads are diverging, sounds like all the better reason to put it up on github. It should be straightforward to at least put the subversion history into that and then let people bring it up to date with whatever enhancements they’ve already done. I could volunteer to move the svn history to git and create the repository, but I’d need someone other than me to also (or instead) be admin since I shouldn’t be trusted with accepting pull requests (since I have no C experience).
Yes, it should be cloned to github, if only because github is where people look for open-source projects. Whether anybody is going to take over accepting updates is another question. Don’t wait on that.