"Pay for Open Source" form on homepage

[chadwhitacre]

← #4616

Pursuant to gratipay/inside.gratipay.com#987 and #4427, this PR moves the project listing off of the homepage and replaces it with a form to "Pay for Open Source."

Todo

• homepage form
  • fix test suite
  • link to blog post: Link to blog post justifying recommendation #4602
  • blippy blip: Tweak a couple tiny things #4603
  • batch some pre-reqs: New homepage plumbing #4606
  • implement JSON endpoint for basic form: Implement JSON endpoint for homepage form #4604
  • clean up JSON endpoint for basic form: Clean up JSON endpoint for homepage form #4617
  • wire up form to hit endpoint: Wire up homepage form to hit JSON endpoint #4613
  • implement error checking: New homepage error handling #4621
  • rationalize Optional sections → Rationalize how optional sections are treated #4609
  • "Choose an Ecosystem" → Add ecosystem chooser to homepage form #4610
  • "Invoice Details" → Expose receipt details to configuration on homepage form #4612
  • nice to have:
    • style credit card form: can't easily due to iframe (slack)
    • fix css bug w/ radio: slack
• receipt: Payments for open source receipt #4611
• update terms of service: (Deduplicate Terms of Service #4599 &) Update terms for "Pay for Open Source" #4600
• /browse/payments page → Browse payments #4607
• make a charger to stub out Braintree in test? (a la ConsoleMailer, etc.) Travis seems fine post-Update Braintree creds for test #4616?

Deploy

• wire up custom field pfos_uuid

[mattbk]

Thoughts as a potential company:

• what sort of file do I upload?
• how do I know how many technical employees a project has? Or if I have a lot of projects to give to, is there an average number I can use?
• what would an example tweet look like?

[chadwhitacre]

2780b0f:

[chadwhitacre]

what sort of file do I upload?

I have a UI in mind for that section of the form, hinted at in 2780b0f.

Stay tuned ...

how do I know how many technical employees a project has? Or if I have a lot of projects to give to, is there an average number I can use?

That's actually supposed to be your technical employees. Clarified sufficiently in 6a3285a?

what would an example tweet look like?

Hmm ... I was trying to leave this vague because I have no idea, really. Maybe we automate tweets eventually but probably not for a while and maybe never? To start we'll just manually tweet things out based on customer input. Nice and natural and organic. Longer term I actually have #1513 in mind with this. Once we collect the info it should be pretty easy to spit out SVGs for READMEs.

[chadwhitacre]

Initial feedback from @jdorfman in private Slack chat:

• "I love the button, 'Pay for Open Source'"
• re: Add an Ecosystem: "wait what does that mean"
• re: Gratipay taking 5%: "that’s fair"
• "the N,NNN X N is kinda confusing"
• "love it"

[chadwhitacre]

f557e1e

[chadwhitacre]

8c02f8b

[chadwhitacre]

Alright, once this is green I'm going to start using this as an integration branch for further work, ∆ is already 483 and we have a number of other things to do, not just on this form but that need to be deployed at the same time as the form.

[chadwhitacre]

Green! Rebasing on master ...

[chadwhitacre]

Rebased, was 3d5faf0.

[chadwhitacre]

Alright, that's four chunks of work remaining:

1. form wireup (big, includes db table(s), hold, & email dance),
2. ecosystem chooser (ecosystems table prepoped like countries but with logos(?), plus table to hold CSV uploads w/ (package manager, uid, weight))
3. terms of service (thinking basically a separate section governing this form based on VML vs. existing payments flow)
4. /browse/payments is our primary bragging outlet (besides Twitter) to start with, also where admins can see pending (no email verified) payments

[chadwhitacre]

Pushed off cancel homepage commits (moving those to a PR), was fe84e52.

[chadwhitacre]

Also rebased on master.

[chadwhitacre]

Per slack w/ +1s from @clone1018 and @dowski I am planning to try to self-merge and deploy this work ahead of gratipay/inside.gratipay.com#1044.

[chadwhitacre]

I'm getting ready to merge the next and final chain: #4621 → #4611 → #4600.

[chadwhitacre]

Let's see what Travis does with this. If green I think we are ready to merge and deploy! 😱

[chadwhitacre]

[chadwhitacre]

Testing out locally on this here integration branch.

[chadwhitacre]

Once Travis is green I plan to go for it—merge and deploy!

[chadwhitacre]

Waiting for Travis again ...