Relax open work requirement

[chadwhitacre]

Ever since the Gratipocalypse, we've required the "Teams" receiving money on Gratipay to go through an application and approval process. One of our main criteria for approval has been that Teams provide what we called "open work":

Open Work means that the Team provides a clear path for any individual to voluntarily begin contributing to the Team's work and to share in any revenue the Team generates.

Experience has shown this to be too restrictive. We still want to encourage and emphasize open work on Gratipay, but we don't want to require it. The purpose of this project is to relax the open work requirement.

---

✈️ This is the flight deck for the Relax Open Work Requirement project. ✈️

---

Todo

• update the user interface
  • merge Edit TOS to decouple payins and payouts #4117
  • merge Remove the To-do URL #4214
  • merge Revise the New Project form #4130
  • merge Revise site copy to keep up with ToS changes #4157
  • merge to master
  • deploy
• update the review repo
  • rename the team-review repo to project-review
  • update TEAM_REVIEW_REPO in the Heroku environment
  • merge Switch from "teams" to "projects" to keep up with decoupling project-review#281
• update Inside Gratipay
  • merge Revise review howto in light of ToS changes inside.gratipay.com#861
• blog post: https://gratipay.news/from-teams-to-projects-45c46718507b
  • update link to terms-of-service.md diff
  • publish
• announce on Twitter
• notify owners of projects that are accepted or under review
• notify "everyone" via email: Send email for Terms notification #4232 → Finish sending out Terms notification #4282 → Actually mail the terms notification inside.gratipay.com#972
• put notice on website: Update announcement #4229
• land Make search search teams as well #4222 → Clean up descriptions in search #4266

[chadwhitacre]

Looks like we have two big pieces of work remaining before we can merge this branch to master: #4130 and #4157.

We should also figure out testing. Oooo! I have an idea ... ;-)

[chadwhitacre]

Yesssss ... now to make sure that propagates to PRs against this branch ...

[chadwhitacre]

👍

Seeing Travis on #4130 ...

[chadwhitacre]

Cool. We'll just need to remove this branch from .travis.yml as part of our final merge to master.

[chadwhitacre]

New plan: build all branches after all, so that Travis will test PR chains (e.g.).

[chadwhitacre]

Rebased on master, was c2644b5.

[chadwhitacre]

I squashed all of #4117 into a single commit, to make this integration PR easier to read and work with.

[chadwhitacre]

Blech. cf13cc6 is hitting the #4224 bug again, even with Faker 0.7.3. 😞

https://travis-ci.org/gratipay/gratipay.com/builds/182073772

[chadwhitacre]

Lol ... and 25018df hits the "13 failed" that we're also seeing at #4130 (comment). That one at least goes away with a rerun.

[chadwhitacre]

That one at least goes away with a rerun.

Which of course makes it harder to debug. :-/

[chadwhitacre]

Rebased, was 25018df.

[chadwhitacre]

@mattbk Reverting is different than rebasing. Reverting adds a second commit that is the inverse of the first. Rebasing lets you remove the first.

[chadwhitacre]

slack

[mattbk]

Rebased, was fd2c60a.

[chadwhitacre]

I'm drafting a blog post.

[chadwhitacre]

We need to figure out some sort of on-site notice, and maybe email.

[chadwhitacre]

Simple post: https://gratipay.news/from-teams-to-projects-45c46718507b.

[chadwhitacre]

Slight revision on the post: https://gratipay.news/from-teams-to-projects-45c46718507b.

[chadwhitacre]

Driving in slack.

[chadwhitacre]

💃

[chadwhitacre]

We're live with the UI and repo changes and blog post! Waiting to announce until tomorrow.

---

---

[chadwhitacre]

Regression:

[chadwhitacre]

[chadwhitacre]

Regression fixed in #4230.

[chadwhitacre]

Twittered: https://twitter.com/Gratipay/status/808702383282880516.

[chadwhitacre]

Alright ... email! Where did we do that before? How did we do it?

[chadwhitacre]

Me starts with gratipay/inside.gratipay.com#376 ...

[chadwhitacre]

Here we go:

gratipay/inside.gratipay.com#235
→ #3385 (comment)
→ #3510

I'm planning to write a script to queue this locally, with a production Mandrill key in local.env for sending.

[chadwhitacre]

Yeah, that's got the whole live-blog on it.

[chadwhitacre]

PR in #4232.

[chadwhitacre]

Congratulations, people! With gratipay/inside.gratipay.com#972, we have relaxed our open work requirement! 🌝 👏 💃 🌻 🎆