I just read that this is possible, if the functions are declared as classmethods, not staticmethods.

Big question: is this design (that I've done) "pythonic"?  Everything is going to be a class method.  Makes sense to me, but perhaps breaks python conventions?

Two other possible designs:
* create a new file: securesync/sync.py, where all these methods are global and there is a file-level global syncing_models list.
* Create a regular class SyncingModels, and instantiate it at the global level.  Would allow flexibility, but also more responsibility (either each class with syncing would have to own it's own instance and remember to call it to sync, OR ... I don't know).

Even in the case where we keep this as a static class, moving into a sync.py file might be best.  It's a little weird to have a globally used class that's not a django model defined in models.py to me.

Comments / suggestions welcome.