More help is always welcome. If you’re interested, you can read the contributing guide. If you have any questions or issues, please feel free to post them to this list or ask in the #rapidsms IRC channel on Freenode. Bugs can be reported on Github.
At this time, we are currently continuing to support 1.6. For the next release, if possible, I'd like to drop Django 1.6 support, so we won't have to maintain 2 sets of migrations, one for South (1.6) and one for Django's new migration framework (1.7, 1.8, and all future versions). I think it's also time to get rid of extensible datamodels and the contrib.locations app (which could be moved to a separate repo if there was interest). Instead, we'd document more Django-ish ways to customize RapidSMS (as discussed inhttps://github.com/rapidsms/rapidsms/issues/393).
I'd welcome any feedback about the above thoughts. I'd also welcome any ideas re: tickets that need addressing, or features that are on people's wishlists.