All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "tech-board-discuss@lists.linux-foundation.org"
	<tech-board-discuss@lists.linux-foundation.org>
Subject: Re: [Tech-board-discuss] Technical Advisory Board Elections
Date: Mon, 12 Nov 2018 12:16:32 -0500	[thread overview]
Message-ID: <20181112121632.7de966f1@vmware.local.home> (raw)
In-Reply-To: <20181112121126.GA2707@amd>

On Mon, 12 Nov 2018 13:11:26 +0100
Pavel Machek <pavel@ucw.cz> wrote:

> On Wed 2018-11-07 14:20:52, Chris Mason wrote:
> > On 7 Nov 2018, at 5:12, Pavel Machek wrote:
> >   
> > > Hi!
> > >
> > > I'd like to stand for TAB elections in 2018.
> > >
> > > I'm not sure what the format of statements for the slideshow is / how
> > > long it should be?
> > >  
> > 
> > Hi Pavel,
> > 
> > You can take a look at the google doc for statements from this year, or 
> > look at last year's: https://goo.gl/ADVFtT
> > 
> > In general it's an introduction to yourself and why you'd like to run 
> > for the TAB, one-three short paragraphs.  
> 
> Ok, let me try:
> 
> "Kernel hackers are funny people. They count time in patch
> levels. Pavel started hacking kernel at time of Linux 1.3, because he
> wanted his CD-ROM to work; that eventually became NBD driver. He then
> helped with x86-64 kernel port and got hibernation support merged into
> kernel, which he still co-maintains.
> 
> Pavel currently works on various embedded projects. In his spare time,
> he rides horses, helps maintaining the LED subsystems, and he is on
> quest to get up-to-date kernels running on cellphones, with final goal
> of running "normal" distributions on phones.
> 
> Pavel believes that community is important, and that important
> decisions should be made publicly. He believes that development should
> be fun, and that honest communication should be possible on the
> mailing lists. Pavel finds it important to get replies when
> communicating with maintainers; even reply that is not politically
> correct is useful, because it you know maintainer is willing to talk,
> and ideally you get also some idea what the problem is. Silent
> maintainer is worse as you don't know what is going on. Goal of the
> kernel development should be to get best possible kernel, and it
> should be possible to have fun while doing so.
> "
>

Hi Pavel,

I just want to confirm that this is your self nomination. Usually,
people will send a new message (not in a thread) with the subject like
"TAB Nomination".

Perhaps we need to spell this out a bit better.

Pavel, either just confirm that is what you mean, or better yet, send
out a new email to the tech-board-discuss list (not as a reply to a
thread) with the subject "TAB Nomination", and that will also more
likely get more people to see it.

Either way, I'll then add you to the google docs of those that are
running.

-- Steve

      reply	other threads:[~2018-11-12 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 10:12 [Tech-board-discuss] Technical Advisory Board Elections Pavel Machek
2018-11-07 14:20 ` Chris Mason
2018-11-12 12:11   ` Pavel Machek
2018-11-12 17:16     ` 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=20181112121632.7de966f1@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=pavel@ucw.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.