3 ms·
> There is a floor, however: if the payment computation arrives at a trivial total for a package, we reassign the money to other packages. Not sure I like this
by Crosseye_Jack 8y ago
> There is a floor, however: if the payment computation arrives at a trivial total for a package, we reassign the money to other packages.
Not sure I like this. It’s not very clear for a start. I read it as they do a calculation on each subscribers code use, if they deem its “not worth it” they give the money to someone else, they didn’t say what that floor is or offer to “hold the money until it reaches a valid payout value”.
From what I read it as if your code was valued at $0.05 for a sub they will give that 5c to someone else but what if 1000 subs was using that code? Would the maintainer get that $50.
Also seems they are weighing it on the code side of the project not the actual code used. What if I’m importing Newtonsoft’s Json library but “only” using using the object serialization function The release zip for that is 6.something MB where I may feel that the websocket server/client I use which come in at 130KB~ provides me with “more value”. But based of the size of the two repos Newtonsoft would be getting much more of my sub than the websocket lib.
Edit: > Each maintainer will have to sign the lifter agreement.
What happens if they haven’t signed the agreement? (The link to the agreement 404’s) lets say a sub signs up thinking “great all my repo maintainers will get paid...”, you detect they are using Repo X that has not signed up to your service because they don’t know about it (yeah sending a email / issue on GH saying “Hey, we have money for you, just give us your bank details” won’t get the email immediately sent to spam :-p) What is happening to those funds? Are you letting the subs know their money is not being collected? What if I don’t want to agree to your terms (I dunno, don’t like your font choice or something) and I will never sign up, would the money I would be getting get split up to the other repos the subs are paying for? Do you tell them that Repo X isn’t getting a cut of their money? (Remember the sub may think Repo X is really worth the money.)
What about if they are using a Microsoft Library in their DotNet Core project but have a paid account with Visual Studio / Microsoft?
- undecisive 8y agoI'm glad I'm not the only person who found this surprising. Withholding payment until a threshold is reached would make some sense, though for some packages they might be waiting years. Another approach might be to reserve some kind of "bump" fund - a small percentage from all the other projects gets reserved, and when small packages get to half the threshold they can be "bumped" in the theory that 5 dollars to a big project is nothing, but to a tiny project might be game changing. Probing actual line-of-code usage stats would be impractical, I suppose. It's a difficult question, but an important one
- fastball 8y agoBecause a two-line package should not need money to maintain it. The payment is intended to make up for some of the time the developer of the dep expended, it's not supposed to be proportional to the utility other developers get out of it. That's what makes it still OSS and not commercial software.
- Crosseye_Jack 8y ago> Because a two-line package should not need money to maintain it. I didn't bring up "two line packages", the websocket package in question is more on the size of 20k of code lines. > The payment is intended to make up for some of the time the developer of the dep expended, it's not supposed to be proportional to the utility other developers get out of it. Repo size doesn't always mean time expended. > That's what makes it still OSS and not commercial software. OSS can still be commercial software. Code could be A/GPL and still offer commercial license's to remove restrictions. And as others have said in this thread its often the smaller / less well "known" packages that don't get much "love" when it comes to financial support.