Sounds like a tools sort of issue. Maybe they need a webform that opens a ticket for the reporter. That person can then check back in online for status. And on the backend the Ombudsteam can automatically
report on issues reported over time, current issues open, and issues closed by resolution type (e.g. no action taken, 1:1 coaching, removal from position), etc. On the other hand, I suspect the volume of issues is quite low and that may fail to justify this
sort of automation. JL From: ietf <ietf-bounces@xxxxxxxx> on behalf of Abdussalam Baryun <abdussalambaryun@xxxxxxxxx> Hi Alissa, I hope this ombudsteam procedure is working well with no issues. How does the procedure monitor the time/delay of respond/action? I remember in 2017, I send an email to its email and cc to one person's name mentioned in your email. I did
not get any reply (that email sent was ignored by both emails, and is still waiting for reply with very long delay), I noticed then that this ombudsteam is not working well as needed. Maybe there is a problem in implementation of rfc7776 or the procedure needs
to be update for better practice. IETF is about implementing procedures for best practices and for the community needs. Best Regards AB On Fri, Jan 11, 2019 at 7:36 PM IETF Chair <chair@xxxxxxxx> wrote:
|