Re: Making YouTube videos work better for IETF/IRTF participants
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Sat, 31 July 2021 18:56 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5213A1559 for <wgchairs@ietfa.amsl.com>; Sat, 31 Jul 2021 11:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HQXxb5y_22hS for <wgchairs@ietfa.amsl.com>; Sat, 31 Jul 2021 11:56:49 -0700 (PDT)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9232D3A155A for <wgchairs@ietf.org>; Sat, 31 Jul 2021 11:56:49 -0700 (PDT)
Received: by mail-vk1-xa30.google.com with SMTP id d16so2770599vkp.4 for <wgchairs@ietf.org>; Sat, 31 Jul 2021 11:56:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=epgZP+Bx/W5f0ZLtM+lrmk7k3EO8mArES9oGTgwyr6M=; b=UusymPD0nDDy7GN2s4i+tG22KLDs6aV41MJDPYvRCe0auJ8dud19i2TU4H5iGJWr0j D9l75f/qx7MA38I9WbZAbe5ETUu2tF3yHZSuYdldSySX44dFf+4gSPA7s8Xmz2RX4yfZ hmAsvzMPGlTBo0VQXtOELDtCTnG0Nkre5eT7Rd6HAEhfQ6m48n6TDIRV68SrGI3exZrr GU9bnX1bz5kv2frurV2waOLGX1z+prkhAPKiY1dz6kYTA3a/KMLx04EUsKCpGOSlzoSs Gsgen3/PWHu1wqKcnHIibnNklxio1+Q6bvOlJ83OWhSQzpUraUu2D1GwxVN3s7c+vfUr 04KQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=epgZP+Bx/W5f0ZLtM+lrmk7k3EO8mArES9oGTgwyr6M=; b=qNKEyuLYgmKsZtTC2O23GLXKUBuANFF4P2HMHfbRKhlGtIyxdlbzDGvML6wCod1ipo zr7i1z1aAPfDsUafYvkLCeSTtzdjXKOsEDSWtzt0eNxrefuIZx4XDFegpMcTbvCf4wkx tuk8CsOwV3SAgLgIu+gpIqq0FKEwYqLl+fXxjNbeeG/RQ/j5tDHiom4kUduWZ5zKqZ1o jcFCuS6qC3PwT+9GPcTiTxIZIfvsNIESsGQBVnk8N1+ejIu54wC9uuagVPqPFvHjlD9Q T9rDr+QfOmvd+sAhGq3J+2VNceJwSCrMWTu1CAS/FufaNQgiq8CSrdeqOvqphxNlczk/ UZLQ==
X-Gm-Message-State: AOAM530Iu7IzilBJn9swoXEGB0c8ncGBIVJ27NvHeAFhRoGk/viha6EL IeBpIBQqgnKhdEqvfd3fgEIR6Wh8haPXmspqiKI=
X-Google-Smtp-Source: ABdhPJxH935jV6mE7XE6waS5jal2/1ebc8F1A1srEGNoCsrMK57vGvFLcquQo0cw16KnVEgofbNh+Jqbzv+knacQRAI=
X-Received: by 2002:a05:6122:147:: with SMTP id r7mr5543693vko.16.1627757807049; Sat, 31 Jul 2021 11:56:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dUj_2LvPMnDc3X+4zq5g=P1sOvSj46ng6hQM0JJrWfwA@mail.gmail.com> <SJ0PR02MB78537272DE438DDA2927CDE2D3ED9@SJ0PR02MB7853.namprd02.prod.outlook.com> <CAKcm_gMWOa7txtYu4pT74tm4n92h93-Gi7Z67Hshh88Xd16zww@mail.gmail.com>
In-Reply-To: <CAKcm_gMWOa7txtYu4pT74tm4n92h93-Gi7Z67Hshh88Xd16zww@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 31 Jul 2021 13:56:20 -0500
Message-ID: <CAKKJt-cBp+QCs4BP7=HZjCaXr89NuFNz+UnRkO0NixJzwBfOTg@mail.gmail.com>
Subject: Re: Making YouTube videos work better for IETF/IRTF participants
To: Ian Swett <ianswett@google.com>
Cc: "MORTON JR., AL" <acmorton@att.com>, WG Chairs <wgchairs@ietf.org>, "irsg@irtf.org Steering Group" <irsg@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000dea4f005c86fe5e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/jp1xiSscrUhaVEvbe_KK41lJYOg>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jul 2021 18:56:55 -0000
Hi, Ian, On Sat, Jul 31, 2021 at 10:48 AM Ian Swett <ianswett@google.com> wrote: > I think this is a good suggestion. > > I tried searching for 'ietf110 MASQUE' and 'ietf100 quic', and the results > seemed quite good, but YMMV. > Yeah, there are things that work well. Adding a dash (the videos are actually tagged as something like "IETF111-QUIC-") doesn't seem to reduce false positives, and if you're searching for a meeting that didn't happen or hasn't been uploaded yet, it's REALLY hard to figure that out. I was searching for "IETF-111-MOPS" before it was uploaded, and I still got LOTS of matches 😀 But fixing this for IETF and IRTF people to find things quickly, easily, unambiguously, and "where we should already be looking for related information" seems like a better plan than figuring out how a mutable matching algorithm works this week ... Best, Spencer > On Sat, Jul 31, 2021 at 10:54 AM MORTON JR., AL <acmorton@att.com> wrote: > >> Spence wrote: >> >> Would your working group/research group participants find making >> your YouTube videos helpful? >> >> >> >> Sure, it can be very helpful to review the recording, >> >> >> >> and >> >> ...that searching for a specific video from a specific IETF meeting >> doesn't work super well. >> >> >> >> I’d rather not to search too long for resources, either. >> >> Al >> >> >> >> *From:* WGChairs <wgchairs-bounces@ietf.org> *On Behalf Of *Spencer >> Dawkins at IETF >> *Sent:* Saturday, July 31, 2021 10:31 AM >> *To:* WG Chairs <wgchairs@ietf.org>; irsg@irtf.org Steering Group < >> irsg@irtf.org> >> *Subject:* Making YouTube videos work better for IETF/IRTF participants >> >> >> >> I hope everyone had a lovely IETF 111, and rested up at least a little >> before starting to read IETF e-mail. >> >> >> >> So, full disclosure,I REALLY miss having MeetEcho posting archival videos >> that synchronized the chat with the speakers and slides, etc. but we're >> where we are now, so I'm going with that, and want to make a positive >> suggestion. >> >> >> >> Making our session videos available on YouTube is in many ways a good >> thing for making them accessible to the world, but my recent experience >> poking around at IETF videos on YouTube has been that searching for a >> specific video from a specific IETF meeting doesn't work super well. Feel >> free to try this, for past meetings of your own groups, and see what else >> pops up along the way. >> >> >> >> Rather than hoping that situation changes, I'm wondering if it's worth >> putting links to IETF meeting session YouTube videos in the datatracker for >> various groups under "Meetings", so I can "view all the past session videos >> for QUIC, in order" without having to wander through spurious matches with >> other videos, trying to remember if the group actually met at IETF 108, not >> knowing whether a video has been uploaded from a session earlier in the >> week, and stuff like that. >> >> >> >> Specifically, I'm thinking about requesting that we either add a "Meeting >> VIdeos" selection to pages like >> https://datatracker.ietf.org/wg/quic/meetings/ >> <https://urldefense.com/v3/__https:/datatracker.ietf.org/wg/quic/meetings/__;!!BhdT!yoI49bJgf1qpJSmPLsa1_oisx4DmSdxLVbkMKMxSaRspaLfQRULAJmcIeKRrmyY$>, >> or just include them as part of the "Meeting Materials" for each meeting, >> perhaps appearing with the agenda, minutes, and blue sheets at the top of >> pages like https://datatracker.ietf.org/meeting/111/session/quic >> <https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/111/session/quic__;!!BhdT!yoI49bJgf1qpJSmPLsa1_oisx4DmSdxLVbkMKMxSaRspaLfQRULAJmcIiqKfEds$> >> . >> >> >> >> Obviously, working group/research group co-chairs could add that to the >> minutes, if they remember to do that, and are in a part of the world where >> YouTube isn't blocked, but it would be better if that happened >> automagically(*) when the YouTube video is uploaded, so we could pretty >> much count on them being available. So, if I'm going to ask someone else to >> do work, I should start with the goal in mind. >> >> >> >> Would your working group/research group participants find making >> your YouTube videos helpful? >> >> >> >> Please share your thoughts, when you have a moment. >> >> >> >> Best, >> >> >> >> Spencer >> >> >> >> (*) I mean "automagically from the working group/research group chair >> perspective". I've had too many conversations with secretariat folk, Greg >> Woods, and tools team members to think that ANYTHING around here happens by >> accident 😀 >> >
- Making YouTube videos work better for IETF/IRTF p… Spencer Dawkins at IETF
- Re: Making YouTube videos work better for IETF/IR… Carsten Bormann
- RE: Making YouTube videos work better for IETF/IR… MORTON JR., AL
- Re: Making YouTube videos work better for IETF/IR… Ian Swett
- Re: Making YouTube videos work better for IETF/IR… Spencer Dawkins at IETF
- Re: Making YouTube videos work better for IETF/IR… Meetecho IETF support
- Re: Making YouTube videos work better for IETF/IR… Lucas Pardue
- Re: Making YouTube videos work better for IETF/IR… Toerless Eckert
- Re: Making YouTube videos work better for IETF/IR… Spencer Dawkins at IETF
- Re: Making YouTube videos work better for IETF/IR… Meetecho IETF support
- Re: Making YouTube videos work better for IETF/IR… Spencer Dawkins at IETF