IETF Logo Mail Archive

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

Alissa Cooper <alissa@cooperw.in> Thu, 06 June 2019 06:49 UTC

Return-Path: <alissa@cooperw.in>
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 5C270120182 for <tools-development@ietfa.amsl.com>; Wed, 5 Jun 2019 23:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=vSfm+X4u; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aIHdmRFR
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 3jrSe0Iu5U1w for <tools-development@ietfa.amsl.com>; Wed, 5 Jun 2019 23:49:31 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84BA1200F7 for <tools-development@ietf.org>; Wed, 5 Jun 2019 23:49:30 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id EC6DD222CE; Thu, 6 Jun 2019 02:49:29 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 06 Jun 2019 02:49:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=P 7tlKHfZV9xQFf6hAwBCTtKKIXzqTGsMSh55T/1ktnY=; b=vSfm+X4uI2fS4SYPG uVv9H6OoVXZhfyk/bVU9zeKgxWem/b7K5qtve+aDJ9a8uluVD2JNQ/Ep+3I6h5dd fGUTqtUm1IqvCN2I+E47w+HO/6m7iQ6Uu/WPjIdA4kCZ3QAE1XNwHS1tHChcbGnu fytYByc7oB7N40oKCNMAlhRb1MUDhTYwbgsM9/N/7pWEf1Okj1PnOsCOG5oVNNUs mh9SO94En2aKDyB8XmU90hORAwF32Pw5f59PFmNt2nt7xh+5Lw2HeMtNir4B5bO9 tbXVeVwDqkCQPjXpMVkMH8HbMcaZ0cZ7Enw0CEg6Lh0PAMuOfLvWCzFdyeB4CICd y1TjA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=P7tlKHfZV9xQFf6hAwBCTtKKIXzqTGsMSh55T/1kt nY=; b=aIHdmRFR0K4v//+pHaQM8i7EOs5tEiqgAR84cYmw2ARbjlhkSctEXJnL4 8oprPsuPP9l8lHtFNOKK3B+fMG0ZxfN2pIjpfW9Ea6GfZpSb7GBAcSAt9Ytua/h0 6YtsHkChWkW1JN8l51rLEnZkRxA+HBDePxQ+qTwZxvS/YQpzuh3/AuHrdUrdyFru 62OoZ8gH+ioPfsYhdTfyI5llVcWa/qAPGYyCqVEBAUlaf3X4cUBW4y4hJMgJ7KYE KGIlotAaMDlyZd2NVembcrYGPbKRkxegBYbkOBQjBzR/KfswUrdZwfMody1hUSV7 LTB2GlK2aQuUYCAIkZ4kKV1QZSI/g==
X-ME-Sender: <xms:ebf4XOQyEe2QdFmhlTRvvR6XWqWeajA-BRLVN2ZDplgcap_89ySBYg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegfedgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhi shhsrgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomh grihhnpehivghtfhdrohhrghdpshhushhtrghinhhivghtfhdrohhrghenucfkphepudej fedrfeekrdduudejrdekkeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrse gtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:ebf4XJCMOhVBliEBNsPRTmgANOu-P-e135EhbcXIylqAqMgrrSUShg> <xmx:ebf4XNjYivFfj_VNGelbAjVyt8vhDhpjBIDphPDIcB2nuIBYQmAP0Q> <xmx:ebf4XCNaWQIGLvSi5zJpsAL2LSMKNAQa6v5nFMdQr0-gzK9Le9171Q> <xmx:ebf4XI-IJjgsGszl1iglmr0JROvnkulEi_JLkEh4ixhXOWedPFNoBQ>
Received: from rtp-vpn5-43.cisco.com (unknown [173.38.117.88]) by mail.messagingengine.com (Postfix) with ESMTPA id AA06280065; Thu, 6 Jun 2019 02:49:28 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <17C1710B-122B-46E6-8A51-32EC8DDDE0ED@vigilsec.com>
Date: Thu, 06 Jun 2019 08:49:29 +0200
Cc: Robert Sparks <rjsparks@nostrum.com>, IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8DEDD044-46C8-4F13-89D5-0F6DF3BB7975@cooperw.in>
References: <AE18154F-E974-4F18-BD0A-25882607C334@vigilsec.com> <0dd6a9a9-4ba0-4d2b-7fd6-8fb4426a42f4@nostrum.com> <17C1710B-122B-46E6-8A51-32EC8DDDE0ED@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/Lp4mapdNp7pMxS06Qcah08bMaVY>
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: Thu, 06 Jun 2019 06:49:34 -0000

There is discussion in the LLC Board about taking the site down altogether, so I would suggest that folks hold off on making plans for it for a bit.

Alissa

> On Jun 5, 2019, at 10:40 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> Greg Wood suggested that the site could be could be restructured to remove the email address altogether.  However, we need to have SustainIETF@isoc.org forwarded to some IETF email address, and of course, someone needs to be responsible or reading the traffic that comes there.
> 
> Russ
> 
>> On Jun 5, 2019, at 4:22 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>> 
>> 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