Skip to content
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

Replaced Proposed Working Group Still Shows Up on AD's Responsibility List #2889

Closed
ietf-svn-bot opened this issue Feb 24, 2020 · 12 comments
Closed

Comments

@ietf-svn-bot
Copy link

resolution_fixed type_defect | by [email protected]


Éric Vyncke notes that the TMRID Proposed Working Group that was replaced by the DRIP Working Group still shows up for him here:

https://datatracker.ietf.org/doc/ad/%C3%A9ric.vyncke

under the header "start chartering/rechartering"

TMRID is marked as "replaced" in the datatracker, and does not show up on the general "chartering groups" list. Replaced Proposed Working Groups should not show up as current work items on their datatracker page, but we want to keep the history. Can we create a new header for "Replaced Charters" like there is a header for "Replaced Internet-Drafts" and have them show up at the bottom of the page with the replaced I-Ds? That way the Area Director isn't trying to figure out their next step for a charter that is replaced.

Thank you!

Amy


Issue migrated from trac:2889 at 2022-03-04 07:41:45 +0000

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from new to under_review

@ietf-svn-bot
Copy link
Author

@[email protected] commented


I don't think replaced Internet-Drafts show on that page, but I'll verify (or will leave it as part of the work to do to resolve the issue) that's what the code does. My initial inclination is that the document not appear on this page at all. It will still show up as replaced in searches, so history isn't lost.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Ah. When I look at Deborah's page:

https://datatracker.ietf.org/doc/ad/deborah.brungard

The very last section is "Replaced Internet-Drafts." So I was going from that. As long as the history is retained I don't see a problem with it dropping off the page for the AD.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


On inspection, the code will show replaced documents, but the real issue here is that the replaced charter is now in the wrong chartering state. When it was replaced, the chartering state should have been changed to the "not under review" charter state.

As a workaround for Éric, we can give that charter the correct chartering state and it will disappear from the ad document page. This is related to #2872 and is a duplicate of a very old ticket at #1286.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Also related: #2873

@ietf-svn-bot
Copy link
Author

@[email protected] changed priority from n/a to major

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from under_review to closed

@ietf-svn-bot
Copy link
Author

@[email protected] changed resolution from `` to fixed

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Fixed in 79bb245:

Move charters for replaced groups to a new replaced state. Close any outstanding ballots on them. Fixes #2889, #2873, and #1286. Commit ready for merge.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Instead of moving the charter state to 'notrev', I created a new 'replaced' state so that search results and history are clearer.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Fixed in 79bb245:

Move charters for replaced groups to a new replaced state. Close any outstanding ballots on them. Fixes #2889, #2873, and #1286. Commit ready for merge.

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Fixed in 08130f4:

Merged in 79bb245 from [email protected]:
Move charters for replaced groups to a new replaced state. Close any outstanding ballots on them. Fixes #2889, #2873, and #1286.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant