Comment Everything seems like a hammer to me (Score 1) 27
Full disclosure: I am a Drupal CMS web developer, and I know nothing about Python/Django.
I explored the demo and what I saw, to me, looked like in 2015 it would be most efficient to re-write the system using the Drupal CMS going forward, using the current system as a Functional Requirements specification to meet or better. The development bang-for-buck goes with Drupal for managing the content required, while gaining much from using Drupal, while lowering development costs. Since the system was closed-source to begin-with, in doing as I have suggested, I see many other Drupal developers being able to join and contribute towards on-going and future development. The barrier to entry for those developers to be able to contribute seems lower than at present, so far as I can tell from these cheap seats in the Slashdots.
Drupal offers what is known as Drupal Distributions, which are different installed flavors of Drupal that have been pre-configured. For example OpenAtrium is an intranet-in-a-box, doing calendaring and task management and tracking. You might release the next version as a Distribution of Drupal, while joining the Drupal development community?
But that's just me and I might be wrong. Everything looks like a hammer to me, because what I see looks like totally normal stuff do-able and more efficient with the Drupal CMS/API, but development is inefficient as it stands now, from what I can tell.