You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just requested a new interim meeting for the OpenPGP working group. It will be a remote meeting starting at 2025-02-10T11:00:00Z. I asked the system to create a meetecho room.
Because of my own confusion about the UX, i failed to include an agenda in the initial meeting request.
I went back to edit the request (at https://datatracker.ietf.org/meeting/interim/request/interim-2025-openpgp-01/edit ), added the agenda, and hit "Submit". It appears to have saved my request, but it produced a warning (which i failed to record verbatim) about not having included the remote instructions in the request (maybe because the meetecho information hasn't been completed yet?).
I went back to re-edit the request to see whether i could reproduce it the warning, and now when i edit the request and submit, i don't get any such warning.
If you'd like me to try to replicate the problem with a phony meeting request so i can get a verbatim copy of the error message, please let me know and i'll do that.
Describe the issue
I just requested a new interim meeting for the OpenPGP working group. It will be a remote meeting starting at 2025-02-10T11:00:00Z. I asked the system to create a meetecho room.
Because of my own confusion about the UX, i failed to include an agenda in the initial meeting request.
I went back to edit the request (at https://datatracker.ietf.org/meeting/interim/request/interim-2025-openpgp-01/edit ), added the agenda, and hit "Submit". It appears to have saved my request, but it produced a warning (which i failed to record verbatim) about not having included the remote instructions in the request (maybe because the meetecho information hasn't been completed yet?).
I went back to re-edit the request to see whether i could reproduce it the warning, and now when i edit the request and submit, i don't get any such warning.
If you'd like me to try to replicate the problem with a phony meeting request so i can get a verbatim copy of the error message, please let me know and i'll do that.
Code of Conduct
The text was updated successfully, but these errors were encountered: