Should we improve our (internal) communication?
Hi all,
today ries (aka ftp-master) was down due to a scheduled maintenance activity.
Now, scheduled means programmed, and suddenly this question comes to
me: should the project be notified of such core activities? should we
only relay on #debian-devel irc channel topic to know this?
ries is not a barely used machine, it's the one of our fundamental
servers, and it went down without notification (to my knowledge, or at
least to a wide audience).
Other times, when I asked on irc why a given machine when down I often
have received a reply that sounded like "WTF you want? go and do
something else and don't bother us", not really encouraging, but I
moved along.
Now, I don't think that writing a 2 lines email with "Hey dudes,
tomorrow we're going to take ries (our beloved ftp-master) down due to
maintenance to improve the service - just take note of it" takes long
time, and it would have allowed developers, maintainers, and generally
all the "more involved" users of debian to know what's happening in
the infrastructure we all use.
There is also a mailing list created ad-hoc for such annoucements,
debian-infrastructure-announce, but it is barely used.
Should we improve how we communicate in the project? Shouldn't there
be more information on what's moving "behind the scenes"? It's just me
that would like to know it?
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: