rfc1: refine maintainer PR review process

Problem: RFC 1 says that maintainers must not make value judgements
on correct PRs, must merge them rapidly, and must express value
judgements as patches, which contradicts current project practice.

Instead of "rapidly", refer to RFC 48 which is intended to provide
remedies for "the maintainers are ignoring me!" problems.

Adjust the "value judgement" policy so that maintainers can continue to
ask contributors to rework PRs to increase their value and avoid needless
churn in the commit history.

This policy was likely added to C4.1 to solve a real problem with an
intransigent 0MQ maintainer.  We can always come up with a governance
remedy if Flux finds itself in a similar situation down the road, but
for now we seem to be doing OK.

Author: garlick

spec_1.rst

@@ -156,18 +156,14 @@ Development Process
 
 -  Maintainers SHOULD NOT merge their own patches except in exceptional cases.
 
--  Maintainers SHALL NOT make value judgments on correct patches.
-
--  Maintainers SHALL merge correct patches from other Contributors rapidly.
+-  Maintainers SHALL merge correct patches from other Contributors as described in :doc:`spec_48`.
 
 -  The Contributor MAY tag an issue as "Ready" after making a pull request for the issue.
 
 -  The user who created an issue SHOULD close the issue after checking the patch is successful.
 
 -  Maintainers SHOULD ask for improvements to incorrect patches and SHOULD reject incorrect patches if the Contributor does not respond constructively.
 
--  Any Contributor who has value judgments on a correct patch SHOULD express these via their own patches.
-
 -  Maintainers MAY commit changes to non-source documentation directly to the project.
 
 -  Autotools products, if applicable, SHOULD NOT be checked into the project