Skip to content

Conversation

jennifer-richards
Copy link
Member

This refactors some internals of the liaison statement (LS) forms to improve testability and clarity. Adjusts the options available for "To" and "From" groups based on the user's role(s).

Note that these changes only impact the groups that can be used to populate the "From > Groups" and "To > Groups" fields. The "From > From contact", "From > Response Contacts", and "To > Contacts" fields and their behavior are unchanged. Furthermore, the "From" header field on the actual email that delivers the LS is not affected by this.

In the following, "any group" means IETF, IESG, IAB, any active area, or any active WG.

Roles permitted to add new outgoing LS:

  • Area Director
    • From their area, an WG in their area, the IETF, or the IESG
    • To any SDO group
  • IAB Chair
    • From any group (Was previously only the IAB)
    • To any SDO group
  • IAB Executive Director (No current such role exists in the datatracker)
    • From any group (Was previously IAB only)
    • To any SDO group
  • IETF Chair
    • From any group (Was previously only the IETF)
    • To any SDO group
  • Liaison Manager (of an SDO group)
    • From any group
    • To only their SDO group
  • Secretariat
    • From any group
    • To any SDO group
  • WG Chair
    • From only their WG
    • To any SDO group
  • WG Secretary
    • From only their WG
    • To any SDO group

Roles permitted to add new incoming LS (these were not changed):

  • Authorized Individual (of an SDO group)
    • From only their SDO group
    • To any group
  • Liaison Manager (of an SDO group)
    • From only their SDO group
    • To any group
  • Secretariat
    • From any SDO group
    • To any group

Still a WIP to confirm the changes are in the right direction and for some further code cleanup.

Related to ietf-tools/liaison-tooling-2025a#4 and #4514

@mirjak
Copy link

mirjak commented May 6, 2025

Actually not sure we need a separate IAB Executive Director. The IAB Executive Director is a member of the Secretariat, so the role should be sufficient. This is also related to this discussion: ietf-tools/liaison-tooling-2025a#7

Also I think we actually want to get rid of the Authorized Individual but we need to fully double-check that we don't use it anymore but that's the outcome of ietf-tools/liaison-tooling-2025a#25 and ietf-tools/liaison-tooling-2025a#11

I think I asked that Robert at some point and he might have looked into this already but I can find it right now: Is there a list of all currently Authorized Individuals somewhere, so we could quickly review it?

@jennifer-richards
Copy link
Member Author

Ok - I won't worry about the permissions for those roles then (i.e., I'll leave them as they are in this PR).

I think I asked that Robert at some point and he might have looked into this already but I can find it right now: Is there a list of all currently Authorized Individuals somewhere, so we could quickly review it?

The easiest way to see these is through the Django admin in the sandbox. I can give you instructions for that offline. There are 137 Authorized Individuals for SDO groups.

@rjsparks
Copy link
Member

This addresses the from form issue for the people who currently have access - lets at least get this into a feature branch now, and add modeling liaison coordinators with a separate PR.

rjsparks
rjsparks previously approved these changes May 23, 2025
Copy link

codecov bot commented May 23, 2025

Codecov Report

Attention: Patch coverage is 97.61905% with 2 lines in your changes missing coverage. Please review.

Please upload report for BASE (feat/liaisons@06de5dd). Learn more about missing BASE report.

Files with missing lines Patch % Lines
ietf/liaisons/forms.py 97.50% 2 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##             feat/liaisons    #8883   +/-   ##
================================================
  Coverage                 ?   88.81%           
================================================
  Files                    ?      314           
  Lines                    ?    41441           
  Branches                 ?        0           
================================================
  Hits                     ?    36807           
  Misses                   ?     4634           
  Partials                 ?        0           

☔ 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.

@jennifer-richards jennifer-richards changed the base branch from main to feat/liaisons May 26, 2025 14:09
@jennifer-richards jennifer-richards marked this pull request as ready for review May 26, 2025 14:09
@jennifer-richards jennifer-richards merged commit fca02cf into ietf-tools:feat/liaisons May 26, 2025
10 checks passed
@jennifer-richards jennifer-richards deleted the liaison-contact-privs branch May 26, 2025 14:10
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants