From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=65.103.231.193; helo=muon.bluestop.org; envelope-from=rebecca@bluestop.org; receiver=edk2-devel@lists.01.org Received: from muon.bluestop.org (unknown [65.103.231.193]) (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 2552F211D6174 for ; Mon, 11 Mar 2019 15:54:06 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 91A7679D69; Mon, 11 Mar 2019 16:55:21 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluestop.org; s=mail; t=1552344921; bh=sy4L0mr4br5oT6GracvDaviOJG1eTFXUvERjFWnx07U=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=t0dKePT2/n+sfdVz4SVlQy6wMFNX3MoAr9PoKnvRiohBnWFr0QMJ03yigMZcqys+G wuD9Mho8c0JLqhUwwTbYmaJCjdJQ1KFufJl1QBtrBDWD2R8mxewsD3YwwS6utGPf1f HDhl4RF7IrMJKcb6Pi74Ll4s2LwwYrj/9BekAlBI= Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zwyoJ203VlwO; Mon, 11 Mar 2019 16:55:21 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [10.0.10.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Mon, 11 Mar 2019 16:55:21 -0600 (MDT) To: stephano Cc: "edk2-devel@lists.01.org" References: <3dd639e4-2ff8-f8f1-a10d-8b4059169e25@bluestop.org> <4425e69d-72d9-eb1b-85eb-21c1f11c431d@linux.intel.com> From: Rebecca Cran Message-ID: <78ad39f6-38bc-0783-2f99-44204e3cce24@bluestop.org> Date: Mon, 11 Mar 2019 16:54:04 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 In-Reply-To: <4425e69d-72d9-eb1b-85eb-21c1f11c431d@linux.intel.com> Subject: Re: [edk2-announce] March 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: Mon, 11 Mar 2019 22:54:06 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US On 3/11/19 4:20 PM, stephano wrote: > On 3/11/2019 1:55 PM, Rebecca Cran wrote: > >> You can't see without following the pull request *who* committed the >> change.  There are almost 1000 open pull requests, which is something >> we probably want to try and avoid. They also seem to have _lots_ of >> labels. I wonder if there's a cleaner way of handling them? > > Agreed. We spoke about some of the downsides of pull requests in the > last stewards meeting. Linus did a fair job of detailing some of these > here: > > https://github.com/torvalds/linux/pull/17 > > I'm going to work with EDK II maintainers to be sure that we do not > move to a model that makes their life harder (e.g. 1000 open pull > requests). > >> >> >> Also, about groups.io, I wonder if I might want to investigate their >> support for using our own domain, so people don't have to remember >> that the mailing list and documents are on groups.io and not >> tianocore.org? >> > > Yes, I'm hoping to use our own domain with groups.io. Once we've > completed the testing phase I'll bring this up to my boss(es) to get > approval for an enterprise account ($200/month). That will allow us to > use something more friendly with tianocore.org. Thanks! Sorry for the skepticism, I've just had experiences in the past with new systems being introduced which made work more difficult (e.g. a commercial code review tool: several teams avoided it by using Review Board or Gerrit instead). -- Rebecca Cran