Responsibility for mail server, impact on Subversion



Hi all,

A number of people have suggested that it would be irresponsible to do the
Subversion migration while our mail infrastructure is in the terrible state
that it is. I strongly agree... and suggest that we commit to delaying the
Subversion migration if the mail infrastructure is not functioning reliably
by Monday. As unfortunate as it would be to delay, we can not responsibly
expect our users to cope with such a change without fully functioning mail
services for support and co-ordination.

To back this up, I would like to own the responsibility for getting our mail
services back up and running reliably. This problem needs a clear owner, not
fresh layers of temporary fixes, trial and error experiments and incomplete
analysis. *No* changes should be made without confirmation, unless a serious
emergency change is required in which case you should follow up to this mail
both on list and directly to my address. This means mail server config on
all our machines... and (!!!) firewall configuration related to mail server
functions.

This will allow Ross (and perhaps others, if he needs them) to focus 100% on
preparing for and documenting the Subversion migration, which is *extremely*
important to get right, while ensuring that we do not make more mistakes as
we attempt to fix the mail server infrastructure.

Thanks,

- Jeff

-- 
linux.conf.au 2007: Sydney, Australia           http://lca2007.linux.org.au/
 
           What do you get when you cross a web server and a hen?
                                  Apoache.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]