From nobody Fri Apr 22 10:26:21 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 7BAA412DD48 for ; Fri, 22 Apr 2016 10:26:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -22.521 X-Spam-Level: X-Spam-Status: No, score=-22.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=paypal.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 FckIeH1IIvsz for ; Fri, 22 Apr 2016 10:26:17 -0700 (PDT) Received: from den-ipout-03-data1.paypalcorp.com (den-ipout-03-data1.paypalcorp.com [173.224.160.157]) (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 D3EF312DCBB for ; Fri, 22 Apr 2016 10:26:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=paypal.com; i=@paypal.com; q=dns/txt; s=pp-dkim1; t=1461345977; x=1492881977; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=YQQ3Iz8mLgBeYzX3BegkgFlew1YsUxpzhyrsk4vD6GQ=; b=NRvwz+oeDSWkAaf2tl/VwEkDHwoCv6/11F360EQ0WqPOpkg/lkIF4d4q 70T8Yd1lrZ9x7UX9rSoCF9rxaq4w/45+Q9228l4B/ZmRCtaGcXVCmczBI 9SFNatwHgceOy6M9ArSpXyN1SHPKgPls6nUmMNFIO7UbQGCJEYsB4/2RU 1YxtSvy8axOZdavwU1EMShd7/ZiX5BUoRwMO3McFRM2aYboXxKdgdVbG9 4KsEosk/Hswbxm801cFZwaShUwxwwxErlwwbdLCwzL3UkF9niTpJZu9fY 1rpjGVVT3aG7OxUxtTw2vmJK8DWCgLhwnH38Vsnca68+ezJ3XqroBac++ w==; X-IronPort-AV: E=Sophos;i="5.24,518,1455001200"; d="scan'208";a="14055130" Received: from unknown (HELO lvs-ipcld-01-data1.paypalcorp.com) ([10.184.246.166]) by den-ipout-03-data1.paypalcorp.com with ESMTP; 22 Apr 2016 11:26:15 -0600 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,518,1455004800"; d="scan'208";a="4857059" X-CloudService: Office365 Received: from mail-bn1lp0139.outbound.protection.outlook.com (HELO na01-bn1-obe.outbound.protection.outlook.com) ([207.46.163.139]) by lvs-ipcld-01-data1.paypalcorp.com with ESMTP/TLS/AES256-SHA256; 22 Apr 2016 10:26:15 -0700 Received: from SN1PR06MB2094.namprd06.prod.outlook.com (10.169.125.142) by SN1PR06MB2093.namprd06.prod.outlook.com (10.169.125.141) with Microsoft SMTP Server (TLS) id 15.1.466.19; Fri, 22 Apr 2016 17:26:14 +0000 Received: from SN1PR06MB2094.namprd06.prod.outlook.com ([10.169.125.142]) by SN1PR06MB2094.namprd06.prod.outlook.com ([10.169.125.142]) with mapi id 15.01.0466.022; Fri, 22 Apr 2016 17:26:14 +0000 From: "Hodges, Jeff" To: "ietf-and-github@ietf.org" Thread-Topic: [Ietf-and-github] Legal notices (was: Re: A possible way of keeping WG informed of github tracked issues? Thread-Index: AQHRXITFd1TLDrBmEkqSAY0gTXnN6Z8WXT+AgAAZJACAAAQeAIAABw8AgAGYcwCAfi+7gA== Date: Fri, 22 Apr 2016 17:26:13 +0000 Message-ID: References: <700E78FA-C5ED-4597-97F3-25D4B67722A0@mnot.net> <56AEC1EC.1030706@gmail.com> <56AECB4C.6060402@gmail.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=paypal.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [173.224.162.69] x-ms-office365-filtering-correlation-id: 57e5cf76-eed8-4d63-2a4b-08d36ad33480 x-microsoft-exchange-diagnostics: 1; SN1PR06MB2093; 5:UmqTEu1wTOJvOKhesiLW008XpleugsQ3SZSGyMSgTP3LIG6I3X9+8S/5LHHn1x9ZDac3MhiZoFbdPVJkFNou/4Jg5+4fxy16SVdc4GUxXsFXd9z5eEUvkwY2h+xfvmQYRSO7t0Q4r4SgG0TS7kc+GMo4ktBzAmjad1ndu6Owd+MdDYdpzV3KdkYYSbq1zn9k; 24:NtOrN07V+vRNekJDPNTDTxqAWRC3EBC1ppa6w6imYX8zBMulOVi7ZTmGrINnRjjDonaJIyrfkpKrH5iGEN25Ws0Vo+mxc/XPyN2gI/iBlC0=; 7:Fo60RT5J30wT33XFOlanuD6d8NQhf9rmccujCa0QHZrCmcQQrf2Ve/MyQGtpNV6uGMXrpv+q/blD8jMABa8H9y+in3qMJrBoiHwafYpVUIdSRxD5wiS3jCTWF4XNRHpJyvXRMgDtVac19Wfsk44uTtVbjoks7/D/pRHgDU6jgPhdKa4ZHAAFXCjqnfV49VrjpbBR6auWx7tIoa/PO1rSsfDe/x98J8mJC6CKPolOMxA= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR06MB2093; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(95692535739014); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:SN1PR06MB2093; BCL:0; PCL:0; RULEID:; SRVR:SN1PR06MB2093; x-forefront-prvs: 0920602B08 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377454003)(51444003)(87936001)(4500500003)(15975445007)(586003)(3846002)(93886004)(2900100001)(6116002)(102836003)(2950100001)(54356999)(107886002)(5002640100001)(2906002)(11100500001)(110136002)(10770500004)(50986999)(81166005)(5640700001)(2501003)(10130500003)(122556002)(86362001)(76176999)(92566002)(5004730100002)(189998001)(5008740100001)(82432001)(1096002)(77096005)(10300500001)(36756003)(10290500002)(19580395003)(10400500002)(9686002)(73692002)(230783001)(450100001)(66066001)(3280700002)(106116001)(1220700001)(99286002)(19580405001)(3660700001)(2351001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR06MB2093; H:SN1PR06MB2094.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: <5BBECE9BEA3F5742B84A1F39471FE4AB@namprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: paypal.com X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2016 17:26:13.9423 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: fb007914-6020-4374-977e-21bac5f3f4c8 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR06MB2093 X-CFilter: Scanned den1 Archived-At: Subject: Re: [Ietf-and-github] Legal notices (was: Re: A possible way of keeping WG informed of github tracked issues? 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: Fri, 22 Apr 2016 17:26:19 -0000 On 2/1/16, 7:26 PM, "Charles Eckel (eckelcu)" eckelcu@cisco.com> wrote: >https://github.com/martinthomson/i-d-template/blob/master/template/CONTRIB >UTING.md is a great example and addresses many of the concerns others >have raised > about github usage, but I agree with Brian that it would be better to >include a ptr to the Note Well than a snapshot of it. +1 Also, BTW, the W3C has pretty well worked out how to incorp github.com repos into their processes, including mailing lists (as Harald noted upthread). Here's some info that we IETF oughta at least look at and perhaps borrow/leverage.. 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 License/Contributing legal boilerplate: https://github.com/w3c/licenses HTH, =3DJeffH > >On 2/1/16, 4:04 AM, "Ietf-and-github on behalf of Brian E Carpenter" >brian.e.carpenter@gmail.com> wrote: > >>On 01/02/2016 15:39, Mark Nottingham wrote: >>>>On 1 Feb 2016, at 1:24 pm, Brian E Carpenter >>>> wrote: >>>> >>>>IANAL, but my understanding is that it is generally better to point to >>>>the official >>>>rules than to generate copies in each place or to add explanatory >>>>material >>>>that might unintentionally modify the interpretation. So maybe we >>>>should >>>>create a short CONTRIBUTING.md and request the IETF counsel to check >>>>it. >>>I think that's the function of NOTE WELL, isn't it? >>>Each WG might have additional information they want to add, so I don't >>>think we could have each one be exactly the same, but maybe what we >>>need is ( NOTE_WELL + ADDITIONAL_GITHUB_SPECIFICS? + WG_STUFF ). >> >>Sure, but the NOTE WELL is not a universal constant, and may change from >>time to time, which is why I used: >> >>This repository is for an IETF effort and falls under IETF rules: see >>http://www.ietf.org/about/note-well.html >> >> >> Brian >> >>_______________________________________________ >>Ietf-and-github mailing list >>Ietf-and-github@ietf.org >>https://www.ietf.org/mailman/listinfo/ietf-and-github >> > > From nobody Fri Apr 22 15:21:02 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 DCD9112E963 for ; Fri, 22 Apr 2016 15:21:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=kingsmountain.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 xjR3jMsqO9tQ for ; Fri, 22 Apr 2016 15:20:58 -0700 (PDT) Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id C468512E95A for ; Fri, 22 Apr 2016 15:20:55 -0700 (PDT) Received: (qmail 31830 invoked by uid 0); 22 Apr 2016 22:20:52 -0000 Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy7.mail.unifiedlayer.com with SMTP; 22 Apr 2016 22:20:52 -0000 Received: from box514.bluehost.com ([74.220.219.114]) by cmgw4 with id laLo1s00C2UhLwi01aLrUC; Fri, 22 Apr 2016 16:20:52 -0600 X-Authority-Analysis: v=2.1 cv=aJ5j99Nm 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=XYUc-DgfXtMA:10 a=UFWr1SZZQlcA:10 a=kziv93cY1bsA:10 a=SSmOFEACAAAA:8 a=48vgC7mUAAAA:8 a=qI-sqkvjAAAA:8 a=AUd_NHdVAAAA:8 a=NEAV23lmAAAA:8 a=pGLkceISAAAA:8 a=FoGfdgL0UfYH4V5tHaUA:9 a=IP-mh1zjA4WeguUm:21 a=PVaPQeaAPMSasemm:21 a=QEXdDO2ut3YA:10 a=_0_MY4KVxfwA:10 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Date:Message-ID:Subject:From:To; bh=i/V/Rua+DoPjR8+ZFRAqofmSY6EFrGFXub+R4+9ZN6c=; b=m0fYJN5W87mJNKSyH6VtZW6ss8 D9QkhtIu0dYHTpP0IknPg7izyLgspwM/XbqCSPKyk36fVDkc2Rxt5LHMd3HBrfU2XoGP7TuhKaAkX 9CSDlfI9XenOU+PPcwPMsr75m; Received: from [70.213.9.16] (port=5716 helo=[10.0.0.1]) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_2) (envelope-from ) id 1atjRP-0004xz-UR for Ietf-and-github@ietf.org; Fri, 22 Apr 2016 16:20:48 -0600 To: Ietf-and-github@ietf.org From: =JeffH Message-ID: <571AA3B4.30709@KingsMountain.com> Date: Fri, 22 Apr 2016 15:20:36 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 70.213.9.16 authed with jeff.hodges+kingsmountain.com} Archived-At: Subject: Re: [Ietf-and-github] Legal notices (was: Re: A possible way of keeping WG informed of github tracked issues? 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: Fri, 22 Apr 2016 22:21:01 -0000 see also... Using GitHub for W3C specifications https://www.w3.org/2015/Talks/1217-github-w3c/#/ On 4/22/16, 10:26 AM, "Ietf-and-github on behalf of Hodges, Jeff" wrote: On 2/1/16, 7:26 PM, "Charles Eckel (eckelcu)" eckelcu@cisco.com> wrote: >https://github.com/martinthomson/i-d-template/blob/master/template/CONTRIB >UTING.md is a great example and addresses many of the concerns others >have raised > about github usage, but I agree with Brian that it would be better to >include a ptr to the Note Well than a snapshot of it. +1 Also, BTW, the W3C has pretty well worked out how to incorp github.com repos into their processes, including mailing lists (as Harald noted upthread). Here's some info that we IETF oughta at least look at and perhaps borrow/leverage.. 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 License/Contributing legal boilerplate: https://github.com/w3c/licenses HTH, =JeffH > >On 2/1/16, 4:04 AM, "Ietf-and-github on behalf of Brian E Carpenter" >brian.e.carpenter@gmail.com> wrote: > >>On 01/02/2016 15:39, Mark Nottingham wrote: >>>>On 1 Feb 2016, at 1:24 pm, Brian E Carpenter >>>> wrote: >>>> >>>>IANAL, but my understanding is that it is generally better to point to >>>>the official >>>>rules than to generate copies in each place or to add explanatory >>>>material >>>>that might unintentionally modify the interpretation. So maybe we >>>>should >>>>create a short CONTRIBUTING.md and request the IETF counsel to check >>>>it. >>>I think that's the function of NOTE WELL, isn't it? >>>Each WG might have additional information they want to add, so I don't >>>think we could have each one be exactly the same, but maybe what we >>>need is ( NOTE_WELL + ADDITIONAL_GITHUB_SPECIFICS? + WG_STUFF ). >> >>Sure, but the NOTE WELL is not a universal constant, and may change from >>time to time, which is why I used: >> >>This repository is for an IETF effort and falls under IETF rules: see >>http://www.ietf.org/about/note-well.html >> >> >> Brian >> >>_______________________________________________ >>Ietf-and-github mailing list >>Ietf-and-github@ietf.org >>https://www.ietf.org/mailman/listinfo/ietf-and-github >> > > _______________________________________________ Ietf-and-github mailing list Ietf-and-github@ietf.org https://www.ietf.org/mailman/listinfo/ietf-and-github