Charter tool not sending (some) messages to Secretariat upon state change

[ietf-svn-bot]

owner:olau@iola.dk resolution_fixed type_defect | by cmorgan@amsl.com

---

Previously, when an AD moved a WG charter into internal review, the Secretariat got a message that looked something like this:

From: "Datatracker via RT" iesg-secretary@ietf.org
Subject: [www.ietf.org/rt #50974] Regarding WG bfd: State
changed to Internal review

The WG "Bidirectional Forwarding Detection" (bfd) has been set to
Internal review by Adrian Farrel.
Please place it on the next IESG
telechat and inform the IAB.

WG: http://datatracker.ietf.org/wg/bfd/charter/
Charter: http://datatracker.ietf.org/doc/charter-ietf-bfd/

We are no longer getting those messages. Ron Bonica moved wpkops into Internal review on 2013-01-22, and nothing was received by iesg-secretary@ietf.org.

Interestingly, on the same day, Stephen Farrell moved kitten into internal review, and we did get a message, but not the boilerplate one above. The message was something he put into the "Message to the Secretariat" field at http://datatracker.ietf.org/doc/charter-ietf-kitten/state/.

We would like to still get notification when a charter moves into internal review whether the AD puts anything in that field or not, because we still have to send the internal review message to the IESG and IAB manually.

---

Issue migrated from trac:949 at 2022-03-04 02:42:30 +0000

[ietf-svn-bot]

@olau@iola.dk commented

---

After some investigation, it turns out the problem is that the boilerplate code is not being inserted because of a bug in the fix to issue #901. I'll attach a patch to fix that.

IMHO, long-term someone should write down how the chartering workflow is from your (Secretariat) point of view, then we should revamp this part of the tool to take that into account and avoid unnecessary manual chores. I don't know if you're interested in that, if so perhaps either Ryan could do it or you could ask Ray to allocate some hours for me and I would be happy to do it (it's unfortunately outside the original project grant). It always bothered me that the original spec in several places just ended with a "then email the Secretariat and let them deal with it".

[ietf-svn-bot]

@olau@iola.dk uploaded file charter-state-js-bugfix.patch (0.5 KiB)

Fix for Javascript renaming bug (messages -> info_msg)

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

From bf7b128:

Applied patch from olau@iola.dk, see issues #949 and #877.

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from new to closed

[ietf-svn-bot]

@rjsparks@nostrum.com changed resolution from `` to fixed

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Amy reports this bug is fixed for her. I'm moving the discussion of another round of improvements of secretariat handling of charters to a separate thread.