Choosing names

I understand that this is important, but rather than poll for name
preferences on every API point, here is what I propose we do:

1. The person generating the PR chooses the name they think best.
2. They announce their proposed change, making sure to include things
like names.
2a. (Optionally) They describe alternatives they considered and the
reasons they didn't choose them.
3. Everyone else does the usual standards forum thing of nitpicking
names, or in reviewing the change.

It's not clear that this would save time overall, but maybe by moving
the nitpicking stage later in the process we can avoid the costs for
uncontroversial things and it allows the person proposing a change to
get on with the substantial aspects of the change.  Changing names
when we collectively change our minds is a little tiresome, but not
overly so.

Received on Wednesday, 26 August 2015 01:43:20 UTC