Re: [vmeet] what's been working/failed/tried in hubs?

Alia Atlas <akatlas@gmail.com> Tue, 11 October 2016 13:15 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31421129480 for <vmeet@ietfa.amsl.com>; Tue, 11 Oct 2016 06:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 J-u3gGyId6JL for <vmeet@ietfa.amsl.com>; Tue, 11 Oct 2016 06:15:11 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 3118C12946E for <vmeet@ietf.org>; Tue, 11 Oct 2016 06:15:11 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id t192so12205537ywf.0 for <vmeet@ietf.org>; Tue, 11 Oct 2016 06:15:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CfV/qEvy2gA6vExDvMMxI4ZdWowIU7bNTWesYBZpwKU=; b=EFDlHkePLlH3nmtt1Y7zvCzYj0PeZXiY1tL/W4G/db1FnO+onY9R9ot8sET8BRDmN+ TrnSl4+NnVsem9PTfNAGoW5Z2FlOUfJdBbH5WgCdK/S6rhv5Jnd2nr8OjvoM5PBsw+FF 3VhRcRobSNsXck78PKkjfzP7WNF/FiyUBDbGfs8DUnayfBx5k4XlqY1DDp32WWlXY0ol jNucVsCB211I33mde+i0H4bz4PrGU/aKxOa1iqGcYdLDnzxx9rPL/rzS0OX/x3izUWSU 4Xqm19/5gN9urcrAR5nQ3Iz8AdBSJUshbzMB4NverzrKB8qh7WkPorrTTvHOJGsnrbVP eYTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CfV/qEvy2gA6vExDvMMxI4ZdWowIU7bNTWesYBZpwKU=; b=edV1BfwbnIl0VzQI0muk7Ps2Iya8YOuES7tcoqx3RPj4O6mjJqRTWtZJVdy4kFIu7/ OYscRkQriGZmcU2Emkwwxe5gQBle97jSBpR6Gc8/4YijdOnDq2MwkSo40WaWwBaVVky4 +5Zk9mGVKt6lYGGbt/eI+/I6o5NhhWJO0jfwepTZAEh0ZZixMWpUix5byeiiqXBseerR ZQ9buhQ9XdbZHFJcZp40Cwyn9o/3EW8f4sSQaARU1jYttKcltgim3yQ6BdjwfDAfikqw 9KPhFsI/pip8Ah8DwlbI29Ck85cVzMHaL/4qUoZjzitagZ8epgOpyW9vB4DPpBrmw1Pw lFWQ==
X-Gm-Message-State: AA6/9RniEfrhu16ICECZhNvrf43k7dSvOIozEPMpoymV79ev/48AePl6ck7JXS+hKb6UbeMpfNTbUq/VPmWYPQ==
X-Received: by 10.13.203.80 with SMTP id n77mr3163413ywd.220.1476191710286; Tue, 11 Oct 2016 06:15:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.56.133 with HTTP; Tue, 11 Oct 2016 06:15:09 -0700 (PDT)
In-Reply-To: <BCD8FF11-6277-466F-B74E-8AF5939758ED@isoc.org>
References: <CAG4d1re1td4oaPpHMHn7Ka4OYT37B6QRsygM1uvWZhDTzqyJGA@mail.gmail.com> <BCD8FF11-6277-466F-B74E-8AF5939758ED@isoc.org>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 11 Oct 2016 09:15:09 -0400
Message-ID: <CAG4d1rfueX7puZ1kLnjD8hx1yD_AR8BXvoOgaODMi8TfwBczxQ@mail.gmail.com>
To: "Christian O'Flaherty" <oflaherty@isoc.org>
Content-Type: multipart/alternative; boundary=001a114829fc834864053e96aad4
Archived-At: <https://mailarchive.ietf.org/arch/msg/vmeet/sizovxh2gjKTnFlODwUQelAgbnc>
Cc: "juliao@braga.eti.br" <juliao@braga.eti.br>, "vmeet@ietf.org" <vmeet@ietf.org>
Subject: Re: [vmeet] what's been working/failed/tried in hubs?
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 13:15:14 -0000

Hi Christian, Dhruv, Vinayak, & all,

Interesting.  In Boston, we have tried doing some remote hubs during the
last 2 IETFs.  This has been primarily routing related WGs and hosted at
Juniper in Westford.   While they're public, I think most of the attendance
has been from Juniper folks, because they are there, hear about it more
easily, and are more interested.

In addition, we've had a couple get-togethers in Cambridge - one to
celebrate Scott Bradner's retirement and another social lunch.   We're
trying to pull together a meet-up with a few short technical presentations
and then potentially dinner afterwards.

In this area, we have a good number of experienced IETFers but reaching out
to pull new people in is more challenging.  It's also not completely clear
what will excite others enough to come to an event.  The social lunch did
have lively discussion, including of course IETF tech topics.

I'm thinking that focusing on remote hubs during IETF isn't as useful for
us, because a lot of the active folks are at IETF and the time-zone
differences are hard.

I'm also wondering about identifying/asking for community organizers to
focus on planning a few events (1 or 2 between IETFs) and think about how
to get the word out.

It sounds like this is a different approach, though very similar in some
ways of trying to add talks and interaction.

Thoughts?
Alia

On Fri, Oct 7, 2016 at 4:12 PM, Christian O'Flaherty <oflaherty@isoc.org>
wrote:

> Hi Alia,
>
> There’s a draft that will be updated soon with some experiences and
> recommendations.
>
> Some comments inline:
>
> > I am curious about how the various IETF Hubs have been doing?
> > What activities have you tried and found useful/successful/interesting?
>
> Hubs in Latin America have been diverse:
>         Some hubs were just a small gathering for remote WG session
> participation only.
>         Some hubs were meetings with an introduction/presentation and then
> the WG session (sometimes with local explanations and discussions in
> parallel)
>         Some had a previous introduction webinar to prepare participants
>         Some hubs were organized for IETF promotion and the WG session
> itself was less important (more local activities)
>         Sometimes (in Brazil) they were organized as remote "IETF
> meetings” were the students had a WG to attend in each slot.
>         Some hubs were co-located with other events (academia) were a
> meeting room had the remote WG session
>
> > What did you try that failed miserably?
>
> In some cases the hubs had as few as three or four participants… but I
> would not consider it a failure.
> There were hubs that failed because remote participation was impossible
> (low quality) and they did something else.
>
> > Do you have a community organizer (or group of folks) pushing the
> organization
> > of the activities and facilitating?
>
> Yes… there’s always an organizer / facilitator
>
> >   Do you have different people stepping up to pull things together?
>
> Yes… I’m including Juliao Braga from Brasil who is the main one in our
> region.
>
> >
> > What is your participation like?  Is it largely experienced IETFers?
> researchers & students? interested developers?
>
> We’ve been using them for IETF engagement so they’re usually not
> experienced IETFers, mostly students and professors, some network
> operators. I’m not aware of developers but some students can count as such.
>
> >
> > Personally, I'm brainstorming a bit about what might be useful to try in
> the Boston Hub and how much to push or encourage structure.  It feels like
> some can be quite useful.
>
> Please don’t consider our experiences as “best practice”. We do have
> completely different needs and objectives for remote hubs in our region.
>
> Christian
>
> >
> > Thanks,
> > Alia
> > _______________________________________________
> > NOTE WELL: This list operates according to
> > http://mipassoc.org/dkim/ietf-list-rules.html.
> > https://www.ietf.org/mailman/listinfo/vmeet
>
>