Keeping it simple, lets focus on two things.
First, lets take PaceHeadInEntry, which a number of people have indicated that they want either this or something like it before the format can be declared done.
Second, lets see if we can significantly reduce the number of alternative syntaxes being considered for link. For starters, I'm taking Tim's request (as echoed by Rob) that link related Paces which have not been updated recently be recommended for closure.
Even with this done, this would have been eight retired Link related paces, and eight new Link related Paces. However, with Danny retiring two in favor of PaceFieldingLinks (thanks, Danny!), this shifts the balance to ten retired and six under active consideration.
I'd like to reiterate my request that for the ones that we don't come to consensus on this time, we don't simply put these back in the queue.
Effectively this means that if somebody objects to a pace, one of three things happens:
(1) the person agrees to work on fixing the issues that they have
identified, and the issue goes back on the queue with this
understanding. (2) the chairs note the objection, but finds that there is enough
support for the proposal to declare rough consensus, and the
proposal gets accepted.(3) the pace gets rejected.
- Sam Ruby
