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.
With the release of version 18.11, further development will depend mostly on sponsors. But let us first cover things that will not change. For two main reasons, because we already have that covered in other solutions and because by maintaining focus, one can ensure simplicity.
Some things never change
Django Music Publisher originally supported just one publisher per installation. This was extended for the US. A set of up to three publishers in different PROs in the US can be used, with one of them being the “main” one. 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.
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
These features have been identified as missing. They will be added if sponsors are secured. Some of these features we already have in other solutions, so they must be ported here, but in most cases, they require coding from scratch.
We are looking for sponsors for these features.