Django Audit

This audit demonstrates mainly:

  • Open Source does not mean "a right to participate"
  • Change Resistance within Open Source Projects
  • Methods to apply a Rework without any support from the project/community

Summary

  • The product does not keep what the website promises
    • simplicity, automations, ...
  • The project has several deficits
    • Missing contribution processes
    • Access rights are removed without public vote / notice
  • The code is difficult to maintain
  • Non-Standard Terminology makes teach-in difficult

Subsystems

  • Persistency (ORM for Sqlite3, Postgre, MySQL)
  • Security (Authentication / User Management)
  • Web Management Application (Administration, Data-Management)
  • Templating (other Template Systems can be used)
  • URL Mapping
  • Caching
  • Internationalization

Website

Weaknesses

  • Main page is overloaded with information
  • Tutorials go directly into full knowledge
    • e.g. cmd-line interface prior to GUI Admin
  • Documentation Comments unprocessed since long time
  • Does not invite to contribute to the Project

Strengths

  • Design & Impression
  • Integration of Trac

Product

Weaknesses

  • Simplicity is not prioritized
  • Framework is more complex than necessary
  • Weak Documentation

Project

  • Lead: Adrian Holovaty
  • Team: Overview of Active Team not available (not rated as relevant, see Mailinglist Topic below)
  • Authors: Authors Overview

Weaknesses

  • Missing strict separation of Project Resources
  • Missing Strict Contribution Processes (long delays to contribution)
  • Missing liberality and openness

Code Base

Weaknesses

  • Low Object Orientation (e.g. management.py
  • Low modularization
  • Subsystems not strictly decoupled

Community

Own Threads

Other Threads

Django User

Leadership