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

Area names are not correct for renamed areas in proceedings #7706

Closed
1 task done
gloinul opened this issue Jul 19, 2024 · 1 comment · Fixed by #7723
Closed
1 task done

Area names are not correct for renamed areas in proceedings #7706

gloinul opened this issue Jul 19, 2024 · 1 comment · Fixed by #7723

Comments

@gloinul
Copy link

gloinul commented Jul 19, 2024

Describe the issue

I was looking back at older proceedings and looked at IETF 107. The areas listed here includes WIT, and do not list Transport (TSV). There appear the datatracker fails maintain/present correctly what area WGs belonged to at the particular point in time and meeting. This leads to strange presentation like for 107 where MASQUE WG was TSV, but WebTrans was ART at that time. And ART do exist as category due to other WGs. This appears to be common across all proceedings pages that are generated based on datatracker database.

Example: https://datatracker.ietf.org/meeting/107/proceedings

Code of Conduct

@gloinul gloinul added the bug Something isn't working label Jul 19, 2024
@rjsparks
Copy link
Member

This is most likely bug in the proceedings templates where it's not using group_parent_at_the_time (or getting to parrent correctly from group_at_the_time) where it should be.

russhousley added a commit to russhousley/datatracker that referenced this issue Jul 21, 2024
When generating IETF meeting proceedings, use the Area Acronym for each WG at the time of the meeting. Fixes ietf-tools#7706.
rjsparks pushed a commit that referenced this issue Aug 5, 2024
When generating IETF meeting proceedings, use the Area Acronym for each WG at the time of the meeting. Fixes #7706.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants