Access to contact groups for the purpose of broadcasting SMS messages I think is a great idea.

I've tended to shy away from contact management (editing contacts but group management would also fit under that) as that would best be implemented elsewhere (libfolks? qtcontacts? contact sync? other contact apis?).

Managing of contact groups specifically with GV is something more applicable to DC and having that without contact management would be odd so it could justify support for it. I'm a bit mixed about how much of all of GV's settings to put into DC though. I at least rarely use them so keeping GV simple at the cost of going to the website seems acceptable. Thoughts? Use cases?

Originally everything was based off of imitating the gv mobile page. Eventually I added support for things on Chad Smith's page. Also looking at the official Chrome extensions source is helpful. I also saw a thing or two on misc other google voice apis.

I find I rarely touch the GV APIs much these days, most of the work is on UI features on top.

I'd love assistance and as a fulltime C++ developer, Python has been my preferred dynamic language to learn. You can also consider helping uvatbc out with qgvdial. I personally am not much of a fan of the split development. The way I think of the difference in DC and qgvdial (hopefully not offending uvatbc) is that DC is an end-user app while qgvdial is a tech demo with every feature possible added but work needed on making it usable.

I'd recommend forking the project and playing with it
https://github.com/epage/DialCentral

Since you talked about the APIs:

Session management, threading, caching, etc layer:
https://github.com/epage/DialCentral...src/session.py
GV API to DC Adapter (makes working with TOR easier)
https://github.com/epage/DialCentral...oice/gvoice.py
GV API
https://github.com/epage/DialCentral...oice/gvoice.py