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
Django Music Publisher originally supported 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 on 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.
As the result of described limitations, specifically, no territory-related data (the only territory is World), only a single performing rights affiliation is possible. Furthermore, due to the Writer and publisher shares limitation, mechanical and sync affiliations for writers are pointless, so they will not be included.
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.
Since 19.1 release, we have internal data validation, CWR generation, and complete test coverage.
In 19.7, data structure was significantly extended and support for CWR 3.0 was added.