From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Tue Jun 23 02:10:49 2020 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 4D5AF3571C2; Tue, 23 Jun 2020 02:10:49 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id E07B435711D for ; Tue, 23 Jun 2020 02:10:48 +0200 (CEST) Received: by mail-qk1-f174.google.com with SMTP id j80so6007986qke.0 for ; Mon, 22 Jun 2020 17:10:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevelionel.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=OAe42LymtJx5jJ06GZCE5b2iT0M22TQ+f9++XO4dDUQ=; b=aolkg79C0FyPt5r9kysKw6W2D5wKUz8WP0Xgal5+8JV4XAri+DC9Hlvgw6KdEsiEKm aM7dwXsKB5u9MT5Vje8wLfu++5wMnOfMqTMeTtfXZrlqDruaMn3+zUddbkS8/geTxl/q w+hIoeOuubaTaflqTQlB6YrkMsqMWc39mR30w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=OAe42LymtJx5jJ06GZCE5b2iT0M22TQ+f9++XO4dDUQ=; b=oOP1btwWq8LBX+IGjBlifjf0fLnQ0yb49qxQ2XHCZ61Ec2mV47eVDnoRhVX7iSsKif faBjelFVdYydNCy8dWyUaW05u+zADrfWn931CgZC0nN+Z/g3g+dGYEWNPvdIXH+iukQu BOlJtAXx89ZyFzlnGvTz8syV4Uas8DuyCziOy/1AJ2uh0OzS9Au+P6HeF7qS4S+okp+6 zUaW3/RWVEyRpT4A16HTU3TuR+1Y7PP1Dw9yhCsIXCBgPMRQS1sUeC7Z3SG4jrpS/Zt7 pX5oDkvEEUdv0PYiiRaQdltHCl/sritrGkmsrlYdhikEgA573A4MoMzhA++/zocYDitR YT+g== X-Gm-Message-State: AOAM530i4CPTeoCStWHnmPSoO9tWmOjjHRkLD6BP3DrabOQ0nepPeOof 1xGD6N0vL0w3pQTUFaJ1YIDLwHJqN8V4hw== X-Google-Smtp-Source: ABdhPJxFTuh15rzW/8iW6mLvEsB5k1aO9jbQW+jYh0bns1IoVAemtyj6hIaP87yriXYjM2Fs4lH4tA== X-Received: by 2002:a37:6b47:: with SMTP id g68mr18301551qkc.190.1592871046770; Mon, 22 Jun 2020 17:10:46 -0700 (PDT) Received: from [192.168.1.12] ([71.161.209.175]) by smtp.gmail.com with ESMTPSA id x19sm1857052qtc.36.2020.06.22.17.10.45 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Jun 2020 17:10:46 -0700 (PDT) Subject: Re: [J3] (SC22WG5.6240) 2022 WG5 meeting To: WG5 List References: <20200619235913.262F1358B1A@www.open-std.org> <67861af9-2206-4559-8964-dd29728263f9@www.fastmail.com> From: Steve Lionel X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <62b96d2c-353a-4a53-156e-a6a3b7364288@stevelionel.com> Date: Mon, 22 Jun 2020 20:10:44 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <67861af9-2206-4559-8964-dd29728263f9@www.fastmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: owner-sc22wg5@open-std.org Precedence: bulk Some people in this thread are replying to the J3 list only, and some to BOTH J3 and WG5, which results in duplicates. Please pay attention when you reply. That said, there are two, somewhat separate issues being discussed here. I started by asking about potential hosts for the 2022 WG5 meeting. We have two proposals so far that fulfill the requirements for a WG5 meeting. (Van's suggestion of Pasadena is as a location only - he has said he is not able to provide the meeting rooms and other infrastructure a WG5 meeting requires, and as I've mentioned earlier we can't rely on a free room tossed in with a hotel block.) Most of us are familiar with both Berkeley and Mesa Labs, as they were the sites for the previous two NA WG5 meetings. Maybe someone can offer a site towards the East coast? (Tom discussed NASA sites - that would be nice.) Then a separate exchange started about meeting places for J3 when it is not joint with WG5. Some have expressed antipathy to Las Vegas for these, though I haven't spotted specific objections. I would ask those interested in alternative locations to get together with Dan and Jon (J3 Treasurer) to research sites elsewhere, identifying venues and gathering data on costs. As Bill has mentioned, Vegas has many advantages, but they're not unique. Among he many factors to consider is the typical weather in February and October, our usual J3 meeting months. It's not sufficient to name a favorite city and then rely on others to make it work. As nice as it is, the suggestion that NVidia could host multiple meetings is likely to be problematic for representatives of other vendors. WG5 met at IBM Canada once, and we were scheduled to meet at Cray's offices in Minneapolis this year, so vendor hosting is not unheard of, but I don't think we want to get in the habit of using any one vendor's facilities as an ongoing host. That said, if NVidia wants to put together a proposal for a WG5 meeting in 2022, we'd gladly look at that. Steve