Okay, how do I start... Solus is a great project and I love working on/with/for it. I learned a lot about compiling and packaging and as such I want to give back by maintaining a few packages and fixing minor problems.
But I'm a bit tired of sitting in IRC to ask "PersonXYZ: Can you please commit this?" so maybe this is T2616 part 2.

Phabricator has limited abilities but as we keep growing there will be more and more patch submissions. Ideally you could name more maintainers that can commit themselves, but that needs a lot of trust (and knowledge to fix broken updates). I was thinking about some categories like "just a minor patch, please commit asap" (e.g. PHP 7.2.x), "big update, maybe with breaking changes, request for comments and tests" (e.g. PHP 7.1 -> PHP 7.2) and "initial inclusion, please check for mistakes". On the other hand this would add even more bureaucracy.

To make it a bit more concrete:

• D1582 is important for (mostly German) users to have a working VPN to their router. The SVN solution is dirty, I get that. Ikey wanted to check it out and upload it as a tarball himself, but it failed and wasn't touched since.
• D2983 is a small patch that was tested with two OpenVPN configs and worked fine. I asked a few times in IRC, but nobody reacted.
• Hotspots are on the Solus 4 tasklist, so I packaged D2878 and tried to start a discussion about what hotspot-integration should finally look like, but there was no response.
• PostgreSQL 10 has been out for a while, but upgrading databases from 9.6 to 10 needs old and new binaries. So what do we do? A postgresql-10 package? Where to discuss this? With who? If it's not important right now, then what is?

An alternative could be a current roadmap to see what's being worked on and what's important in the near future. Haskell stack and kernel upgrade? Okay, I won't bother you. Software xyz needs an update? I'll be happy to help. Software xyz is already maintained by Person xyz? Sorry, that wasn't noted anywhere and I just wanted to help.
Maybe it's a lack of coordination? We are not enough to have permanent maintainers for every package but are too many without fixed responsibilities, so some work is done twice or thrice. Maybe it's just me and everyone else is happy.

I'd be happy if @ikey, @JoshStrobl and others like @kyrios123 (or everyone else) would find some time to comment.