Development Roadmap for Django Music Publisher

Django Music Publisher has a narrow focus. It covers the needs of most writers who are also original publishers of their own musical works, regardless if they are the only author or not. It also covers the needs of some original publishers who publish multiple writers. And there is no plan to change the focus.

Some things never change

Original Publisher(s)

Django Music Publisher supports just one publisher per installation. No data on other publishers (publishers for non-controlled writers) can be entered. This will not change.

Administration, Co-Publishing and Sub-Publishing

Django Music Publisher only supports one original publisher per controlled writer and does not take data about administrators or sub-publishers, nor any territory-related data. None of it is on the roadmap for Django Music Publisher.

Co-publishing deals are still possible, though each publisher has to manage their own data. Consult the manual for details.

Writer and Publisher Shares

Staring with 2020, Django Music Publisher features a global setting for agreement shares.

The default is that controlled writers maintain 50% of performing rights, while the other 50% and 100% of mechanical and synchronization rights are transferred to the original publisher. This is how things are usually done in the US, UK, and many other countries.

However, some countries may have other customs and sometimes rules, e.g. in the Netherlands, only 1/3 of the shares are transferred to the publisher, and not just performance shares.

The only information entered through the app is the writers’ relative (“manuscript”) shares, all other share data is calculated based on that. This will not change.

And some things do change

2018 releases were primarily about data for CWR registrations, but also about setting up and documenting the development process, and simplifying deployment.

In 2019, internal data validation, CWR generation, and complete test coverage were added, as well as experimental CWR 3.0 support.

With the 2020 version, the deployment to the free Heroku tier can be performed with no technical skills. Installing upgrades and security/bug fixes requires technical skills. There is currently no way to make this process simpler.

We provide that as affordable service, together with user support.