Background: RFCs should be in development until frozen or retired.
Problem: Frozen RFCs are being updated.
----------------------------------------------------------------------
Solution #1: Ignore updates to frozen/retired RFCs
Solution #2: Allow frozen/retired RFCs to be updated,
if the status is unchanged.
Solution #3: Allow frozen/retired RFCs to be updated, but only
if the update further clarifies the RFC
----------------------------------------------------------------------
There are currently some RFC updates in the queue that update frozen
RFCs. Once again the progression is:
Developing
/ \
Frozen Retired (or Withdrawn or Retracted)
| |
(No futher discussion required)
New statuses may appear, such as "Accepted" and "Rejected", but it is
premature to talk about that until Larry actually starts accepting
or rejecting RFCs (should he so choose).
A status change from "Frozen" to "Retired" may be acceptable. Such
updates would indicate that discussion came to an end on a topic,
and subsequent discussions caused the author to remove that idea
from consideration.
So, what's everyone else think? I really don't want to write up
an RFC about this. :-)
Z.
