django: Fat models and skinny controllers?
It depends of what your application is about, but the beauty of Django is that it does not enforce you to put your logical code in your views or in your models, this is your call.
If you think that some logic is strongly related to your model then you can make a method of it. The rule (for me) is that your model should be agnostic about the environment (web-app, Crontab running a manage command, etc). 
My policy is to try to put the bare minimum in my models.
By the way, you don't plan to handle request and sessions in your models don't you ? that is a bad idea.
This is a general architecture question.  I read in many places that in an MVC framework, (1) models ought to be fat, and controllers ought to be skinny.  But I also read that (2) the details depend on the framework you're developing in.  So, what if you're developing in django?
My experience with django is that a lot of the logic ends up getting put into views and forms.  Not the "business logic," but the details of handling requests, sessions, etc.  In terms of lines of code, these details often outweigh the business logic of manipulating model objects.  Am I doing something wrong, or is this how django works?