Re: [107attendees] Where the action is, at virtual meetings ...

Benjamin Kaduk <kaduk@mit.edu> Sun, 29 March 2020 20:54 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: 107attendees@ietfa.amsl.com
Delivered-To: 107attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7936E3A08A3; Sun, 29 Mar 2020 13:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 u-tesFrV8lb1; Sun, 29 Mar 2020 13:54:44 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0863E3A087E; Sun, 29 Mar 2020 13:54:43 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 02TKsbRQ005886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 29 Mar 2020 16:54:40 -0400
Date: Sun, 29 Mar 2020 13:54:37 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>
Cc: IETF <ietf@ietf.org>, 107attendees@ietf.org
Message-ID: <20200329205437.GS50174@kduck.mit.edu>
References: <CA+9_gVvSvdocYSsw-FEAFrAL8Fq--CQpRj2OFJfvUVx6PjBrTA@mail.gmail.com> <7316D61D-A962-4943-BF02-FC676D671219@icloud.com> <6c578ff5-2870-7b86-6590-7ab01f944376@htt-consult.com> <9F76E481-FAF1-4EB0-8F82-1CF296F99FBF@fugue.com> <6e19f35e-8da4-f63f-26d5-7b5e1be075fd@htt-consult.com> <9BFB58E6-2EE2-44C3-B04D-C45C21A4E99B@fugue.com> <57092354-ff42-91fc-08b5-546364af6b4e@htt-consult.com> <AFBA0AFD-EBFD-4F45-B3D8-B8B35C7D5C22@fugue.com> <24192.54005.771799.752970@fireball.acr.fi> <FC04F89A-9B0E-4319-ABFA-3C8F3048477C@bangj.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <FC04F89A-9B0E-4319-ABFA-3C8F3048477C@bangj.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/107attendees/H4tS-nFPtE8a8h65My94VVEkV4o>
Subject: Re: [107attendees] Where the action is, at virtual meetings ...
X-BeenThere: 107attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 107 attendees for official communication <107attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/107attendees>, <mailto:107attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/107attendees/>
List-Post: <mailto:107attendees@ietf.org>
List-Help: <mailto:107attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/107attendees>, <mailto:107attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Mar 2020 20:54:46 -0000

On Sun, Mar 29, 2020 at 01:38:54PM -0400, Tom Pusateri wrote:
> 
> For me, most of these solutions are missing searchable archives. This is built in to email. In the past, the IETF has published the jabber logs and I have written scripts to sync them with audio and slides. Slack limits history in most cases I’ve used it.

To be clear, the IETF still does publish the jabber logs, not just "in the
past": https://www.ietf.org/jabber/logs/

-Ben

> Any solution going forward should have:
> 
> 1. history is kept forever
> 2. easily searchable.
> 3. timestamps for synchronization
> 4. source of message can be correlated to IETF person database
> 5. archive available in standard format (no HTML screen scraping please. Yeah, I know, Beautiful Soup is amazing, but I have better things to do.)
> 
> Tom
> 
> 
> 
> 
>