Autopay dependencies if your code makes revenue

[serapath]

Maybe this needs to be custom and decided from individual case to case, but maybe there could be some guidelines how to determine the amount of revenue that should be shared with a dependency project.

Next, if the dependency project has multiple collaborators, what would be the key to determine which fraction of a received payment is distributed to each of the collaborators?

[bhaugen]

In value equations when income crosses a project boundary, the distribution is up to the participants in the project.

In other words, give the payment to the project and let the collaborators deal with it. (Or at least that's one way to think about it.)

[serapath]

I try to think from the perspective of a service provider. If somebody adds this to their open source project, each project has:

• an address to receive money
• a certain amount of collaborators
• a certain amount of dependencies (other open source projects they rely on)

It's true, that each project - internally - needs to decide how to distribute revenue to it's internal helpers (=collaborators) and external helpers (=dependencies), but if best practices or some ideas how to do that cannot be provided, then maybe at least a standard on how to specify this once it has been decided by the project :-)

[bhaugen]

if best practices or some ideas how to do that cannot be provided,

Should be doable.

then maybe at least a standard on how to specify this once it has been decided by the project :-)

Not sure what you mean there. "How to specify" might be a good issue for the Value Flows project. If you are interested in helping, I'll raise the issue there and link to here. (If not, I might do it anyway...)

[serapath]

This "value flows thing" is way to buzzwordy and verbose for my taste. For me - language is a means to communicate information - so to use common business vocabulary is way easier then building an ivory tower of vocabulary that makes it easier to misunderstand each other.

I'd like to think in terms of accounting and balance sheets, because i feel that is more widespread vocabulary. Business Processes are now transactions on top of balance sheets.

Maybe there could be some kind of json file in each project, that contains the main address of the project you look at, all the keys of collaborators and the keys of dependencies (thus projects used by the one you currently look at). ...of course, each of those "dependency projects" would have such a json file itself.

Next to the addresses that you can send money/shares/ressources/whatever at, it would contain a "distribution key". ...so each payment or donation or whatever received by the process could automatically pushed to all the collaborators and dependency projects based on the "distribution key"