add more maintainers

[paroj]

the current xz utils situation inspired me to pressure you to add additional maintainers to this repo, so things get moving again. Lets say @flyingOwl

[flyingOwl]

I mean, jokes aside... This project really needs a little push. I know a few people who use DSub regularly and they all complain about minor inconveniences. Those things could have already been fixed as some of them have pending pull requests or are part of forks. I use DSub because it handles music and the connection to my setup the way I want. And with some changes and bug fixes, it would be perfect and probably more attractive to others. Having a manually build fork that is a dozen commits ahead just feels wrong.

[paroj]

maybe we can start by unifying our own forks into one with the main goal of collecting bugfixes and keeping the code buildable with a recent android studio so people can easily contribute.
I have integrated your pull requests into my fork in #1126 and added some more fixes over the holidays. We could start with that.
Additionally I would make ServerProxy an inline copy instead of a submodule to simplify updating, while keeping both repos in sync. I dont think it is used outside of DSub anyway..

I would call the fork DSub2000 to clearly mark it as a fork and hope that we can merge the changes back here one day. That would be the best outcome so the changes arrive as an update to existing users at some point.

If you agree, I can go ahead and create such a repo and add you as a maintainer.

[flyingOwl]

That would be awesome. Let's do this!

I also have a few more features in my fork and my local copy (still uncommited). But it will probably take a week or two until I can get my hands on the code again.

[norohind]

Greetings. I'm also interested in contributing small fixes for problems that annoy me daily.
Paroj, could you please open issues section in your fork so we can discuss fork related stuff there?

[paroj]

done. this is the fork for reference: https://github.com/paroj/DSub2000

[gravelld]

It might also be time to support the new Open Subsonic spec... https://github.com/opensubsonic/open-subsonic-api