Re: [Manycouches] DOGFOOD Virtual BoF

"Mukom Akong T." <mukom.tamon@gmail.com> Thu, 18 April 2019 02:41 UTC

Return-Path: <mukom.tamon@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E86C4120158 for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 19:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001] 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 9d7tNQbFPl2i for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 19:40:58 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 2193C120088 for <manycouches@ietf.org>; Wed, 17 Apr 2019 19:40:58 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id u15so436116otq.10 for <manycouches@ietf.org>; Wed, 17 Apr 2019 19:40:58 -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=UCEmts5fOrHghzsfACO4HWVX9dJpOOYra0CssnFeuxg=; b=NsA2O3u39DRFf12z7nH6UpSwb7Qs61CxAnmeByVaN3NFFxpYFWWU8a9wIXh0b6KG/I CIEnVl03QD3qgd0ORgCnyV0X7MFIibsrrtDbAWmPuvDo3vhD4eAewOE9UcSOIfC4XdKx wM8vbXX9E5rauWC6wdd8Zm/v6tNFKq8gTQ5S7yRKfXUv6/yyuvhinlZ7yhckE9he94o6 YT2DKVxp4Nu183eXRSKVV3ZTC7oYWtzIeX/PC0El8cstwccsotTeUL1VxL7Cmen4PmyB U5DxmuoJqJO/AyWFrBZqXRN5vmkbMR/ysq3RT+fnLuGyrfGtbVrBaP8MkTFx3Jh47nwM yAQQ==
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=UCEmts5fOrHghzsfACO4HWVX9dJpOOYra0CssnFeuxg=; b=gv4/yVnV+EVlAQgEtm4kN9t7Clky92Yfj6C7/qgRZypL2KAf8/N14Wb8mzYkDLeIQx dmmWMpx2gDdCBT8y1NKlo1xsTQIq8KaWwJ4p0eY3J2wXwFClvOS+y9aHu2HT8JrX3lax /80fPVueGEPYi3/3SDaLjmIIWb5ZXkOO2v+EDm9TdZ8H8EZMYOtXkwB7kvnXvE7kFsKB ICQcBG44Xi2i7w/u+Fo/rFfkcin3r11sDniJMicSWGmajG8oavAp1P7HLy6pXy46rSw8 hry+fhN5UGL2Ud8Yyoz6yqiVNnIzOhOAoqeaTzPbXlx1kQzv9rdMH4OySU2Pw3GY9bvN +aSg==
X-Gm-Message-State: APjAAAWj3lb9AlG+QGuvPvgRUd7MKkSMbyJorjjF/LUuxHsDqJn65DGs i4Qdsr6oSpmrbUBQyUpcIy6fuqmved7kThAFMpE=
X-Google-Smtp-Source: APXvYqw4OsMFyOH631ujz+HDwp/Zjrg1geQtCybrditUEZI3N75NlGa3+P4+HJBWac0siUqN7q8CZEZSzssKPg1nECs=
X-Received: by 2002:a9d:7e91:: with SMTP id m17mr54831408otp.78.1555555257033; Wed, 17 Apr 2019 19:40:57 -0700 (PDT)
MIME-Version: 1.0
References: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com> <CAHDzDLCKgvdDuxznW7UAQsvKWK1jCgdsUyLJA7GYGdYwUq-XOQ@mail.gmail.com> <7b4e4551-3d10-0b6e-91c1-4bc51c8d0831@network-heretics.com>
In-Reply-To: <7b4e4551-3d10-0b6e-91c1-4bc51c8d0831@network-heretics.com>
From: "Mukom Akong T." <mukom.tamon@gmail.com>
Date: Thu, 18 Apr 2019 06:40:26 +0400
Message-ID: <CAHDzDLDpXePASaYK-YNnVgeG2ju51gJ1t7eEB4SaQkExGf=Q4g@mail.gmail.com>
To: Keith Moore <moore@network-heretics.com>
Cc: manycouches@ietf.org
Content-Type: multipart/alternative; boundary="000000000000862c370586c4eeb0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/xC59msG_Hs3oR48yr1QbpemQGRs>
Subject: Re: [Manycouches] DOGFOOD Virtual BoF
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 02:41:03 -0000

On Wed, 17 Apr 2019 at 20:41, Keith Moore <moore@network-heretics.com>
wrote:

> I think we have to start somewhere, so starting with some base case -
> say just email - makes more sense than trying every tool right off the bat.
>


trying "every other tool" for say X months is starting somewhere and will
enable us to pick the most effective tool with the confidence of experience.



>
> shared editor that can keep track of
> what's been concluded.



this looks like a good requirement.



> but even then we need to have some discipline for
> what to put where.   Also, if we use multiple tools without some kind of
> integration between them I don't think we'll find that collection of
> tools very useful.



tech integration between multiple tools is a good requirement at a future
state. in the beginning and for a small number of people, that discipline
can be provided with a imple process that we all agree to follow.



>    Sometimes even when sticking to one tool - say
> slack - I find that the information that emerges from the discussion is
> so scattered that it's nearly unusable.
>

i use slack extensively at work, we define clearly what needs to
conversations that happen in slack

- if it's a key decision, someone gets an action item to make an entry into
the team's "Decision Log"  (a wiki page)
- if it's a set of tasks that need to be done, someone gets an action item
to create those as tasks in a project management system (JIRA) with a due
date and assignee

most "tool problems" are really just a lack of discipline in following a
pre-agreed upon process.


>
> I also am loathe to use third-party tools that track my activity, and
> would not want to see IETF adopt such tools.  So, for instance, google
> anything is (IMO) not appropriate.
>

that's fair and we can use that as a requirement for evaluating different
tools: "does not track user activity"


>
> We should decide what kind of tools we need rather than insisting on
> shoehorning our activity into existing tools.   And I'm not aware of an
> existing tool that would do the job well.
>


thank you. this is the thinking behind my suggestion. if we are trying to
do something different, it _may_ not be possible to use existing tools,
thinking and processes.


>
> On 4/17/19 11:11 AM, Mukom Akong T. wrote:
> > I think we ought to question even the tools and not assume that the
> > current tools as we have now are the best ones for the new approach we
> > want to try.
> > If there's some more effective tool out there, let's find it and try
> > it. It's better to settle on current tools with the secure knowledge
> > that we've tried the alternatives.
> >
>
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches
>


-- 

Mukom Akong T.

LinkedIn:Mukom <https://www.linkedin.com/in/mukom>  |  twitter:
@perfexcellent


------------------------------------------------------------------------------------------------------------------------------------------
“When you work, you are the FLUTE through whose lungs the whispering of the
hours turns to MUSIC" - Kahlil Gibran
-------------------------------------------------------------------------------------------------------------------------------------------