I was listening to some of the discussion at the CC meeting yesterday. There was a concern about items that don’t appear on a calendar tend to disappear.
I recall that there’s a particular innovation to the standard rules of order, for which I’ve been trying to find a reference but can’t, that creates a “stack” of issues. This stack becomes a list of things that are in a “holding pattern” which are not active, not scheduled, but also not forgotten.
Have you heard of this before?
I was thinking that this might be a friendly offering to the CC as a possible procedure to aid in not losing issues that are not under current consideration.
As I was thinking about this, a stack does not necessarily end up being a linear FIFO (first in, first out) list. Although more complicated, there might be a GANTT like representation of the stack such that there are dependencies on issues. So, a issue might be placed in the stack “until X date” or “until issue X is resolved” … but this might be too complicated or more complicated than is necessary.