Re: [codesprints] Codesprint at IETF 115.

Robert Sparks <rjsparks@nostrum.com> Wed, 26 October 2022 19:20 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 67CCEC14F72C; Wed, 26 Oct 2022 12:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.29
X-Spam-Level:
X-Spam-Status: No, score=-1.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.398, NICE_REPLY_A=-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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 QVAC590ReLpW; Wed, 26 Oct 2022 12:20:41 -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 CC5CFC14F6EC; Wed, 26 Oct 2022 12:20:41 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 29QJKenV034320 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 26 Oct 2022 14:20:40 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1666812041; bh=3dS5fFxPhAnM5oTNu7mmgrjfpfE33qc0A2dAKTU1x18=; h=Date:Subject:From:To:References:In-Reply-To; b=rmMEivB+BuVRUg4kxNEIpQBe0avURnh3Ov0e6HzcQI8OOCOwrv4pNb9fHfWXS6AtM EHcr4WCw4MMh1Yzoobjnh+f9zzKdeKqprvQemzZuXHmSDgsFslCwaYiONycrs7tWWO VZqVCfI9e7ohcOMDIgDzh90SNMTe3OkAUWzlcvSc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <0fdc2d6a-ba59-c0e4-0c7c-414e95f9109c@nostrum.com>
Date: Wed, 26 Oct 2022 14:20:35 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.3.3
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>, IETF Codesprints <codesprints@ietf.org>
References: <af946d4c-1184-ac5d-41de-70bbffd0eb57@nostrum.com> <3da7452d-c9aa-9955-7e8b-70f7a0c6e0f2@nostrum.com>
In-Reply-To: <3da7452d-c9aa-9955-7e8b-70f7a0c6e0f2@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/abLp7WX_tab6yINmSEUtS3rXki0>
Subject: Re: [codesprints] Codesprint at IETF 115.
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: Wed, 26 Oct 2022 19:20:45 -0000

If you're planning to sprint but haven't warmed up your development 
environment yet, please take some time now to do so.

Remember to switch to the feat/tzaware branch and rebuild your 
containers. Fetch a fresh copy of the database. Leave time this week and 
early next for us to help you work through any issues you might run into 
so that time is not lost on the Sprint Saturday.

If dataracker development is all you are using docker for, then I suggest:
```
(cd docker; ./cleanall); docker volume prune
```
to make sure you have new images once your at the head of feat/tzaware.

If you are using docker for other things, read the cleanall script and 
take a more selective approach to not disrupt your other activities.

RjS

p.s. I will be slow to respond to messages Oct 31, but other sprinters 
can help with any problems reported during that time.


On 10/13/22 4:59 PM, Robert Sparks wrote:
> If you'll be joining us at the codesprint in London, please add yourself 
> to the table at https://notes.ietf.org/notes-ietf-115-tools#.
> 
> We're starting to collect the issues we hope people can work on, but of 
> course, anyone is welcome to work on whatever is bothering them the most.
> 
> If you have something that you would like to take on early, let me know 
> and I'll add it to https://github.com/orgs/ietf-tools/projects/7/views/1.
> 
> Please read through what's below, and make sure that you are ready to 
> work on the /feat/tzaware branch.
> 
> I hope to see you in London!
> 
> RjS
> 
> On 9/27/22 10:13 AM, Robert Sparks wrote:
>> All -
>>
>> If you can participate in the Codesprint at IETF115, please take some 
>> time in the next week or so to bring your development environment up 
>> to current and switch it to the /feat/tzaware branch. My plan is to 
>> have all contributions at the sprint come into that branch (we expect 
>> to deploy it right after IETF 115).
>>
>> Instructions for setting your environment up (which is even easier now 
>> than it was at IETF 114) are at 
>> https://github.com/ietf-tools/datatracker/blob/main/docker/README.md. 
>> At the step at the beginning replace `git checkout main` with `git 
>> checkout feat/tzaware` for this sprint.
>>
>> RjS
>>