From: Bjorge, Erik C <erik.c.bjorge@intel.com>
To: chipsec@lists.01.org
Subject: Re: Organizational Meeting
Date: Mon, 12 Nov 2018 18:21:16 +0000 [thread overview]
Message-ID: <7FE3244EBB31F1449E4EC79CFE44E3F4C2CFB638@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <98f72a1ea4124311ba3336f75aad2ce9@fmsmsx122.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3515 bytes --]
I can make that work.
Thanks,
-Erik
From: John Loucaides [mailto:john(a)eclypsium.com]
Sent: Monday, November 12, 2018 9:45 AM
To: Thiébaud Weksteen <tweek@google.com>
Cc: Bjorge, Erik C <erik.c.bjorge@intel.com>; chipsec(a)lists.01.org; chipsec-users(a)googlegroups.com; chipsec <chipsec@intel.com>
Subject: Re: Organizational Meeting
Sorry about that. Wed should be fine for me. Erik, how about you?
Thanks,
John
On Mon, Nov 12, 2018, 2:44 AM 'Thiébaud Weksteen' via chipsec-users <chipsec-users(a)googlegroups.com<mailto:chipsec-users@googlegroups.com> wrote:
Hi all,
Any chance to make it slightly more Europe friendly? 11am PST is fine but on another day? Would Wednesday works?
Thanks
On Sat, Nov 10, 2018 at 1:27 AM Bjorge, Erik C <erik.c.bjorge(a)intel.com<mailto:erik.c.bjorge@intel.com>> wrote:
Sounds good to me.
Thanks,
-Erik
From: John Loucaides [mailto:john(a)eclypsium.com<mailto:john@eclypsium.com>]
Sent: Friday, November 9, 2018 4:16 PM
To: chipsec(a)lists.01.org<mailto:chipsec@lists.01.org>; chipsec-users(a)googlegroups.com<mailto:chipsec-users@googlegroups.com>; chipsec <chipsec(a)intel.com<mailto:chipsec@intel.com>>
Subject: Organizational Meeting
Hey everyone,
Now that it's been a while since we have been meeting regularly (and I've moved over to eclypsium), we might want to do a more formal sync between maintainers. Word on the street is that Friday is best for this, so I'd like to propose next week, Friday, Nov 16 at 11am PST. Let me know if that works. If not, no problem. Just suggest another time for me.
The idea is to discuss focus areas and next steps for the maintainers. Also, we can sync on process steps and expectations so that we don't accidentally drop/break stuff.
Logistically, I'm thinking we set up a google hangout/meet with dial-in option. If that doesn't work, again, just let me know. We can follow up with meeting details.
Thanks!
John
--
You received this message because you are subscribed to the Google Groups "chipsec-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chipsec-users+unsubscribe(a)googlegroups.com<mailto:chipsec-users+unsubscribe@googlegroups.com>.
To post to this group, send email to chipsec-users(a)googlegroups.com<mailto:chipsec-users@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipsec-users/7FE3244EBB31F1449E4EC79CFE44E3F4C2CFAE5E%40ORSMSX114.amr.corp.intel.com<https://groups.google.com/d/msgid/chipsec-users/7FE3244EBB31F1449E4EC79CFE44E3F4C2CFAE5E%40ORSMSX114.amr.corp.intel.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "chipsec-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chipsec-users+unsubscribe(a)googlegroups.com<mailto:chipsec-users+unsubscribe@googlegroups.com>.
To post to this group, send email to chipsec-users(a)googlegroups.com<mailto:chipsec-users@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipsec-users/CA%2BzpnLcad51QqC_G_eDPm0gGW%2BukG%2BteeHuvkcyQEJmoMa8kDA%40mail.gmail.com<https://groups.google.com/d/msgid/chipsec-users/CA%2BzpnLcad51QqC_G_eDPm0gGW%2BukG%2BteeHuvkcyQEJmoMa8kDA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 11182 bytes --]
next parent reply other threads:[~2018-11-12 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98f72a1ea4124311ba3336f75aad2ce9@fmsmsx122.amr.corp.intel.com>
2018-11-12 18:21 ` Bjorge, Erik C [this message]
2018-11-12 22:02 ` Organizational Meeting Arun Koshy
[not found] <CA+zpnLcr9qFN3T2OHF_-fkFFY7qNjOA2TFKvsAaVQZNciWVnJA@mail.gmail.com>
2018-11-13 22:31 ` John Loucaides
2018-11-14 20:06 ` Arun Koshy
[not found] <bb9883d40d904adf8ab4e66da0222759@fmsmsx103.amr.corp.intel.com>
2018-11-10 0:27 ` Bjorge, Erik C
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-all 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=7FE3244EBB31F1449E4EC79CFE44E3F4C2CFB638@ORSMSX114.amr.corp.intel.com \
--to=erik.c.bjorge@intel.com \
--cc=chipsec@lists.01.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).