public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: stephano <stephano.cetola@linux.intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] [RFC] TianoCore Design Meetings
Date: Mon, 25 Mar 2019 08:25:56 -0700	[thread overview]
Message-ID: <3a930ad9-49bc-5b5c-df8e-cd9a7c0cb15b@linux.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E40B339@SHSMSX104.ccr.corp.intel.com>

Hey Liming,

Yes, that's no problem. We will do the move on April 3rd (PST) so that 
we don't conflict with the holiday.

Cheers,
Stephano

On 3/25/2019 6:51 AM, Gao, Liming wrote:
> Stephano:
>    April 5th (Friday in PRC) is Chinese public holiday. Could we place one day ahead, how about April 3th (PST)?
> 
> Thanks
> Liming
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of stephano
>> Sent: Saturday, March 23, 2019 8:29 AM
>> To: edk2-devel@lists.01.org
>> Subject: [edk2] [edk2-announce] [RFC] TianoCore Design Meetings
>>
>> We would like to start holding code design meetings every 2 weeks
>> starting on April 4th. I'm proposing the times of these meetings as
>> 16:00 GMT (8am PST) and at 2:30 GMT (9:30am Friday in PRC).
>>
>> I have chosen the APAC day / time based on feedback from those community
>> members and maintainers. For our members in EMEA, this is your chance to
>> propose a new day / time. Specifically, I'd like to hear from
>> maintainers and technical leads in the EMEA region as their
>> participation is vital to these meeting's goals.
>>
>> This meeting is a chance for the TianoCore community to bring any
>> initial design ideas and communicate those ideas to tech leaders and
>> fellow developers. I will be collecting ideas for discussion, and will
>> be sure that those ideas are shared in both sessions so as to get
>> feedback across all our community members.
>>
>> Content related to designs (including documentation, slides, and links
>> to code) can be shared on Groups.io:
>>
>> https://edk2.groups.io/g/devel/files/Designs/2019
>>
>> I will also post meeting minutes here, so that those that miss the
>> meeting can review the design files and notes together.
>>
>> I've added the events to the calendar:
>>
>> https://edk2.groups.io/g/devel/calendar
>>
>> And will update the wiki with each session's topics:
>>
>> https://www.tianocore.org/design-meeting/
>>
>> As always, please feel free to contact me with questions or comments.
>>
>> Cheers,
>> Stephano
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2019-03-25 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  0:28 [edk2-announce] [RFC] TianoCore Design Meetings stephano
2019-03-25 13:51 ` Gao, Liming
2019-03-25 15:25   ` stephano [this message]

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=3a930ad9-49bc-5b5c-df8e-cd9a7c0cb15b@linux.intel.com \
    --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