Re: [boost] boost.org https certificate expired 4 month ago

Subject: Re: [boost] boost.org https certificate expired 4 month ago
From: Michael Caisse (mcaisse-lists_at_[hidden])
Date: 2015-08-14 10:49:40

On 08/13/2015 11:51 PM, Vladimir Prus wrote:
> On 12-Aug-15 12:38 AM, Niall Douglas wrote:
>> On 11 Aug 2015 at 1:36, Klaim - Joël Lamotte wrote:
>>
>
>> We would move to new servers, but need root access to copy off all
>> the existing data. So we keep pinging emails, and hope one day the
>> person in question replies.
>
> How about starting a new server, configuring nginx to proxy to the
> current server by IP address, and changing DNS to point to the new server?
> SSL will be handled by the new server.

If this was just the webserver for the website it would be fine, but it 
is the trac server and that is creating some problems. We *will* have a 
solution. It will have to involve control in the end.

>
>> This is why we need a dedicated employed person to do this stuff,to
>> keep migration plans and plan upkeep so getting orphaned from access
>> never occurs in the first place, and even if it did there is a live
>> offsite backup configured using docker/drbd etc we can replicate
>> from. The steering committee can only authorise that spending if
>> there is consensus from boost-dev that someone should be employed to
>> do this stuff, until that happens this situation will keep recurring
>> into the future with no end in sight.
>
> Lots of open-source project manage to have a website without employing
> anybody. I think the problem is really access, not employment.
>

Agreed. We just need access. There are many people willing to do the work.

michael

-- 
Michael Caisse
ciere consulting
ciere.com