Skip to content

Conversation

@evyncke
Copy link
Collaborator

@evyncke evyncke commented Nov 2, 2025

Address #9822

I did not dare to modify the /person/[email protected] hence a new URL /person/[email protected]/details

I.e., some pages in the NomCom part should probably be modified to point to this new /person/[email protected]/details

@evyncke
Copy link
Collaborator Author

evyncke commented Nov 2, 2025

Updated at least one page of the NomCom private site to link to this detailed page

@codecov
Copy link

codecov bot commented Nov 2, 2025

Codecov Report

❌ Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 88.54%. Comparing base (cbb0e2e) to head (5ca3d72).
⚠️ Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
ietf/group/templatetags/group_filters.py 66.66% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9857   +/-   ##
=======================================
  Coverage   88.54%   88.54%           
=======================================
  Files         316      316           
  Lines       42265    42274    +9     
=======================================
+ Hits        37423    37431    +8     
- Misses       4842     4843    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@evyncke
Copy link
Collaborator Author

evyncke commented Nov 2, 2025

As this issue was raised by @MikeBishop for this NomCom this might be interesting to run / deploy it on sandbox quickly once all the checks are completed successfully.

@rjsparks
Copy link
Member

rjsparks commented Nov 3, 2025

I've given the nomcom a custom report for now.

There's a lot that's good in this PR but it should move to /person/ and it can't deal with past roles correcty - the data the datatracker has about them is incomplete at best and misleading at worst. See the tools-discuss/chairs discussion about how poorly the datatracker can talk about the past chairs of a working group at the moment. We will need a data collection effort before we start reporting on anything more than what roles a person hold right now.

@evyncke
Copy link
Collaborator Author

evyncke commented Nov 3, 2025

I was not aware of the report, so, nothing urgent anymore.

I agree with the past roles.

I can move the last 5 years of meetings in the normal /people/ page if you prefer and remove the people/details one

@rjsparks
Copy link
Member

rjsparks commented Nov 3, 2025

I can move the last 5 years of meetings in the normal /people/ page if you prefer

Just checking: Is this really something we want to summarize for any anonymous person to quickly see about any other person? The data is public already, but it takes work to compile the summary. I would like to talk a bit more about the privacy implications before we add it here.

In the short term, a single page that concentrates this for nomcom members to see the values for all the nominees is something I expect nomcoms to ask for (rather than clicking through to each person's person page).

@richsalz
Copy link
Collaborator

richsalz commented Nov 3, 2025

I share the privacy concern. Leave it nomcom only.

@evyncke
Copy link
Collaborator Author

evyncke commented Nov 4, 2025

Up to the tools-team of course, but this smells like security by obfuscation as the data is easy to grab via the datatracker API anyway.

@richsalz
Copy link
Collaborator

richsalz commented Nov 4, 2025

Up to the tools-team of course, but this smells like security by obfuscation as the data is easy to grab via the datatracker API anyway.

Not sure it's easy but yes, it's adding a speed bump in favor of a nod to privacy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants