I promised to loop back re the issues with pull requests not being merged and the future of the database.com
I met with folks from across the company (Salesforce and Heroku). One of the primary reasons that we created the gem in the first place was to stop the fragmentation of approaches to access the salesforce APIs via Ruby. Most of us have been active and passionate in this space for a long time now, and fragmentation is never a good thing.
It looks like we are headed in that direction again with new projects like Eric awesome work with Restforce.
I proposed, and got support for, forming a core committee responsible for owning the ruby 'project'. The discussion was a committee formed by a chair (I'm proposing the dir of open source programs here at Salesforce), a salesforce R&D rep, a heroku R&D rep, and the rest made up of committee members.
Does this sound like a good plan? It would effectively mean, this group owns the code and repo, and manages pull requests, maintenance etc with a direct line to Salesforce Heroku R&D. We would also look at trying to bring this committee together on a annual/bi-annual basis to keep the project moving forward.
If this sounds good, I would suggest the first decision needs to be use the existing gem (with pull requests merged) or use restforce as the basic going forward.
Anyway....hope this helps. Any other suggestions are definitely appreciated!