resolution_fixed type_defect | by rjsparks@nostrum.com
The writeup code currently assumes documents come from working groups. There's no UI for assigning a shepherd for an individual submission to the IETF, and the link for viewing the writeup returns an error. The AD isn't offered the ability to change the writeup.
See any active independent submission in an ADs workflow for an example. At the time of the submission of this ticket, https://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-namespace/ is a good example.
The writeup handling code is probably too closely associated with working groups (having been created as part of the WG tracker effort). The writeups should be more closely associated with documents, and less with working groups in the GUI. Keep an eye towards making it easy to allow other streams to have writeups on a document in the future.
Issue migrated from trac:834 at 2022-03-04 02:32:21 +0000
resolution_fixedtype_defect| by rjsparks@nostrum.comThe writeup code currently assumes documents come from working groups. There's no UI for assigning a shepherd for an individual submission to the IETF, and the link for viewing the writeup returns an error. The AD isn't offered the ability to change the writeup.
See any active independent submission in an ADs workflow for an example. At the time of the submission of this ticket, https://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-namespace/ is a good example.
The writeup handling code is probably too closely associated with working groups (having been created as part of the WG tracker effort). The writeups should be more closely associated with documents, and less with working groups in the GUI. Keep an eye towards making it easy to allow other streams to have writeups on a document in the future.
Issue migrated from trac:834 at 2022-03-04 02:32:21 +0000