Improve when and where the Consensus field is displayed #1955
Comments
|
@rjsparks@nostrum.com edited the issue description |
|
@housley@vigilsec.com changed owner from `` to |
|
@housley@vigilsec.com changed status from |
|
@housley@vigilsec.com changed resolution from `` to |
|
@housley@vigilsec.com commented When setting this value, ask the user if they want to include the consensus boilerplate in the RFC. |
|
@housley@vigilsec.com commented Fixed in 9d5a947: Clarify that the consensus field is talking about whether the doument will include the consensus boilerplate when it is published as an RFC. Fixes #1955. |
|
@henrik@levkowetz.com commented Fixed in d5d9d10: Merged in 9d5a947 from housley@vigilsec.com: |
owner:housley@vigilsec.comresolution_fixedtype_defect| by rjsparks@nostrum.comThe Consensus field is still causing confusion. See #1904.
There are a few other tickets that have touched on when this field is presented:
#1952, #1560, #1380, #1403
I'm of the strong opinion that we only show the field when it's relevant (and that's when it is nearing the handoff to the RFC Editor from streams that distinguish consensus). We should coordinate with each of the stream managers to make sure they agree before making a change.
Issue migrated from trac:1955 at 2022-03-04 04:57:43 +0000
The text was updated successfully, but these errors were encountered: