2014 will soon be history and many out there will ...

2014 will soon be history and many out there will replace the copyright year "2014" with a "2015" in the project's base.html. Then commit and push this small change to the repository, deploy, restart the server, .. and so on. Five to ten minutes per project later is again all in good order - at least for another year, for the year 2015 to be exact. To save us this work, we implemented years ago a super small and simple reusable app: https://github.com/arteria/django-copyright Outdated copyright information are unprofessional. That is the reason why we use this app in almost each and every project we realise.