> Date: Sun, 31 Aug 2025 12:52:24 -0400
> Cc: [email protected]
> From: Michael McMahon <[email protected]>
>
> One more thing, try to avoid CCing [email protected] or any of the
> addresses that point to one of our RT ticket queues from the mailing
> lists. I'm taking sysadmin out of the CC so reply to this thread to
> continue the conversation.
>
> RT does not understand mailing lists and creates individual tickets for
> each reply. Cleaning up the tickets from mailing lists within RT takes
> time away from our other tasks. It isn't all that much additional work
> in this instance, but it is a pattern that is easy enough to avoid and
> can become a bigger issue on large threads. I can automate cleaning up
> larger threads, but creating the automation takes time too.
I'm okay with that, but please, could someone publish some kind of
"official" instructions for reporting these problems as you'd prefer?
The reason I CC sysadmin and savannah-hackers-public is that I never
know whom to tell about each kind of problem. (And in the end the
person who fixed this problem was none of them.) Sending to the
mailman list is an exercise in futility, and even the two addresses I
used didn't yield any response until _after_ the problem was solved.
There are 4 kinds of connectivity problems I faced over the past
years:
. gnu.org is generally inaccessible even to ping
. problems with Git and other VCSes on savannah (slow operation,
refusal of connections etc.)
. problems with lists.gnu.org (delivery or archives)
. email delivery via fencepost
Would it be possible to have specific instructions for each of these
situations (and others if there are any)? While at that, could
someone clarify which problems _should_ be sent to sysadmin for
handling via RT? Bonus points for having designated people of
reasonable availability who could at least reply that the problem is
known and will be looked at when possible.
TIA
