public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: stephano <stephano.cetola@linux.intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] March Community Meeting Minutes
Date: Mon, 11 Mar 2019 16:54:04 -0600	[thread overview]
Message-ID: <78ad39f6-38bc-0783-2f99-44204e3cce24@bluestop.org> (raw)
In-Reply-To: <4425e69d-72d9-eb1b-85eb-21c1f11c431d@linux.intel.com>

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



  reply	other threads:[~2019-03-11 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 16:33 [edk2-announce] March Community Meeting Minutes stephano
2019-03-11 20:55 ` Rebecca Cran
2019-03-11 22:20   ` stephano
2019-03-11 22:54     ` Rebecca Cran [this message]
2019-03-11 22:29 ` stephano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78ad39f6-38bc-0783-2f99-44204e3cce24@bluestop.org \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox