Re: Meetecho available for interim meetings

Meetecho IETF support <> Tue, 06 July 2021 10:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CCBB13A2228 for <>; Tue, 6 Jul 2021 03:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.239
X-Spam-Status: No, score=-2.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.338, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DDRDuPsrD5pz for <>; Tue, 6 Jul 2021 03:27:57 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EFBE53A222C for <>; Tue, 6 Jul 2021 03:27:56 -0700 (PDT)
Received: from [] ([]) by Aruba Outgoing Smtp with ESMTPSA id 0iIymSSIifNGH0iIymaEGW; Tue, 06 Jul 2021 12:27:55 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=a1; t=1625567275; bh=bXYh5cNjh6mrxUMYrIsUSKzHslcLZEivHm3WMDcYtIo=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=SSUL5EKTKv4IoctKQYyTJd6+koBPz7KUmLmC4YtzGjtMspKAu0jbN/417lLuxi7Xo aHXzBE+jhRQXW1qtz01R+Xo4AjxTtKMfwGTsJ1aGU0R1gtTrchxJ/f4IHq202k3HZq T4ajFTE5Kd4Ngmh3L+pd7W3kUmsdCefQfw6aWLPMHonJzN8aDTgdgp9GiM5ZFIZP3/ eTbazjbhvTdo7k1cUCSpSZ8iE5SZt1k6OwPWmQqNsCZ+jkt41yUwOtek03dEbh3qiJ lOatC7W68shuGNgCdWqQV29ZOadt4DVsMFZEHFBijfX1SnYRH0gZIZU2wTjDgxV1Sg zn3oVkOf5+2iQ==
Subject: Re: Meetecho available for interim meetings
To: Christian Amsüss <>, Alexa Morris <>
Cc: Working Chairs <>
References: <> <>
From: Meetecho IETF support <>
Message-ID: <>
Date: Tue, 06 Jul 2021 12:27:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfIrgaHljZdzPXN1ssLqfAytvCOM1Fl1WRxUR9Dkcpig0J3/qJhKeRUZIqcc8y70E7MzHENDmlBwqpP7ZJUMWL3sn7BXzocEI3nejfDulioGDppvCQfot yw8eXEAzU31vYe82vQAwfv5JwFQajnAta1kdns0o0cHMtkKZy6oYU0+bGb4iTYq8Q1Pluh+Y6xaYRbx9XUasMvyidYU0NasuMq0tGv+fHspsx+zbjEjk5k+C
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Jul 2021 10:28:02 -0000

Hi Christian,

Il 02/07/21 12:31, Christian Amsüss ha scritto:
> Hello Alexa,
> On Fri, Apr 23, 2021 at 10:17:07AM -0700, Alexa Morris wrote:
>> We are pleased to inform you that Meetecho is now available for
>> interim meetings, design team sessions, etc.
> thanks, that has been working nicely for the last two CBOR meetings.
> The question of attendance recording came up in the latest: meetecho
> was used for virtual bluesheets in the last virtual IETFs, so does the
> interim version record attendance as well?

attendance data is collected for interims as well. I've verified that 
the same API we use to post bluesheets to Datatracker also works for 
interims. So I can definitely generate and post them if I'm asked to do so.

> In that case, we could do away with the manual attendance in the
> minutes. (Although from a chair perspective, that's a great opportunity
> for everyone to ensure they can write in the minutes, maybe that
> enhances participation).
> Also if so, does it distinguish between Jabber users and those that join
> via meetecho? (We have a few lurkers on the CBOR Jabber channel, which
> is not a bad thing, but I wouldn't count them as present unless they
> interact).

Jabber-only participants are not included in the bluesheets. Only people 
who log in via their Datatracker credentials are.


> BR
> Christian