[FFmpeg-devel] release feedback

[Jethro Walters]

--- On Sun, 15/3/09, Michael Niedermayer <michaelni at gmx.at> wrote:

> From: Michael Niedermayer <michaelni at gmx.at>
> Subject: Re: [FFmpeg-devel] release feedback
> To: "FFmpeg development discussions and patches" <ffmpeg-devel at mplayerhq.hu>
> Date: Sunday, 15 March, 2009, 2:02 AM
> On Sun, Mar 15, 2009 at 01:32:38AM +0000, Jethro Walters wrote:
> > 
> > --- On Sun, 15/3/09, Michael Niedermayer <michaelni at gmx.at> wrote:
> > 
> > > From: Michael Niedermayer <michaelni at gmx.at>
> > > Subject: Re: [FFmpeg-devel] release feedback
> > > To: "FFmpeg development discussions and patches" <ffmpeg-devel at mplayerhq.hu>
> > > Date: Sunday, 15 March, 2009, 12:36 AM
> > > On Sat, Mar 14, 2009 at 10:22:53PM +0000, Robert Swain
> > > wrote:
> > > > On 14/3/09 23:20, compn wrote:
> > > > > On Sat, 14 Mar 2009 21:16:32 +0000, Robert Swain
> > > wrote:
> > > [...]
> > > > > i know the roundup list has been mirrored on gmane since that first
> > > > > downtime. so i'm not sure what else can be done for that.
> > > > 
> > > > The other lists are on gmane aren't they? Are they actually mirrored 
> > > > there and synced back and forth with the lists on mphq? Do distributed 
> > > > mailing lists exist? ;)
> > > 
> > > usenet
> > 
> > Sorta related, but in the case of downtime on the mailing list, you could migrate current development chatter to an IRC channel.
> 
> or go bugfixing on roundup which is together with its ML on
> a different server.
> 
> Which brings me to underline a past comment of mine, avoid
> a single point of failure, be that a person or equipment.

Surely doing that just gives more chances of hardware failure? You spread the load, you spread the risk, but equally, the manpower has to be there to back it up and solve problems when they arise. You have it in one area and one person only needs to solve it. You have failure across a number of areas, more people are needed.