From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=104.47.34.100; helo=nam01-by2-obe.outbound.protection.outlook.com; envelope-from=jerecox@microsoft.com; receiver=edk2-devel@lists.01.org Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0100.outbound.protection.outlook.com [104.47.34.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id A9E1421157FF1 for ; Fri, 19 Oct 2018 09:09:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DWlhugzHv/V22SCxxoPfBaF4avQOqvL/p2wds+Bn4YM=; b=L4XP7v0JJNWBRD6bnlgQxnxxZDlv7OTCWojITf6Yzv1dVLObzgElqaeEDpATyK+FKTQMlnt0riFp0AMNC5vE4lC9AsC2ywfTrOIYt8aFxgi4Hi/k4oJ0uqQS4xepBZTpRvuzIUkbp8ZZZk6TqOwFVQ5vG1OtJwCCwGy0yWEW9PY= Received: from MWHPR21MB0176.namprd21.prod.outlook.com (10.173.52.22) by MWHPR21MB0637.namprd21.prod.outlook.com (10.175.141.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.2; Fri, 19 Oct 2018 16:09:43 +0000 Received: from MWHPR21MB0176.namprd21.prod.outlook.com ([fe80::8817:5ea6:f97f:aa10]) by MWHPR21MB0176.namprd21.prod.outlook.com ([fe80::8817:5ea6:f97f:aa10%2]) with mapi id 15.20.1250.004; Fri, 19 Oct 2018 16:09:43 +0000 From: Jeremiah Cox To: stephano CC: "edk2-devel@lists.01.org" Thread-Topic: [edk2] TianoCore Community Meeting Minutes Thread-Index: AdRnxabuVZCDoU1dR0eVSRA/wMSgAA== Date: Fri, 19 Oct 2018 16:09:43 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [50.35.76.74] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; MWHPR21MB0637; 6:5RhXdmQsGSJc0jIYyrSSCdXpq1I4eangKObXuDATn++vmpe3XvppNfLKy7ATqcK+083e2b9mT0Apa47chr+VwJ98ILQLfceYbhC2DnmU+IUp4HRzGIkch/6TT2kynowlO14nxNVviTISwFm5KU94qLJFXeU6xTzm4jlz5GgxIIxKsQ0H8IFOetbkoDfYvGN2MeAt+ElmoSP/CVXOeHBZ2iE+9ajBsN12EuV2xegTrt9D2AkdN720t1Z8710hqLSP+aVWZVm1aTgmv0VHZRUtXtWM48ALamhggpfTaAvCt87PrOA7WOWSR680Jd9kIvkpR/xUYe2i11e+X7YbT7frzQGEuXkiCZKGHBplaL4cjcxQL/oZHROXRPWHZHuCREUKaFLu0VgxGubf8HLzB/uC1QegTQxYeCLtYmBkwPca7BlyY2jl1ZVyRaQZ9J8AqUPzK4BndNq+CX0uBf+hX0BFwg==; 5:j/+qRL5y2YV0BXFw/LfwUPEvkRbsNNdtiyL9+pnlPksDnN+ST03v030z1zFDZ/l9mKOxkU/LSa6udRDjcly+ggpuH2HYcunXKSahramS2lPmo+j7ELK3qOF1ZBwD5C7rl99CDdSPLd9++DxHs6VLaGIbLbc8Pp++epy1kzxxp5U=; 7:LnrvIv4CXkYEBiJzmZdJW2lta21e3r6ZBdkoh5SXyJjhH18qtFK6nOb0Mx0ZhuNEDdlXKHFKFEbBbaowa2YkUrBwP+W4w1BowZrzfXYDCwxZvyo6nytOAPY/eIGd3BotKjmaD516qvA13cOhW0x81g== x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: e7d1bbc3-bc7c-4c64-8d65-08d635dd4821 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MWHPR21MB0637; x-ms-traffictypediagnostic: MWHPR21MB0637: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(271806183753584)(21748063052155)(28532068793085)(190501279198761)(227612066756510); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(8220027)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231355)(944501410)(52105095)(2018427008)(6055026)(148016)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:MWHPR21MB0637; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0637; x-forefront-prvs: 0830866D19 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39860400002)(376002)(366004)(136003)(199004)(189003)(6916009)(55016002)(66066001)(9686003)(68736007)(71200400001)(6436002)(71190400001)(54896002)(6306002)(1857600001)(5660300001)(4326008)(14444005)(5250100002)(256004)(10290500003)(97736004)(316002)(478600001)(8990500004)(106356001)(105586002)(2900100001)(25786009)(53936002)(14454004)(22452003)(186003)(7696005)(10090500001)(99286004)(81166006)(81156014)(7736002)(8676002)(476003)(86362001)(6116002)(790700001)(6506007)(102836004)(86612001)(2906002)(3846002)(6346003)(8936002)(486006)(26005)(74316002)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0637; H:MWHPR21MB0176.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=jerecox@microsoft.com; x-microsoft-antispam-message-info: S5MWGSw9SXHNgKMpDDdg46C1g9N+QpA+M7Dr21C2orZv9HPFH4VLVHAdDZPy/QGlEvIcxm6bfEVJAw9Ozm1KlbUgVjY0hGSaoYbVu26uODYg26rmZJQzqjzWM4sOZZSU2GcYBisSZ1eIMLmsB9pmC4iMuKhOPus7X974C/NSG8hFKw4PUT882kxdKifu4ebhBhFZ0wkmgNLYwJdbR4+FkXmsfgPQMVyXTrDhuXz54Y0Ga5pf0e3hkiQfp8+gTM+8dkHlTEG4IcUGx5keW7Y8UpPsKp8HUphTU5gvkvzm66CDuaOyLMRlhscDrB6jWqD6GQ1SOwSbi8bV3T5oqFQGuL2iZUPAj7+fVtyQPj7UnRQ= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: e7d1bbc3-bc7c-4c64-8d65-08d635dd4821 X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2018 16:09:43.2925 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0637 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: TianoCore Community Meeting Minutes X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 16:09:45 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Finally finding time to respond to an older thread... >>> The was a concern raised over potential lock-in to Github's, specifical= ly in >>> regards to history retention. >>> Several Github users brought up that this shouldn't be an issue. >> >> Hopefully they said more than that. >> What does "shouldn't be an issue" mean. >> Were these users from multiple organisations? > >I will ask for more details in the next meeting, but the comments were >that the API is quite robust and lends itself to readily accessible data. I'd like to better understand assertions of GitHub "lock in". GitHub provi= des a comprehensive REST API that you can easily drive via Python ("pip ins= tall PyGithub"). I recall one assertion that GitHub holds PR comments hostage, but it is tri= vial to dump out all Comments on all PRs in a repo. g =3D Github( ) repo =3D g.get_repo("chipsec/chipsec") pulls =3D repo.get_pulls(sort=3D'created', base=3D'master') for pr in pulls: for comment in pr.get_review_comments(): print(pr.number) print(comment.body) ... Can folks help me better understand examples of GitHub "lock in"? I think = it would be trivial to author a daemon that listens for PRs and comments, a= nd forward those to a mailing list, if that is preferred for archival. >> >>> Shawn mentioned some benefits to stock Github such as >>> it is always up to date, it includes APIs to extract data, pull >>> requests >> >> Since we are discussing multiple different development systems, can we >> try to be a bit more explicit? This is referring to github's web-based >> branch-based ticketing system, yes? > >Yes that's correct. With respect to web-based, we believe it facilitates convenient, multi-plat= form access, and GitHub's REST APIs can be leveraged to provide a command-l= ine driven experience. I believe Sean's point was that GitHub provides a 1= -stop shop for code reviews and issue tracking such that there is no need t= o spend TianoCore resources set up, maintain, and update separate Bugzilla = and Gerrit services, VMs, OSs, & machines. The REST APIs could be used to = maintain a mailing list or other mirror. I am not asserting that GitHub pr= ovides the best code review and issue tracker experience, our team finds Az= ure Dev Ops is superior, but GitHub is sufficient for most use cases while = handling the infrastructure so that we can focus on getting things done. I think it would be helpful to construct a PROs/CONs table for each of the = proposed end-to-end solution (source control, code review, gates, CI/CD, is= sue tracking, testing, ...). Perhaps this table is on a wiki to enable fas= ter iteration than emails on the DL. >> I know language drift and all, but >> >> is what pull request means to at least 3 participants in this conversati= on. > >I think this is an important distinction to make and I'm sure it will >come up in future discussions. I'll be sure to bring this up. We think of "Pull Request" as a contribution & review process akin to GitHu= b, GitLab, or Azure DevOps. Feedback, responses, automated check-in gates,= and signoff can be handled within each PR ticket. Policies can be assigne= d, automated tests that must pass, enforcement of community wide rules (# o= f reviewers, reviewer list, all comments "resolved"). Tests could start as= simple as successful build and over time could grow to a more comprehensiv= e set of boot, functional, static analysis, ... By leveraging a popular hosting provider's built-in workflow we enjoy signi= ficant efficiencies. Its fully documented and known to most. New capabili= ties are being added daily. No TianoCore resources would be required to ma= nage systems, OS patches, network issues, etc and can instead be focused on= TianoCore code, building tests, and driving process improvements. >> >> It seems somewhat less than ideal to me that all of the github >> proponents were on the opposite call to me and Laszlo (and Ard). Were >> any of them Asia-based or could we try to get them on the call with >> Europe next time? I'm sure me and Laszlo could be somewhat more >> accommodating than your 7AM, but we're not going to stay up for a 3/4AM >> meeting about source control. > >That's understandable. I'm not sure where Shawn and Nate are located, >but I believe it is in the US. We could certainly move the AM call a bit >later if it makes it easier to get more folks from the US on that call. Agreed, pushing the US/EU call out a couple hours (8 or 9am Pacific) would = likely increase Pacific participation. Thanks, Jeremiah