How can I find out who is responsible for Django's CSRF middleware?

Question

How can I find out who is responsible for Django's CSRF middleware so I could ask them questions?

I'm having so many CSRF failures for months on my Django site and it is costing me hours and hours of problems every few weeks. I want to contact the developers who worked on it to ask them one or two root questions about the problems I'm having.

I put up several other posts about the problems that never get satisfactory answers, but that do result in a few work arounds:
http://stackoverflow.com/questions/1650941/django-csrf-framework-cannot-be-disabled-and-is-breaking-my-site
http://stackoverflow.com/questions/1765723/django-csrf-framework-having-many-failures
http://stackoverflow.com/questions/1467425/tons-of-false-positives-from-djangos-csrf-middleware
http://stackoverflow.com/questions/2010432/for-djangos-csrf-failure-middleware-how-can-you-get-the-csrf-errors-to-report-w

Some other people are having the same types of frustrations: http://stackoverflow.com/questions/1785772/completely-disable-djangos-csrf-protection-in-svn-trunk

Answer 1

CSRF protection is being re-worked for Django 1.2. See the community wiki page CsrfProtection that discusses the current limitations and proposals for re-working. Personally I'm thinking about moving ahead and using Simon Willison's django-safeform project as a temporary solution until 1.2 is released.

Answer 2

I've said this before, but you should not be using trunk for production projects. Use the stable release, and you won't have any problems.