On 2/8/19 10:52 AM, Andrew Fish wrote:
I think the patch workflow is kind of like a coding standards. Some folks
advocate for lots of small patches (common in open source projects), and some
folks advocate for a patch per bug. I think the biggest upside to the patch
granularity is it is much
On Tuesday, 19 February 2019 23:23:59 MST stephano wrote:
> Github Pull Requests
> -
> We are still considering Github as a possible platform for patch review.
One thing I've not seen mentioned here is that there's an official command line
tool for GitHub, named 'hub': https:
On 2/19/2019 10:23 PM, stephano wrote:
Groups.io
-
Laszlo and I will evaluate Groups.io, however initial impressions is
that this will work as a communication platform going forward. We'd like
to use this for design discussions and as a replacement for our current
mailing
On 02/15/19 20:54, Felix Polyudov wrote:
>> -Original Message-
>> From: Laszlo Ersek
>> Sent: Friday, February 15, 2019 9:23 AM
>>
>> Just a short comment below.
>>
>> (Not changing my stance in any way that I've presented thus far; the
>> comment is only meant in addition to / as a clarifi
> -Original Message-
> From: Laszlo Ersek
> Sent: Friday, February 15, 2019 9:23 AM
>
> Just a short comment below.
>
> (Not changing my stance in any way that I've presented thus far; the
> comment is only meant in addition to / as a clarification for that.)
>
> On 02/15/19 09:43, Ard B
On 2/14/2019 6:56 PM, Rebecca Cran via edk2-devel wrote:
Thanks, I'm cautiously optimistic that groups.io will maintain a nice
email interface to the list(s). However I don't see any messages/topics
(in https://edk2.groups.io/g/main), and it appears my test posts are
being moderated: are there
On 02/15/19 03:56, Rebecca Cran wrote:
> On 2/14/19 3:13 PM, Kinney, Michael D wrote:
>> You can review the groups.io features. I think what you
>> want is available. Stephano has also setup an edk2 area
>> in groups.io for community member to try out.
>>
>> https://groups.io/static/help#feat
Just a short comment below.
(Not changing my stance in any way that I've presented thus far; the
comment is only meant in addition to / as a clarification for that.)
On 02/15/19 09:43, Ard Biesheuvel wrote:
> I would like to see more engagement from these contributors in the
> actual project bef
s.01.org; Kinney, Michael D; Laszlo Ersek
> Subject: Re: [edk2] [edk2-announce] Community Meeting Minutes
>
> On Thu, 7 Feb 2019 at 18:52, Jeremiah Cox via edk2-devel
> wrote:
> >
> > Apologies on the late reply, I was on vacation for several weeks and just
> > got bac
On 2/14/19 3:13 PM, Kinney, Michael D wrote:
You can review the groups.io features. I think what you
want is available. Stephano has also setup an edk2 area
in groups.io for community member to try out.
https://groups.io/static/help#features
There are a number of CI services that are
> boun...@lists.01.org] On Behalf Of Rebecca Cran via
> edk2-devel
> Sent: Thursday, February 14, 2019 12:28 PM
> To: Jeremiah Cox ; Ard
> Biesheuvel
> Cc: Kinney, Michael D ;
> edk2-devel@lists.01.org; Laszlo Ersek
>
> Subject: Re: [edk2] [edk2-announce] Community M
euvel
Sent: Friday, February 8, 2019 5:58 AM
To: Jeremiah Cox
Cc: stephano; edk2-devel@lists.01.org; Kinney, Michael D; Laszlo Ersek
Subject: Re: [edk2] [edk2-announce] Community Meeting Minutes
On Thu, 7 Feb 2019 at 18:52, Jeremiah Cox via edk2-devel
wrote:
Apologies on the late reply, I was on
.01.org; Kinney, Michael D; Laszlo Ersek
Subject: Re: [edk2] [edk2-announce] Community Meeting Minutes
On Thu, 7 Feb 2019 at 18:52, Jeremiah Cox via edk2-devel
wrote:
>
> Apologies on the late reply, I was on vacation for several weeks and just got
> back to this.
>
> Regardin
On 02/08/19 18:33, Rebecca Cran wrote:
>
> On February 8, 2019 at 2:01:59 AM, Laszlo Ersek
> (ler...@redhat.com(mailto:ler...@redhat.com)) wrote:
>
>> I don't see the workflow modification as viable. The "patch series"
>> concept is integral to every single open source project that I've ever
>>
> On Feb 8, 2019, at 9:33 AM, Rebecca Cran via edk2-devel
> wrote:
>
>
> On February 8, 2019 at 2:01:59 AM, Laszlo Ersek
> (ler...@redhat.com(mailto:ler...@redhat.com)) wrote:
>
>> I don't see the workflow modification as viable. The "patch series"
>> concept is integral to every single ope
On February 8, 2019 at 2:01:59 AM, Laszlo Ersek
(ler...@redhat.com(mailto:ler...@redhat.com)) wrote:
> I don't see the workflow modification as viable. The "patch series"
> concept is integral to every single open source project that I've ever
> worked with. The evolution of a feature or a bug f
On Thu, 7 Feb 2019 at 18:52, Jeremiah Cox via edk2-devel
wrote:
>
> Apologies on the late reply, I was on vacation for several weeks and just got
> back to this.
>
> Regarding "Patch Review System Evaluation", on the call, I disagreed with
> your conclusion, but that note is not captured below.
On 02/08/19 07:41, Rebecca Cran wrote:
> On Thursday, 7 February 2019 11:30:38 MST stephano wrote:
>
>> My apologies if I was not clear in the minutes. We are not rejecting
>> Github, but rather taking time to evaluate how we can supplement
>> Github's features to emulate our current patch revie
On Thursday, 7 February 2019 11:30:38 MST stephano wrote:
> My apologies if I was not clear in the minutes. We are not rejecting
> Github, but rather taking time to evaluate how we can supplement
> Github's features to emulate our current patch review requirements. We
> do not want to rush into
Hey Jeremiah,
My apologies if I was not clear in the minutes. We are not rejecting
Github, but rather taking time to evaluate how we can supplement
Github's features to emulate our current patch review requirements. We
do not want to rush into change and risk losing data or causing
frustratio
Apologies on the late reply, I was on vacation for several weeks and just got
back to this.
Regarding "Patch Review System Evaluation", on the call, I disagreed with your
conclusion, but that note is not captured below. My reading of the email and
call discussions, I did not hear our community
On 1/12/2019 7:59 PM, Rebecca Cran wrote:
I wonder if we might want to have a separate mailing list for reviews?
I find it a bit overwhelming having both patches and more general discussions
on the same list, since I only check it every few days.
My original thought was to add "edk2-announce
On 01/13/19 04:59, Rebecca Cran wrote:
> On Friday, 11 January 2019 12:26:30 MST stephano wrote:
>
>> Patch Review System Evaluation
>> --
>> After evaluating Github, Gitlab, and Phabricator, we will be remaining
>> with the mailing list for now. Github did prove a poss
On Friday, 11 January 2019 12:26:30 MST stephano wrote:
> Patch Review System Evaluation
> --
> After evaluating Github, Gitlab, and Phabricator, we will be remaining
> with the mailing list for now. Github did prove a possible "2nd runner
> up" (albeit distant). Also,
24 matches
Mail list logo
