Re: [119all] Result of the IETF 119 Brisbane post-meeting survey
John C Klensin <john-ietf@jck.com> Tue, 16 April 2024 03:00 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DD4C14F6AF for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2024 20:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RNodZ7PiHjTz for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2024 20:00:17 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89B44C14F694 for <ietf@ietf.org>; Mon, 15 Apr 2024 20:00:17 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1rwZ3N-000DZy-Ik; Mon, 15 Apr 2024 23:00:13 -0400
Date: Mon, 15 Apr 2024 23:00:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Christian Hopps <chopps@chopps.org>, John Scudder <jgs@juniper.net>
cc: ietf@ietf.org
Subject: Re: [119all] Result of the IETF 119 Brisbane post-meeting survey
Message-ID: <7BCE2880B3840C19ADA97267@PSB>
In-Reply-To: <m2pluqi8g1.fsf@ja.int.chopps.org>
References: <DC6C12FF-601C-4180-9FD1-4A1589531113@ietf.org> <m2y19iinsy.fsf@ja.int.chopps.org> <B6F57D48-8E9E-409A-BD26-3706F102188B@ietf.org> <27F155AC-9B10-4FAD-ABE6-ACD79769B571@chopps.org> <1E1EF642-93B7-4245-B702-839B850AB369@ietf.org> <15323534-6E6F-4EC8-954B-9BB6207EDF4C@chopps.org> <86800871-EFAF-4394-BD2A-C7110F574228@juniper.net> <m2pluqi8g1.fsf@ja.int.chopps.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/67s_lXNx57tQP80PBQHySkLfj4o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2024 03:00:23 -0000
--On Monday, April 15, 2024 18:07 -0400 Christian Hopps <chopps@chopps.org> wrote: > > John Scudder <jgs@juniper.net> writes: > >> Hi Chris, >> >> On Apr 14, 2024, at 7:23 AM, Christian Hopps <chopps@chopps.org> >> wrote: >>> forced/unwanted remote participation >> >> It occurs to me I don't know what you mean by this phase. >> Obviously, nobody is literally being forced to participate >> remotely. I guess you're probably talking about the responses to >> Q5 other than "it is my preferred way to participate"? > > Yes, from the survey: > > "For the third time, we asked people who participated remotely > (Q5), why they did and if they would have preferred to participate > onsite (Q5a). Once again, the major factor, cited by 75% of people, > was the lack funding to travel." Chris, John, Sequences like the above arewhy I keep arguing that one has to be very careful about how survey answers are interpreted and how much is read into them.. and often about exactly how questions are asked and what alternatives are given. The latter comes with the understanding that it is sometimes not possible to do better. For this case, and using myself as an example... While I'm an oddity, not least because I have not had organizational funding for IETF participation for years, I've participated remotely and have answered that question with "yes, I would have preferred to be onsite" and "lack of funding". Same answer for San Francisco, Prague, and Brisbane; little no information in the survey answer about the relative differences in costs to me or what secondary factors might have contributed to my deciding to not go and/or not ask for a fee waiver (a small fraction of the cost anyway). And, because some of those factors include what I consider sensitive information, if there had been detailed questions about them, I probably would not have answered. Maybe I'm unique in those ways, but I'd be really surprised. So, yes, the question is good to ask and the data are useful. And changes in the ratios of onsite to remote attendees or the percentage who respond "yes" are at least interesting and may give an indication of something to watch and think about. But drawing strong inferences from them -- especially when there is reason to suspect that the collection of people who respond to the survey are not a random or representative sample of the IETF community or even IETF meeting participants (and that completeness and responsiveness to answers to one question may be representative of different opportunity samples than those to another)-- is what my colleagues in the professional statistics and survey businesses consider highly suspect and questionable. In case someone wonders, yes, I could put on my long-shelved survey designer and statistician hat and make some suggestions about how to make questions like that and the answers more precisely and reliably interpretable. But doing so would come at the cost of a longer and more complicated survey instrument and questions that at least some would find more intrusive. Either or both might easily discourage responses and make the profiles of those who respond less representative than even the current questionnaire and process. No easy solutions to those problems. The closest one is that other than all of us become more careful about how much we read into the numbers. thanks, john
- Re: [119all] Result of the IETF 119 Brisbane post… Christian Hopps
- barista coffee at IETF 119 Jim Reid
- Re: [119all] Result of the IETF 119 Brisbane post… Jay Daley
- Re: [119all] Result of the IETF 119 Brisbane post… Christian Hopps
- Re: [119all] Result of the IETF 119 Brisbane post… Jay Daley
- Re: [119all] Result of the IETF 119 Brisbane post… Christian Hopps
- Re: [119all] Result of the IETF 119 Brisbane post… John Scudder
- Re: [119all] Result of the IETF 119 Brisbane post… Christian Hopps
- Re: [119all] Result of the IETF 119 Brisbane post… John C Klensin