Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD Capabilities With Page Table Attributes

["Michael Kubacki" <mikuback@linux.microsoft.com>]

Sounds good, thanks for the quick response. Can you please send a 
calendar invite when you get a chance?

On 6/1/2023 10:42 PM, Ni, Ray wrote:
> It's a good idea to have a focus area ("project") for everyone working together on the same problem.
> I see the benefit of having "project" is to align everyone's priority so the "project" can be done within a certain deadline.
> 
> Let's talk more about following items in next meeting:
> 1. Alignment of the problem to solve
> 2. Alignment of the priority
> 
> I am available at 10pm~11pm (GMT+8) next Wednesday night.
> 
> Thanks,
> Ray
> 
>> -----Original Message-----
>> From: Michael Kubacki <mikuback@linux.microsoft.com>
>> Sent: Friday, June 2, 2023 10:24 AM
>> To: Ni, Ray <ray.ni@intel.com>; Oliver Smith-Denny <osde@linux.microsoft.com>;
>> devel@edk2.groups.io; Ard Biesheuvel <ardb@kernel.org>; Kinney, Michael D
>> <michael.d.kinney@intel.com>; t@taylorbeebe.com
>> Cc: Leif Lindholm <quic_llindhol@quicinc.com>; Ard Biesheuvel
>> <ardb+tianocore@kernel.org>; Sami Mujawar <sami.mujawar@arm.com>; Sean
>> Brogan <sean.brogan@microsoft.com>
>> Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD Capabilities
>> With Page Table Attributes
>>
>> Hi Ray,
>>
>> We found the last meeting to be very helpful. Can you please set up an
>> agenda for an upcoming meeting to discuss what's happened since and next
>> steps?
>>
>> If you're available, perhaps we could see if Wednesday next week at the
>> same time would work?
>>
>> We'd also like to share how GitHub Projects [1] can be used to track
>> future work in the memory protection work stream. We've talked about
>> Projects for a while in the TianoCore Tools & CI working group and this
>> looks like a great opportunity to try it out. A public project has been
>> created in the TianoCore org [2]. I've placed some initial high-level
>> pillars in the project at the moment.
>>
>> Projects can help break down larger complex items and show how the
>> pieces fit together in a single place. It helps visualize who is working
>> on what, when they roughly expect to complete it, and what pillars of
>> memory protection work such as compatibility, testing, etc. are defined
>> and how we're making progress toward them. In this meeting, we'd like to
>> discuss how we can most effectively use it to collaborate in upcoming
>> work areas.
>>
>> It is not meant to replace the mailing list for communication or change
>> code review process but to organize and visualize agreed upon memory
>> protection work items. Ideally, this will help track that the areas are
>> covered we expect, simplify planning to intercept the changes in
>> platforms, show how work items are connected, and enable new
>> contributors to quickly see how they can contribute.
>>
>> [1] -
>> https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-
>> about-projects/about-projects
>> [2] - https://github.com/orgs/tianocore/projects/3
>>
>> Thanks,
>> Michael
>>
>> On 5/17/2023 3:14 AM, Ni, Ray wrote:
>>> I created one event in https://edk2.groups.io/g/devel/calendar.
>>>
>>> Microsoft Teams meeting link: https://teams.microsoft.com/l/meetup-
>> join/19%3ameeting_YTk4ZDU3YjItODkxZC00MTdmLTlkZmUtYThkNGQ0ZWYyMDZ
>> h%40thread.v2/0?context=%7b%22Tid%22%3a%2246c98d88-e344-4ed4-8496-
>> 4ed7712e255d%22%2c%22Oid%22%3a%2255d36a50-78be-4ced-bc27-
>> 3d06c576cc19%22%7d
>>>
>>> The ICS file is also attached.
>>>
>>>
>>>> -----Original Message-----
>>>> From: Oliver Smith-Denny <osde@linux.microsoft.com>
>>>> Sent: Wednesday, May 17, 2023 1:12 AM
>>>> To: Ni, Ray <ray.ni@intel.com>; devel@edk2.groups.io; Ard Biesheuvel
>>>> <ardb@kernel.org>; Kinney, Michael D <michael.d.kinney@intel.com>;
>>>> t@taylorbeebe.com
>>>> Cc: Leif Lindholm <quic_llindhol@quicinc.com>; Ard Biesheuvel
>>>> <ardb+tianocore@kernel.org>; Sami Mujawar <sami.mujawar@arm.com>;
>>>> Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>>> <sean.brogan@microsoft.com>
>>>> Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD
>> Capabilities
>>>> With Page Table Attributes
>>>>
>>>> Hi Ray,
>>>>
>>>> That works from our side, thanks for setting up the meeting!
>>>>
>>>> Oliver
>>>>
>>>> On 5/15/2023 7:53 PM, Ni, Ray wrote:
>>>>> All,
>>>>> Can you check if the meeting time is ok for you?
>>>>>
>>>>> It will be in this week:
>>>>> * PDT Wednesday 07:00
>>>>> * Paris Wednesday 16:00
>>>>> * Shanghai Wednesday 22:00
>>>>>
>>>>> ________________________________________
>>>>> From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Taylor
>> Beebe
>>>> <t@taylorbeebe.com>
>>>>> Sent: Thursday, May 11, 2023 0:10
>>>>> To: devel@edk2.groups.io; osde@linux.microsoft.com; Ard Biesheuvel;
>> Kinney,
>>>> Michael D
>>>>> Cc: Ni, Ray; Leif Lindholm; Ard Biesheuvel; Sami Mujawar; Michael Kubacki;
>>>> Sean Brogan
>>>>> Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD
>>>> Capabilities With Page Table Attributes
>>>>>
>>>>> Can we schedule the meeting for Wednesday 5/17? I will be out the
>>>>> following week and would like to attend.
>>>>>
>>>>> Thanks :)
>>>>>
>>>>> On 5/9/2023 7:59 AM, Oliver Smith-Denny wrote:
>>>>>> On 5/8/2023 11:59 PM, Ard Biesheuvel wrote:
>>>>>>> On Tue, 9 May 2023 at 04:04, Kinney, Michael D
>>>>>>> <michael.d.kinney@intel.com> wrote:
>>>>>>>>
>>>>>>>> I would prefer next week as well.
>>>>>>>>
>>>>>>>> Mike
>>>>>>>>
>>>>>>>
>>>>>>> Next week, i can only do Wednesday. The week after (22-26), the time
>>>>>>> slot works for me on any day of the week.
>>>>>>>
>>>>>>
>>>>>> Weds works from our side, the week after also works perfectly well
>>>>>> any day. Thanks for the flexibility and willingness to meet.
>>>>>>
>>>>>> For reference for this specific patch, this bz may help cache in
>>>>>> some info: https://bugzilla.tianocore.org/show_bug.cgi?id=753. The
>>>>>> mail links are largely dead, of course, but can be found on other
>>>>>> mailing list retention sites (maybe in the future we will have PRs
>>>>>> and discussions to reference :).
>>>>>>
>>>>>> Thanks,
>>>>>> Oliver
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>>