The whole point is to force the cloud providers to go through a contract negotiation for licensing rather than keep the door open for them. Nothing prevents the parent project from specially licensing to individual parties.
reply> which use a cloud managed DB solution (GCP CloudSQL PostgreSQL) it means something like this would never be available
replyThat's up to GCP then. I'm sure OP would be willing to license pgrust to them for an appropriate price.
What's the incentive for third parties to contribute, knowing just one guy stands to benefit if the project gets monetized in such a manner?
replyMost of the same incentives of typical OSS contribution? It's not like other OSS projects pay out any earnings made with the product evenly across contributors.
replyAlso, from the trajectory of the project it doesn't look like they are significantly deoendent on outside code contributions.
what exactly are your concern of using agpl db server? It doesn't force you to make rest of your system agpl.
reply>we would be happy to dual-license under a commercial license
reply