One thing I noticed when comparing libGDX to XNA was that the basic game framework that you can extend from in XNA has 2 "tick" methods in it's main class, update() and render() (or something to that effect). Also the Java library "slick2D" follows this convention. This makes it simple to seperate out rendering code from logic updating code.
LibGDX on the other hand only provides a render() method which confused me a little. Should my render() method be handling logic updates? Should it call another method that does, but check time deltas on each loop to decide whether it should run, or should game logic happen in it's own thread?
it definitely does build, otherwise jenkins would scream at me all the time :)
We have our reasons to use SVN for the time being, externals being one of them (git modules don't work for our setup), tooling support being another one. We are eager to give people commit rights, provided they follow a small set of rules.
This does not necessarily help you with your dev process of having lots of local changes that you throw away. But that's something git-svn should be able to solve.
Ping me via e-mail at contact at badlogicgames dot com.
SVN is functional, simple, and it works.
If you're doing OSS contribution right, you'll spend far more time talking and coding than you'll spend poking at SCM, and you won't be maintaining a large fork or poor hacks that upstream doesn't want to merge.
Discuss early, merge often.
The bigger issue right now, as far as libgdx on Ouya would be, is that libgdx doesn't support controllers yet. But badlogic (who also replied to you--he's the main dev behind libgdx) seems to have some ideas on that one. I wanted to start in on writing a gamepad extension to their input system last night, but pulling down a clone with git-svn took most of an hour and I ran out of time. =)