From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by mx.groups.io with SMTP id smtpd.web09.1520.1650397704106585875 for ; Tue, 19 Apr 2022 12:48:24 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Xjx3cMD/; spf=pass (domain: kernel.org, ip: 145.40.68.75, mailfrom: ardb@kernel.org) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 5B6A1B81AA4 for ; Tue, 19 Apr 2022 19:48:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CCF79C385B7 for ; Tue, 19 Apr 2022 19:48:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650397699; bh=05AqNiiDcGxcxJlLEtQn2SNzt+Tw/D9pyIfeBTSei/c=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Xjx3cMD/xAAvta/XCsHNo3DvUEsx7pkTrQMcoeXvyscB1HSNazFlktnSeWyQytOd5 k2BepWIVq0vtA35s/h26dGRakTCkR84ZDfvpRbeBxdUStBNzVSIJMkDsOIW04F55K9 m6cO5PjHedweIBvdaMqlJYSPJW5sQ5Eni/KKjZ2y+lUrO0Flr81dCTxxEkmiUTqWbx Cdu4vZga6j9RYoLsazHHwA05pHXDLnVca1qtahy84yR4NQdlaHXO3J3Agk9hke2Y6p x/XR/k69QPiU5WTmuzCnKxX/MAimp1F26i1awzHoEmIBMXRixyki8G0Gx/YOrAVTHw h1cKJfwpZ+8Jg== Received: by mail-oa1-f50.google.com with SMTP id 586e51a60fabf-e2a00f2cc8so18655805fac.4 for ; Tue, 19 Apr 2022 12:48:19 -0700 (PDT) X-Gm-Message-State: AOAM530YyrvYX4NEgRINVnan66ekKRI8jsMId7r4E62g2Lr1iDsjXbq3 IIY+5hI2TWr5YdkongevmsbLf8YfUwFledm0Reo= X-Google-Smtp-Source: ABdhPJzF2qogUmOHsvnI/0sIIJQ81RHfspvYwQIJdVSgbr+1Y+mw3b8tf87GD3MWgYc+7aGLuSbqUerlPTBAjWWNjAI= X-Received: by 2002:a05:6870:eaa5:b0:da:b3f:2b45 with SMTP id s37-20020a056870eaa500b000da0b3f2b45mr111333oap.228.1650397698859; Tue, 19 Apr 2022 12:48:18 -0700 (PDT) MIME-Version: 1.0 References: <7447e624-0c47-f184-85fa-3db39a91fd40@linux.microsoft.com> In-Reply-To: <7447e624-0c47-f184-85fa-3db39a91fd40@linux.microsoft.com> From: "Ard Biesheuvel" Date: Tue, 19 Apr 2022 21:48:07 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [edk2-platforms][IMPORTANT] CI in edk2-platforms To: Michael Kubacki Cc: "devel@edk2.groups.io" , Ard Biesheuvel , Leif Lindholm , Nhi Pham , Vu Nguyen , Thang Nguyen , Chuong Tran , Thomas Abraham , Sami Mujawar , Ray Ni , Ilias Apalodimas , Andy Hayes , Wenyi Xie , Pedro Falcato , Sai Chaganty , Isaac Oram , Nate DeSimone , Liming Gao , Eric Dong , Dandan Bi , Zailiang Sun , Yi Qian , Chasel Chiu , Benjamin Doron , Jeremy Soller , Deepika Kethi Reddy , Kathappan Esakkithevar , Heng Luo , Bob Feng , Yuwei Chen , Abner Chang , Daniel Schaefer , Gilbert Chen , Michael D Kinney , Kelly Steele , Marcin Wojtas , Meenakshi Aggarwal , Graeme Gregory , Radoslaw Biernacki , Jeremy Linton , Masami Hiramatsu , Peng Xie , Ling Jia , Yiqi Shu , Sean Brogan , miki.demeter@intel.com Content-Type: text/plain; charset="UTF-8" Hello Michael, On Tue, 19 Apr 2022 at 17:17, Michael Kubacki wrote: > > Hello edk2-platforms maintainers, > > There is a TianoCore community meeting on Tools and CI that takes place > weekly on Mondays from 19:30 - 20:30 PDT. > That is 4:30 AM my time, unfortunately. > Meeting Details: > https://github.com/tianocore/edk2/discussions/2614 > > Several recurring topics have come up regarding edk2-platforms: > > 1. Consistently define toolchain support in edk2-platforms > https://bugzilla.tianocore.org/show_bug.cgi?id=3660 > > 2. Audit edk2-platforms maintainers > https://bugzilla.tianocore.org/show_bug.cgi?id=3659 > > 3. Enable continuous integration (CI) in edk2-platforms > https://bugzilla.tianocore.org/show_bug.cgi?id=3658 > > 4. Stable tag support in edk2-platforms > https://bugzilla.tianocore.org/show_bug.cgi?id=3661 > > As a maintainer, your help is needed to make progress on these items. > > Ultimately, we want the open-source platforms to be more approachable > and reliable by removing inactive platforms, eliminating unnecessary > tool divergence, enabling well-defined and functional CI builds, and > refreshing the maintainer list with the appropriate contacts. > > To start, can you please respond if a representative from your package > is able to attend the meeting at the regularly scheduled time to discuss > these topics? > No > If not, can you please state the representative and their timezone you > would like to join the discussion and we can try to plan around that. > > We would like to add this to May 2, 2022 meeting instance agenda if we > have quorum. > > Thank you for your time and assistance. > I'm happy to collaborate on this but a weekly meeting doesn't really fit my schedule to begin with, so please don't plan around my [lack of] availabity. Kind regards, Ard.