From nobody Mon Nov 14 18:49:23 2016 Return-Path: X-Original-To: ietf-and-github@ietfa.amsl.com Delivered-To: ietf-and-github@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62D811294A3 for ; Mon, 14 Nov 2016 18:49:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.402 X-Spam-Level: X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no 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 emNC_ySoHEIS for ; Mon, 14 Nov 2016 18:49:21 -0800 (PST) Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 31ADD1294F7 for ; Mon, 14 Nov 2016 18:49:21 -0800 (PST) Received: (qmail 18394 invoked by uid 0); 15 Nov 2016 02:49:13 -0000 Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy6.mail.unifiedlayer.com with SMTP; 15 Nov 2016 02:49:13 -0000 Received: from box514.bluehost.com ([74.220.219.114]) by cmgw2 with id 82p81u0052UhLwi012pBVK; Mon, 14 Nov 2016 19:49:11 -0700 X-Authority-Analysis: v=2.1 cv=YNIMl32x c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=L24OOQBejmoA:10 a=SSmOFEACAAAA:8 a=NEAV23lmAAAA:8 a=48vgC7mUAAAA:8 a=ieNpE_y6AAAA:8 a=jZII0VwwP6nuq-lME-4A:9 a=KqYruMnwRuqDZHsl:21 a=cI0CGTlqqwvbdS0V:21 a=QEXdDO2ut3YA:10 a=zjWhRoSqWz9hl55Hdlzg:22 a=Bn2pgwyD2vrAyMmN8A2t:22 a=w1C3t2QeGrPiZgrLijVG:22 a=lOZzU2MLX5qQKtuoMSD9:22 Received: from dhcp-8f06.meeting.ietf.org ([31.133.143.6]:62860) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from ) id 1c6To5-0001YF-Ff; Mon, 14 Nov 2016 19:49:09 -0700 To: Paul Hoffman From: =JeffH Message-ID: <5d17a3a2-9333-0336-5fca-08c497db3994@KingsMountain.com> Date: Tue, 15 Nov 2016 11:49:01 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box514.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - KingsMountain.com X-BWhitelist: no X-Source-IP: 31.133.143.6 X-Exim-ID: 1c6To5-0001YF-Ff X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: dhcp-8f06.meeting.ietf.org [31.133.143.6]:62860 X-Source-Auth: jeff.hodges+kingsmountain.com X-Email-Count: 2 X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ== Archived-At: Cc: IETF and github Subject: Re: [Ietf-and-github] WG documents and pull requests, issues, and WG mail X-BeenThere: ietf-and-github@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 02:49:22 -0000 I have experience using github in IETF, W3C, and FIDO Alliance contexts (both as a WG chair (in fido) and as a spec editor (in all three)). IMV, W3C has it pretty well figured out _and_ documented, eg see.. Using GitHub for W3C specifications https://www.w3.org/2015/Talks/1217-github-w3c/#/1 We, IETF, ought to develop similar guidelines/procedures. Note also that W3C folk developed a github-to-mailing list gateway that allows WGs to make fine-grained per-WG gateway configurations (it is open source). fyi/fwiw, below's the note I sent to tools-discuss on this topic a while back, with relevant links. Overall, i think github issues and events _need_ to be gatewayed to a mailing list of any IETF working group utilizing github.com -- however, whether it is done on the main WG mailing list, or an adjunct mailing list (that all WG members are encouraged to join) ought to be up to the WG chairs & WG to decide. HTH, =JeffH ### On 4/22/16, 3:48 PM, "Tools-discuss on behalf of =JeffH" wrote: fyi/fwiw, the W3C has pretty well worked out how to incorp github.com repos into their processes, including mailing lists. Here's some info that we IETF oughta at least look at and perhaps borrow/leverage -- it would be great if we could at least stand up a github-notify-mla instance.. mailing list integration w/github issues & pull requests & pushes, etc https://github.com/dontcallmedom/github-notify-ml/ note that https://github.com/dontcallmedom/github-notify-ml/index.py needs to be installed and configured on a internet-accessible web server, and registered with github.com as a webhook endpoint. how the W3C's instance is config'd is noted here: https://github.com/dontcallmedom/github-notify-ml#w3c-instance see also... Using GitHub for W3C specifications https://www.w3.org/2015/Talks/1217-github-w3c/#/1 ###