Nothing, it's not a service. The code is already out there along with the documentation and language spec. The worst they can do is:
1. Cancel their future contributions.
2. Create a closed source fork (is this feasible with the license if they don't control what others have contributed?)
In the worst case, if there aren't enough go enthusiasts it goes the way of other niche languages. Since the supporters seem to be active enough, I doubt that'll happen.
Cocos2d (at least when I was using it) engendered some really bad anti-patterns in regards to memory management and architecture. MBTileParser doesn't just offer a way to show graphics onscreen, but it considers the MVC architecture in a way that cocos2d doesn't. (When I started, cocos2d was somewhere between 0.9 and 1.1. The state of the engine has very likely improved since, but that's why I wrote this.) Cocos2d didn't even support ARC back then.
The performance of MBTileParser is fantastic. I've profiled map loading to take under 300 milliseconds. I wouldn't necessarily use this for an action game, but for RPGs, this is more than sufficient.
With a UIKit engine, you don't have to deal with OpenGL and UIKit fighting for performance.