Merge pull request #861 from gratipay/projects

Revise review howto in light of ToS changes

nav.py

@@ -50,9 +50,11 @@ def __init__(self, website, parent, fs, slug):
                 if isfile(with_spt):
                     new_fs = with_spt
                 child = NavItem(website, self, new_fs, slug)
+                if child.title is None:
+                    continue
                 self[child.slug] = child  # Populate self as an OrderedDict
 
-        self.title = context.get('nav_title', '[Untitled]')
+        self.title = context.get('nav_title')
 
 
     def __str__(self):

www/howto/review-projects.spt

@@ -0,0 +1,28 @@
+nav_title="Review Projects"
+[---]
+[---] text/html
+
+In keeping with our [Terms of Service](https://gratipay.com/about/terms/), all
+projects on Gratipay are subject to a review process when they first apply, and
+as needed thereafter. Review happens in public in [the `project-review`
+repo](https://github.com/gratipay/project-review/issues).
+
+To help review projects,
+[watch](https://help.github.com/articles/watching-repositories/) the repo.
+Anyone who thinks that a project does not belong on Gratipay has to make a case
+publicly on GitHub, and we have to leave enough time for the community to weigh
+in before rejecting a project. [Chad Whitacre](https://github.com/whit537) has
+the final say.
+
+The only way to find out if a project will be approved is to
+[apply](https://gratipay.com/new) for a project. We don't answer, “Will
+you accept foo?” questions apart from the actual project application
+process.
+
+*Note: Issues in `project-review` before December, 2016 had more stringent
+requirements, explained in the [previous
+version](https://github.com/gratipay/inside.gratipay.com/blob/d73f4c7438bb2cc8781c0298deb3f7b2edeab176/www/howto/review-teams.spt)
+of this document. See also:
+“[Gratipocalypse](https://gratipay.news/gratipocalypse-42fd0ec0d9e8)”
+and “[Gratipay
+2.0](https://gratipay.news/gratipay-2-0-2453d3c53077)”.*

www/howto/review-teams.spt

@@ -1,32 +1,3 @@
-nav_title="Review Teams"
 [---]
+request.redirect('./review-projects')
 [---] text/html
-
-All Teams on Gratipay are subject to a review process when they first apply,
-and as needed thereafter, to make sure they and we are a good fit for each
-other. Review happens in public in [the `team-review`
-repo](https://github.com/gratipay/team-review/issues). To help review Teams,
-[watch that repo](https://help.github.com/articles/watching-repositories/).
-
-There are two criteria for approval.
-
-First, the Team must offer open work. Here's the thought experiment: "Could I
-as an individual voluntarily start doing the Team's work without having to
-coordinate with anyone?" Review their onboarding documentation and to-dos to
-make a determination. This is a positive criterion: we assume a Team is closed
-unless they can show us that they're open.
-
-Second, the Team's brand must not clash too strongly with our own [brand
-values](/big-picture/brand/). This is obviously much more of a judgement call
-than the first criterion. Past rejections are the best indicator of how to
-apply this criterion to new applications. This second criterion is negative:
-Teams are innocent of brand violation until proven guilty. Anyone who thinks
-that a Team *does* clash with our brand has to make a case publicly on GitHub,
-and we have to leave enough time for the community to weigh in before rejecting
-a Team. The buck does have to stop somewhere, of course. Currently, Gratipay
-founder [Chad Whitacre](https://github.com/whit537) is the final arbiter of
-decisions around brand fit.
-
-The only way to find out if a Team will be approved is to apply for a Team. We
-don't answer, "Will you accept ________?" questions apart from the actual Team 
-application process.