242 karma · joined August 31, 2011
We use Stripe to process credit card payments as well as to pay out funds to projects that claim their funds. US based recipients who receive above a certain amount of money will be required to give the required information for 1099 income.
1. https://twitter.com/dudley, https://www.linkedin.com/in/dudleycarr, https://www.linkedin.com/in/wescarr
Anyone with admin access to a repository can register to be paid by StackAid and the total allocation for a project will be split amongst them equally. We plan to allow adjusting the percentages each maintainer receives in the near future.
- People don't want to give money to Stripe, Meta, etc since their projects are already well funded by corporations. We agree! Right now, those projects can just not claim their funds which would then be reallocated, or they can pass their funds on to their dependencies instead. We are exploring other ways to allow you to exempt certain organizations/repositories from being funded.
- People will try and game the system. They can try but they largely will not succeed because ultimately many developers will still need to be convinced to use and depend on their projects. How funds are allocated and what dependencies an open source project has is public knowledge and the community will rightly punish bad actors.
Thanks for all the responses and feedback.
You can also use our GitHub action to publish a stackaid.json file with your dependencies to a new repo just for the purpose of giving us access. This was your repos/source say private to us, but your dependencies can still be funded. It's a bit more effort on your part but hopefully addresses the concern.
Commercial projects can either not claim their funds (which will be reallocated), or elect to pass their funds through to their dependencies.
You also always have the option to explicitly list your dependencies.
- We built a simulation[1] of the NPM ecosystem to see how funds would be allocated. Frivolous projects did not see any significant funding.
- As I mentioned in other comments, you would still need to get many developer to actually use your new packages as either direct or second-order dependencies. Note that 2nd order dependencies receive quite a bit less allocation than direct ones.
- You can always manually manage your dependencies if you see a project engaging in this behavior.
- You still have to get developers to use and depend on these new projects.
- Allocation happens on a per subscription basis, so to realistically take advantage of this scheme, you will need many developers to adopt your new projects.
- Subscribers who notice maintainers doing this will be incentivized to vote with their dollars and change their dependencies to projects that aren't engaging in this behavior.
But if you mean, can you commit a stackaid.json file in a private repository, yes absolutely. As long as the GitHub app is given access to that repo, we will discover it and fund dependencies specified in the stackaid.json file.
All the package.json file we discover in your repos are actually automatically merged together, de-duped, etc before funds are allocated. In the app you can manage which set of repos/files you want to be included.
1. https://github.com/marketplace/actions/stackaid-dependency-g...
1. https://github.com/marketplace/actions/stackaid-dependency-g...
They will also have the option to be pass-through organizations which means that funds allocated to them will instead go to their dependencies.
We are also exploring the idea of being able to declare a list of repos/organizations to exclude from being funded.