zulip+github ? (was: Re: [Tools-discuss] zulip.ietf.org is fully deployed.)

Toerless Eckert <tte@cs.fau.de> Thu, 19 May 2022 19:43 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 63837C26E8DF; Thu, 19 May 2022 12:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.651
X-Spam-Level:
X-Spam-Status: No, score=-6.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 RKnWMmuU3vVx; Thu, 19 May 2022 12:43:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04099C26E8AB; Thu, 19 May 2022 12:43:27 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id E599B58C4AF; Thu, 19 May 2022 21:43:22 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id D145A4EAF2E; Thu, 19 May 2022 21:43:22 +0200 (CEST)
Date: Thu, 19 May 2022 21:43:22 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: tools-discuss <tools-discuss@ietf.org>, Working Chairs <wgchairs@ietf.org>
Subject: zulip+github ? (was: Re: [Tools-discuss] zulip.ietf.org is fully deployed.)
Message-ID: <Yoad2j9fia0fRNi7@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/mRgbY91CW709wBNMOLZFdCyilCo>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 19 May 2022 19:43:33 -0000

https://github.com/ietf-tools/zulip-implementation/blob/main/Service-Plan.md

| 4.2 GitHub integration
| Any stream can be optionally configured to receive GitHub notifications.
|  WGs can decide if these should be received into an existing stream or a separate dedicated stream.

I was trying to click myself through the web-interface but couldn't figure out
how that would have to be set up. It might actually be quite useful to bridge the gap between
the pat of my WG that breathes github, and the other part who doesn't know what it is..

Aka: instructions / pointer (URL) welcome.

Cheers
    Toerless