Process question

We are experimenting with the use of issues (and the labels "question" and
"proposal") to manage a workflow of technical discussion -> concrete
proposal -> consensus.

This seems to have worked well to date.

The original intent in using the "question" and "proposal" lables was to
contain all of the discussion in a single thread under the "question" and
for the "proposal" to be short lived.

Any discussion on the "proposal" thread is intended to be nitpicks with the
language or minor suggested amends that are made before the proposal is
tabled on a call.

Following the call the "proposal" thread is either closed as "resolved" or
"unresolved" or postponed to the next call if we didn't have time to deal
with it.


*Examples:*
https://github.com/w3c/webpayments/issues/57
Was not discussed on the call so it was left open and was postponed till 28
January.
(Assigned to a new milestone)

https://github.com/w3c/webpayments/issues/58
Was discussed and resolved. The issue was closed and a comment added
indicating that the proposal was accepted.

https://github.com/w3c/webpayments/issues/62
Was discussed and the proposal was rejected in favour of a re-write for
more clarity.
The issue was closed but the associated "question" thread was left open for
discussion. Subsequently a new proposal (
https://github.com/w3c/webpayments/issues/67) was tabled for 28 January.


*Question:*
On the 21 January call we discussed the proposal at issue #63:
https://github.com/w3c/webpayments/issues/63

There was not consensus on this proposal and so clearly further discussion
is required.

My preference for the process would be to keep our discussion in one place
if possible and for this to be the "question" thread. Unfortunately a lot
of discussion has already taken place after the call on the "proposal"
thread so closing this thread would potentially lose that history.

For now I am going to manually copy that all across to the "question"
thread and close the proposal as unresolved BUT I'd like to also close
unresolved proposals with some kind of follow on action.

Since we didn't finish up with an action on this particular proposal I am
going to give myself an action to summarise the arguments on a wiki page.
Following this the same (or a similar) proposal may be tabled again or a
counter-proposal that suggest an alternative approach.

Any thoughts on this process?