> Instead of asking to stop, they should do just what they suggest, without further ado - distribute the income to the ecosystem devs the way they see fit
Probably not. The amount of money they are taking in is very small, and if they start to ramp up revenue, then they actually need to start paying people for non-core work, like lawyers and accountants. Assuming that the money is received in Canada, by an Ontario registered non-profit, then it is really easy to do the accounting work for small dollar amounts (I ran several Manitoba and BC based non-profits previously for conferences and community work). If you start paying people who can't invoice you, then you need to sort out cross-jurisdictional payroll, and if you are making alot of purchases through other services.
Comments like this are unhelpful because it assumes that the developer of the project has a desire to run a business (and non-profits are businesses) rather than building and shipping an open source tool that scratches an itch. It's cool to speculate on what could be, but if you think that is the right approach, fork it, run the business transparently, and allocate a portion of revenue to be held in reserve the moment the core team for the project you forked asks for it.
Probably not. The amount of money they are taking in is very small, and if they start to ramp up revenue, then they actually need to start paying people for non-core work, like lawyers and accountants. Assuming that the money is received in Canada, by an Ontario registered non-profit, then it is really easy to do the accounting work for small dollar amounts (I ran several Manitoba and BC based non-profits previously for conferences and community work). If you start paying people who can't invoice you, then you need to sort out cross-jurisdictional payroll, and if you are making alot of purchases through other services.
Comments like this are unhelpful because it assumes that the developer of the project has a desire to run a business (and non-profits are businesses) rather than building and shipping an open source tool that scratches an itch. It's cool to speculate on what could be, but if you think that is the right approach, fork it, run the business transparently, and allocate a portion of revenue to be held in reserve the moment the core team for the project you forked asks for it.