oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bjorge, Erik C <erik.c.bjorge@intel.com>
To: chipsec@lists.01.org
Subject: Re: Organizational Meeting
Date: Sat, 10 Nov 2018 00:27:33 +0000	[thread overview]
Message-ID: <7FE3244EBB31F1449E4EC79CFE44E3F4C2CFAE5E@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <bb9883d40d904adf8ab4e66da0222759@fmsmsx103.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

Sounds good to me.

Thanks,
-Erik

From: John Loucaides [mailto:john(a)eclypsium.com]
Sent: Friday, November 9, 2018 4:16 PM
To: chipsec(a)lists.01.org; chipsec-users(a)googlegroups.com; chipsec <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


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4381 bytes --]

       reply	other threads:[~2018-11-10  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bb9883d40d904adf8ab4e66da0222759@fmsmsx103.amr.corp.intel.com>
2018-11-10  0:27 ` Bjorge, Erik C [this message]
     [not found] <98f72a1ea4124311ba3336f75aad2ce9@fmsmsx122.amr.corp.intel.com>
2018-11-12 18:21 ` Organizational Meeting Bjorge, Erik C
2018-11-12 22:02   ` Arun Koshy
     [not found] <CA+zpnLcr9qFN3T2OHF_-fkFFY7qNjOA2TFKvsAaVQZNciWVnJA@mail.gmail.com>
2018-11-13 22:31 ` John Loucaides
2018-11-14 20:06   ` Arun Koshy

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=7FE3244EBB31F1449E4EC79CFE44E3F4C2CFAE5E@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 NNTP newsgroup(s).