New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Dead documents to have no AD #993
Comments
@rjsparks@nostrum.com changed priority from |
@rjsparks@nostrum.com changed keywords from `` to |
@rjsparks@nostrum.com commented Offering this as a choice is easy. However, there is almost certainly code (especially template code) that assumes ad is not None once a document has the IESG processing taint. Implementing this request will require a careful scrub for such assumptions. |
@jmh@joelhalpern.com commented Convincing the form to allow (none) is complex. |
@rjsparks@nostrum.com commented Addressing this will be tied up in dealing with returning to a "No special state" state for each doc state machine. See #303 |
@rjsparks@nostrum.com changed status from |
@rjsparks@nostrum.com changed resolution from `` to |
@rjsparks@nostrum.com commented Fixed in 9f54af3: Allow responsible AD to be None for documents in iesg states idexists and dead. Fixes #2803 and #993. Commit ready for merge. |
@henrik@levkowetz.com commented Fixed in 1edc863: Merged in 9f54af3 from rjsparks@nostrum.com: |
keyword_sprint
resolution_fixed
type_enhancement
| by resnick@episteme.netThe datatracker UI does not allow you to set the Responsible AD back to "(None)" once the document is moved into IESG processing. For documents in the "Dead" state, being able to remove the AD would be useful.
Issue migrated from trac:993 at 2022-03-04 02:46:16 +0000
The text was updated successfully, but these errors were encountered: