Re: [codesprints] Prepare for the 114 Codesprint

Robert Sparks <rjsparks@nostrum.com> Thu, 21 July 2022 17:05 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5DEAC13C511 for <codesprints@ietfa.amsl.com>; Thu, 21 Jul 2022 10:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfcshko-3XTh for <codesprints@ietfa.amsl.com>; Thu, 21 Jul 2022 10:04:59 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45596C13C502 for <codesprints@ietf.org>; Thu, 21 Jul 2022 10:04:59 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 26LH4uwl023043 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <codesprints@ietf.org>; Thu, 21 Jul 2022 12:04:57 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1658423097; bh=dPc79PI/vDS0Qus67ab0xRf7axhMlC3Yyo/L4v/qRbI=; h=Date:Subject:To:References:From:In-Reply-To; b=nYIeBLjKn5q253XfeQ/oXpF+Yswdcg5Q+VEy/It6T4oh0vMsL4nFcQfn50+ksneo8 DwPRprZZSO+I+RWKmX3y+/GL0Bpw+BUHCtLwEnpAL1j97/0t0X/qwCfweqy+ActBCk TLwXbV1Kyvxvec9EQZqcIk3iXWvpkVFXWSfq/FTU=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <47b8b513-0b09-9493-e2d6-42d4cb7d66d0@nostrum.com>
Date: Thu, 21 Jul 2022 12:04:51 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: codesprints@ietf.org
References: <2aec5a1c-fb1d-a905-5ec7-24b5227ff1d0@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <2aec5a1c-fb1d-a905-5ec7-24b5227ff1d0@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/MfqpHUQ-f0SKoCSz8PI__Oi1bc4>
Subject: Re: [codesprints] Prepare for the 114 Codesprint
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codesprints/>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2022 17:05:03 -0000

I meant to also remind you to be sure to sync your fork of the 
datatracker with ietf-tools/datatracker so that you have the most recent 
commits to main.

On 7/21/22 12:02 PM, Robert Sparks wrote:
> Anyone planning to help at the codesprint at 114 (note that we'll be 
> in the same space as the hackathon this time):
>
> If you haven't been keeping your dev environment in sync with the 
> changes in main, a _lot_ has changed with the development containers, 
> and you will want to spend the time to build them fresh.
>
> Get a fresh clone of main from your fork of the datatracker, then
>
> (cd docker; ./cleanall)
>
> should be sufficient, though I've sometimes found that following that 
> with
>
> docker volume prune
>
> helps.
>
> then follow the instructions at the readme to start the dev 
> environment either from the command line or in vscode. See 
> https://github.com/ietf-tools/datatracker/blob/main/docker/README.md
>
> If you are on a slow net connection or an older machine, this will 
> take some time - possibly over an hour (it takes about 15m on an M1 
> with lots of memory), so it would be good to do this before you get to 
> the sprint this Saturday.
>
> We have a notes page at https://notes.ietf.org/notes-ietf-114-tools - 
> if you are planning to sprint and aren't already listed on that page, 
> please add yourself.
>
> See you Saturday!
>
> RjS
>
>
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints