Update terms for "Pay for Open Source"

[chadwhitacre]

← #4611

Terms changes in light of #4598 on the way to #4427.

[chadwhitacre]

Gosh. This is big.

From slack:

The flow of funds here is tricky.
It may not be the exact same payment processor exemption as before.

Because it's lump sum in --> trickle out?

Mmm … because I think we want to abstract companies and projects from each other.
We want project maintainers to be contractors of Gratipay.
We don’t want them to be contractors of the companies.
Because otherwise the company beancounters are going to have hundreds or thousands of extra contractors to deal with!
Don’t wanna piss off the beancounters. ☺️
A company should get a receipt immediately when they pay, and that should be the end of it.
We can send them a report on projects in their “bundle” when we remind them to pay again, but that’s just a report on projects they’re interested in, not any formal part of the transaction.

So the company is paying Gratipay, end of story. Then Gratipay pays the projects.

Correct.
Gratipay is basically a software development company representing all of open source software.
We’re a Microsoft or Oracle or Red Hat.
Companies pay us for software.
We pay people to write software.

[chadwhitacre]

I think Bountysource is structured something like this. I link the stealth mode startup our old lawyer and some Red Hat formers are doing is also structuring themselves somewhat along these lines.

[chadwhitacre]

I had an idea on this: split it on anon/auth. "These are the terms for authenticated users: . These are the terms for anonymous users: ."

[chadwhitacre]

Rebased, was 7469216.

[chadwhitacre]

Thinking for now a simple section like:

Payments made through the form on the homepage are non-tax-deductible donations to Gratipay.

[chadwhitacre]

Short and sweet. Waddya think, @mattbk?

[chadwhitacre]

🚨 Self-merge license 🚨