Yeah, I saw you forked the repo so I added you to the organization. There's a bug in GitHub right now where you can conceal membership but the button to publicize membership is missing, so you'll only have your word and mine to go on that you're in.
It's still community. Thumper has been refactoring the build process and ensuring OSX supprt, I've been refactoring the entire codebase and getting travis-ci integration, and others have been making tweaks and additions along the way. To take part all you have to do is fork the official repo or someone else's fork (such as mine), make changes, and send a pull request to whichever repo you forked.
As of writing this post these people need to publicize their membership:
If you want to be a member, just post a link to your GitHub public profile.
On a side note, I've got travis-ci working in my fork: https://travis-ci.org/LB--/ChessPlusPlus
Unfortunately the compiler and standard libraries are outdated (and libc++ is missing the include headers), so there will be compilation errors due to incomplete C++11 support.
Hmm I thought this project wasn't going to be using Boost? Appears as if the master branch uses Boost. If the plan is to use Boost, that's fine I can grab it. I just thought we were trying to keep the dependencies minimal.
Hi all, I went away for a while to learn some ruby on rails ( hardcore c/c++ guys get along with RoR, right? :) ).
I know I've been out of touch, but I've got to get something off my head. I don't say this to be mean, and my intentions are for the best. lb-refactor has been around way too long. At first it was just for getting indentation in sync, but odd things have crept in ( ie, a failing travis build when there is no test suite ).
All I'm saying is that it is a very hard project to pick up.
I'm on the same page as naraku and LowestOne been debating for awhile if I want to contribute a bit to the project but it's been quite hard to determine the flow of the program without having to do some serious studying of the code.