ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Mason <clm@fb.com>
Cc: tech-board-discuss@lists.linux-foundation.org,
	"ksummit-discuss@lists.linux..."
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Reminder: Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Wed, 26 Oct 2016 14:04:10 -0400	[thread overview]
Message-ID: <20161026140410.2415d4ea@gandalf.local.home> (raw)
In-Reply-To: <4467045d-42b7-cb94-aeca-9b1fd814954a@fb.com>

On Mon, 24 Oct 2016 11:47:23 -0400
Chris Mason <clm@fb.com> wrote:

> The deadline for receiving nominations is up until the beginning of
> the event where the election is held.  Any statements for the online 
> document need to be sent by Friday Oct 28th.  Please remember if
> you're not going to be present that things go wrong with both networks
> and mailing lists, so get your nomination in early).

Note, to encourage people to post early, the list of names in the
online document will be in the order their nomination emails appear in
the tech-board-discuss archives:

 https://lists.linuxfoundation.org/pipermail/tech-board-discuss/2016-October/thread.html

The earlier you get your submissions in, the further up in the document
you will be listed. So far I have two: Josh Triplett and Rik van Riel.

If you later want to update what will be in the document, please email
me and the list with your update. You will still keep your position in
the document determined by your original submission.

Also, please do not send a nomination as a reply to any email. All
nominations should start their own thread, otherwise they may be missed
and not accounted for.

-- Steve

      reply	other threads:[~2016-10-26 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 15:47 Chris Mason
2016-10-26 18:04 ` Steven Rostedt [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-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=20161026140410.2415d4ea@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=clm@fb.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tech-board-discuss@lists.linux-foundation.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