[cfp-interest 3522] Prioritizing CFP issues

[Jim Thomas]

An increasing number of issues threatens to overwhelm CFP. The technical discussion portion of the agenda this month includes 24 issues. Another 9 in our issues list remain to be addressed. Each issue requires understanding and coming to resolution, which may lead to developing a proposal and shepherding it through WG14 to publication. 
 
How can we make sure the more important issues are given due attention? Below are some of factors relevant to prioritizing issues for CFP work. I think the lists under each factor are roughly in priority order, but just roughly. I’m requesting group input in hopes of converging on helpful guidance for prioritizing issues.
 
Originator of the issue: 
  WG14
  Implementers or users
  CFP only
 
Nature of the specification problem at issue:
  Incorrect or meaningless
  Ambiguous (multiple reasonable interpretations)
  Incomplete
  Technically inconsistent 
  Unnecessarily obscure (to knowledgeable readers)
  Not ISO style
  Not C style
  Subject to misinterpretation by novice or hostile reader
  Poorly worded (with respect to commonly accepted style)
  Editorially inconsistent
 
Age of the specification at issue:
  Recent (e.g. incorrect integration of approved proposals or conflicts introduced by recent changes to the C2Y draft)
  Established
  New (yet to be introduced)
  Legacy (for existing code)
 
Difficulty (complexity, extent, contentiousness) associated with the issue:
  Easy
  Medium
  Hard
Dealing with hard, but otherwise high priority, issues will be challenging.
 
-        Jim Thomas
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20250610/015b30bd/attachment.htm>