Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

How-to for reviewing team applications #311

Closed
mattbk opened this issue Aug 13, 2015 · 18 comments
Closed

How-to for reviewing team applications #311

mattbk opened this issue Aug 13, 2015 · 18 comments
Milestone

Comments

@mattbk
Copy link
Contributor

mattbk commented Aug 13, 2015

Reticketed from gratipay/gratipay.com#3677 (comment).

A how-to page about reviewing team applications should be created at http://inside.gratipay.com/.

Justification: All criteria are not clear for a team to be accepted.

@chadwhitacre
Copy link
Contributor

Agreed.

@mattbk
Copy link
Contributor Author

mattbk commented Aug 13, 2015

So far at the other ticket, I think we've ended up with two solid criteria. In my own words, teams must show that they have a:

  1. "work-first" philosophy (you can help the team before becoming a part of the team)
  2. revenue plan, not just a work plan

Assessment of "matching the mission and brand values/guidelines of Gratipay" has not been addressed.

@mattbk
Copy link
Contributor Author

mattbk commented Aug 14, 2015

"Work-first" is not the best phrase to use because it means other things.

Explained more at gratipay/gratipay.com#3677.

@mattbk
Copy link
Contributor Author

mattbk commented Aug 15, 2015

Include also:

We'll just have it as our policy that a Review ticket must be open at least seven days before it can be decided upon.

@chadwhitacre
Copy link
Contributor

Assessment of "matching the mission and brand values/guidelines of Gratipay" has not been addressed.

@mattbk I think it's actually a negative criterion, not a positive one. The question is not, "Does this Team match our mission and brand values," but rather, "Does this Team not match with our mission and brand values? Does it clash too strongly for comfort?"

@chadwhitacre
Copy link
Contributor

Innocent until proven guilty, in other words. The default assumption is that any given Team does not clash with our brand, and the burden of proof is on the person who wants to say that the Team does clash. What's the clash?

@chadwhitacre
Copy link
Contributor

Page is up here: http://inside.gratipay.com/howto/review-teams.

@chadwhitacre
Copy link
Contributor

I think anyone is permitted to make a case on a team review ticket that a team clashes with the Gratipay brand. But as @mattbk says, "Even at an open company, [...] the buck has to stop somewhere." Right now the buck stops with me. I'm the final judge of whether a Team clashes too strongly with the Gratipay brand. I expect to hand that responsibility off at some point when Gratipay is further along.

And what's important: even though I'm the buck-stopper, I still have to make a case in public. I don't get to nix Teams without making a case and leaving sufficient time for others to weigh in. See KanColleWidget for an example (and see TechRaptor for an example of what happens when we don't make the case properly up-front).

@chadwhitacre
Copy link
Contributor

@mattbk @seanstrom et al. How does the latest howto for team review look?

http://inside.gratipay.com/howto/review-teams

@seanstrom
Copy link

The wording seems pretty good. Is the idea here to focus on that we're pretty open, accepting to everyone, except for those who position themselves as not open or accepting. I know the documentation should speak for itself, but I just wanted to clarify in my words.

@mattbk
Copy link
Contributor Author

mattbk commented Aug 25, 2015

What about the payroll checkbox and what that means?

@chadwhitacre
Copy link
Contributor

@mattbk It seemed to me that if we said something about the payroll checkbox in this document, then we would also want to say something about the parallel checkboxes agreeing to public review and the entire terms of service. I don't think we need to say anything about the public review and ToS checkboxes, therefore I don't think we need to say something here about payroll.

Put another way: the point of this doc is to describe our procedure for people to review Teams. Ensuring that they've passed initial form validation doesn't need to be part of our procedure, since initial form validation is admirably performed by a computer.

@mattbk
Copy link
Contributor Author

mattbk commented Aug 26, 2015

Ahh, I wasn't sure whether you were booting people who didn't check that box or not.

@chadwhitacre
Copy link
Contributor

Ahh, I wasn't sure whether you were booting people who didn't check that box or not.

We don't let them submit the form in the first place without checking all the agreement boxes:

https://github.com/gratipay/gratipay.com/blob/1887/www/teams/create.json.spt#L29-L34

@chadwhitacre
Copy link
Contributor

Is the idea here to focus on that we're pretty open, accepting to everyone, except for those who position themselves as not open or accepting.

I would tend not to use the word "accepting," because clearly we're not accepting of everyone: we have a ~10% rejection rate so far. Claiming to be "accepting" sounds dishonest to me.

@chadwhitacre
Copy link
Contributor

except for those who position themselves as not open or accepting.

This exception isn't sufficient, either: a community such as 8chan is in a real sense more open and accepting than we are, because their formal rules for exclusion are much looser than ours. Their informal rules do have a tendency to exclude people, but having to depend on this formal/informal distinction weakens the force of the exception.

@chadwhitacre
Copy link
Contributor

Their informal rules do have a tendency to exclude people

... in the sense of driving them away, because of the discomfort of being exposed to the unrestrained behavior of others.

@chadwhitacre
Copy link
Contributor

We're linking to the new howto as of gratipay/gratipay.com#3717. Closing here. Reticket any additional issues with the Review Teams howto.

@chadwhitacre chadwhitacre added this to the Pivot milestone Oct 22, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants