IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Transition of sustainietf.org to IETF control

Robert Sparks <rjsparks@nostrum.com> Wed, 05 June 2019 20:22 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 629F112014B for <tools-development@ietfa.amsl.com>; Wed, 5 Jun 2019 13:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dlwIG9PxiYvR for <tools-development@ietfa.amsl.com>; Wed, 5 Jun 2019 13:22:15 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EF3C120043 for <tools-development@ietf.org>; Wed, 5 Jun 2019 13:22:15 -0700 (PDT)
Received: from unescapeable.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x55KMDXX030069 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <tools-development@ietf.org>; Wed, 5 Jun 2019 15:22:14 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1559766134; bh=CuplMLDwGGDgD6YDYc2QARSzoc2lwxzQgFBclwuubyQ=; h=Subject:To:References:From:Date:In-Reply-To; b=OWoU1k7UiJvGayfJ8YAoasLvVjOnN4QMgIK8pUzAHuJuxId9W4w5RrBSpIlt6xia6 0q+Jc16H6UL35YNU8c2EwUq1WG48XZJ23B8NmUjt76kiP3xSC6GBkqD/U0vLo3rcGK bKhYDW2JACDXBoBhb6JLXBhCqMG6lTfSKoR+leEk=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unescapeable.local
To: tools-development@ietf.org
References: <AE18154F-E974-4F18-BD0A-25882607C334@vigilsec.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <0dd6a9a9-4ba0-4d2b-7fd6-8fb4426a42f4@nostrum.com>
Date: Wed, 05 Jun 2019 15:22:13 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <AE18154F-E974-4F18-BD0A-25882607C334@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/TBqrkQgqol7dTjGQyLCmsErTKvY>
Subject: Re: [TOOLS-DEVELOPMENT] Transition of sustainietf.org to IETF control
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 20:22:17 -0000

Yes, if we take this, I strongly suggest putting it in a container, with 
its database also containerized. If it is just wordpress (that is, 
nobody's done anything special), all we'd really need is a copy of the 
database (IIRC, wordpress keeps its static content (like photos) in that 
database).

I think whoever is supposed to manage the content (see e.g. the "Donor 
Wall" at the bottom of the page) should get some training from whoever's 
been doing that at ISOC so far.

You're thinking ISOC would forward sustainietf@isoc.org to whatever 
@ietf.org address we created? It seems to me that this will have to land 
on a person who can manage taking a donation. Until the LLC appoints 
someone else, I think that has to be the executive director, no?

RjS


On 6/5/19 2:57 PM, Russ Housley wrote:
> Dear Tools Team:
>
> The IETF LLC is working on transferring control of the IETF Endowment bank accounts from ISOC to the IETF, a process which should be completed on June 28. As a result, the related website and domain (sustainietf.org) need to be transferred to IETF.
>
> I have asked Glen to work with ISOC to get the domain name transferred to the IETF Trust.
>
> The web site is a WordPress-driven site. I am unaware of any any associated source control.
>
> In addition, the site points people to SustainIETF@isoc.org, so we will need to create a new mailbox for that.  I do not yet understand who will read the mail sent there, so I do not have a suggest way forward yet.
>
> Is this a candidate for a new container?
>
> Russ
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

v2.23.0 | Report a Bug | By Email