This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--RScac0JCarjkRCOecR9uAXUUEeRIuc0um
Content-Type: multipart/mixed; boundary="2ydDOzftFl8o2sOiemWiAZiluQhDgNFVb";
 protected-headers="v1"
From: Kevin Fenzi <kevin@scrye.com>
To: Fedora Infrastructure <infrastructure@lists.fedoraproject.org>
Message-ID: <26f86c4d-f2a1-ff1f-7095-5686f89f3cf7@scrye.com>
Subject: IRC oncall

--2ydDOzftFl8o2sOiemWiAZiluQhDgNFVb
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Greetings everyone.

As those of you who frequent IRC probably already know, we are trying
out having a Fedora Infrastructure "oncall" person for IRC
reuqets/queries/pings. You can find out who this is by asking zodbot:

zodbot: oncall
smooge (Stephen Smoogen) is oncall. If I do not respond please file a tic=
ket

and then we would really appreciate it if you directed your IRC ping to
the nick listed in oncall or (as the reply says) just file a ticket.

Why are we doing this? Well, there are 4 of us who are full time paid
sysadmin/ops folks for Fedora Infrastructure and we were finding that a
large portion of time for everyone was being taken up by IRC interrupts.
Sometimes interrupting multiple people for non urgent tasks. We could of
course just ignore IRC, but that prevents us from handling urgent
interrupts where we do want to look at something quickly. Additionally,
when the oncall person doesn't know how to solve or handle some issue,
they can talk to whoever does know and learn how to do it and document it=
=2E

With this setup, the oncall person can plan on watching IRC and everyone
else can focus on tasks that require more concentration.

If your issue is not time sensitive or urgent, do also just consider
filing a ticket and we will triage it and work it as soon as we are able.=


Thanks in advance for helping us out here.

kevin


--2ydDOzftFl8o2sOiemWiAZiluQhDgNFVb--

--RScac0JCarjkRCOecR9uAXUUEeRIuc0um
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEESz7rprBJHpbnMnrQSzew2A/7u14FAlr5+csACgkQSzew2A/7
u17MGA//RvfjLU/FdhjD82J1wJH5Vn4eBhXQRDo5v0bSdZXpxmMuHl2irEF1BoFn
euW2DOgszSh6K9b7ha8Lx0O+iCtUxKr/DJd9HIURckpyvgIKiWa7bV+Ud3MELGP6
2cPyYnQD2g9cL0dXsdiAZaeDxu4DdJKSvxlYHDz+zJ980PKIU6QxLPtsP7bKVrsU
x5njM7Twj/L6HnNte43Nl4nau1WGfY1TCBaki3XIEF2oX/7f0H1O6yxg5MGVeWCt
yKa4pSaxt02SnSFL3MfIG2eLgFT2FW9Hec10yrbWKQFwlBM+DjbHAJWNl1Y8KQdT
UrjGqBG6EPW8BQ/W/fTgIIw7Lc3vmeOFRWIXw0colWU9HvF/LQV8WbdGvROQoY1i
crWlNqiPwFIO/sr3CHvhyB6pxmNcAwNGzZlFKLzSXA4vD+w5JZyxj2wGQpsJimEi
PWPOv90Or08AZT8NpALVggRCdSP8gLjX5vvWnYZuFustU+BetBxetUsMwi4FqG7h
SC+Q0JcV96ETmZDeXmjA8RJUeb8JkmDxvVH9346vONSdMBTXyh5SkMHaRaj0KLMy
1RuSdHS4QXMWUDayFS2uG1OZBhEt77cdkbD87yLQj8VTwRhh/iwXJxI4dYjAi2aU
lfOXOJOPlrfhE3msJbDrJwSPp7O8/7Jp3TrdhZTVrF5XppkVa80=
=Dohy
-----END PGP SIGNATURE-----

--RScac0JCarjkRCOecR9uAXUUEeRIuc0um--