Now in practice, software is never a done deal. You have bugs. Platforms evolve and you need to adapt the software to it. New features might be added. This is all things you might want to see happen in the future. A subscription service could be a way to participate in the process indirectly. Obviously things need to be balanced as to not corrupt the projects in question.
There are already actors in the place like RedHat and Canonical or product companies like MongoDB but they are focused on their platforms and usually sell "support". As a customer I have a big and changing variety of open source project upon on I depend and negotiating contracts with each of those is time consuming. I would rather pay a fixed amount and have access to a body of experts and direct (part of) their work on projects they own or not. If I scale my subscription up I get more throughput.
A lot of details are conveniently left open to keep the narrative simple and idealistic :)
In my mind anyway, the idea is something like https://railslts.com/ but for potentially every other gem in your gemfile. We would provide security patches, bugfixes, features, documentation, training, version upgrade scripts/documentation and so on to subscribers.
I really like the accumulated credit for features, maybe a system of like: request feature, we put a "credit" value on the complexity of the feature, then companies/people can pledge credits/money for it would work?
How would you actually implement things though? After all, you're essentially trying to sell "support contracts" for open source projects via the platform. You could implement these by a) "hiring" the project owner to work on specific bugs/features or b) hiring freelancers to fix requested bugs.
Furthermore, how would you ...
* determine the value of bugs/features? * react to a project owner abandoning a project? * handle multiple upstream developers?