Talk about revising the team application

[mattbk]

https://github.com/gratipay/gratipay.com/blob/master/www/new.spt

Follows from #4117 as part of Decouple that we'll need to change the team application form.

[mattbk]

I'd like to break this down into groups:

• Basics (required)
  • Team name
  • Image
  • Product or service
  • Homepage
  • Agree to public review
  • Agree to TOS
• Open work fields (optional)
  • Include short sentence explaining open work, with links.
  • Onboarding URL
  • Todo URL
• TWYW fields (optional)
  • Include short sentence explaining TWYW payouts, with links.
  • Agree to Payroll TWYW payouts

[chadwhitacre]

Do we need the open work and TWYW fields?

We're not going to offer TWYW as a product again for a year or three. If/when that happens I expect we'll have a new flow for Projects to turn that feature on. We can explain the product and re-up terms agreement then.

For open work ... I guess we've already gone to the trouble of verifying most of the existing 200+ projects as providing open work. Can we make that a separate verification flow rather than tying it to initial onboarding? What's the benefit we offer to those that go through the process?

[mattbk]

We're not going to offer TWYW as a product again for a year or three. If/when that happens I expect we'll have a new flow for Projects to turn that feature on. We can explain the product and re-up terms agreement then.

Good with that.

For open work ... I guess we've already gone to the trouble of verifying most of the existing 200+ projects as providing open work. Can we make that a separate verification flow rather than tying it to initial onboarding? What's the benefit we offer to those that go through the process?

I can be good with that. We don't currently have any benefit. I think the levels we've talked about would be appropriate under #3736 (once we sort, we need to have a default sort order...). We should keep track of those projects that are already "open work" approved, so we can grandfather them in when we get to that (which I suppose could just be a list on a ticket somewhere, rather than dumping it into the database right now).

[mattbk]

• Help (include short description and/or link to other pages at Gratipay.com/about; Project applications should have details and links #3859)
  • Why do we have to apply?
  • What happened to "open work"?
  • Do I need a project for everything I do, or can one project cover everything? (Teams of one)
• Basics (required)
  • Team name
  • Image
  • Product or service
  • Homepage
  • Agree to public review
  • Agree to TOS

[mattbk]

I think it should remain an "application" (along with verbs on the form) because we review it for approval, but @whit537 just calls it a "form" at gratipay/inside.gratipay.com#821 (comment). Thoughts on either way?

[mattbk]

I'd be working on this but am running into installation issues, apparently due to upgrading to El Capitan: #4131.

[mattbk]

Back on it, comments over at #4130.

[chadwhitacre]

What's the difference between this and #4130, @mattbk?

[mattbk]

This is an issue, that's a PR.

[chadwhitacre]

Gotcha.

[chadwhitacre]

Closing in favor of #4130! :-)