Open GoogleCodeExporter opened 9 years ago
Original comment by wonchun
on 25 Aug 2011 at 7:34
This is barely started. It would be nice to start using Makefiles and such.
Original comment by wonchun
on 5 Sep 2011 at 9:44
How do you want people to submit patches? Have you considered switching to
github or bitbucket? Google Code's lack of pull requests is frustrating.
Original comment by jterr...@gmail.com
on 5 Dec 2011 at 7:46
For now, easiest way is to update/create an issue with a patchset. I'll also
look into adding contributers and setting up code review, tagged builds etc.
I'll look into github, but considering that I work in the same building as the
engineers who run Google Code, I prefer continuing to use it. I would
definitely be open to switching to git (or mercurial?) since that seems to be
what the cool kids are using now. Note that I don't necessarily want there to
be crazy forking going on because of patent issues.
At the high level, you are right that this issue needs some TLC. Like, I should
start a mailing list, at the very least, and reorganize some code so it looks
less of a mess. Recently, all my time that I have for this project has been
occupied elsewhere, but I have more time for it now.
Original comment by wonchun
on 5 Dec 2011 at 8:29
Original issue reported on code.google.com by
wonchun
on 25 Aug 2011 at 7:33