4 ms·
Could some kind of micropayment scheme help these projects make some money? For web servers you might charge per request served. For text editors you might cha
by superquest 10y ago
Could some kind of micropayment scheme help these projects make some money?
For web servers you might charge per request served. For text editors you might charge per unit time the editor is being used.
It'd be interesting if the maintainer could define an acceptable salary, and all "consumers" would just split the bill by proportion of their usage according to the kind of metrics mentioned above.
I would gladly pay such a bill if nearly all the money went straight to the developer, I could cap my contributions, and it was extremely easy to opt-in. Ideally the package manager would read some dotfile or ask me! The problem with projects like Bountysource is that people will never track down all the OSS projects they depend on and figure what would be a reasonable donation to give them. Too much agency is required of the user to achieve meaningful adoption.
Has anything like this been attempted?
Edit: clarifications ...
- whit537 10y ago> people will never track down all the OSS projects they depend on and figure what would be a reasonable donation to give them. Too much agency is required of the user to achieve meaningful adoption. Yes! This gets at the B2B question mentioned elsewhere on this thread. At Gratipay, we're working on integrating package managers to help with aggregation. We've already loaded up all npm packages with stubbed out pages like: https://gratipay.com/on/npm/express/ https://gratipay.com/on/npm/express/ Now we're working on adding the ability for package maintainers to easily claim their packages on Gratipay, and then companies can upload a package.json or something and give a chunk of money to their entire dependency chain. Happening here: https://github.com/gratipay/gratipay.com/pull/4305 https://github.com/gratipay/gratipay.com/pull/4305