public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: tech-board-discuss@lists.linux-foundation.org,
	ksummit-2013-discuss@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Standing for the Linux Foundation Technical Advisory Board
Date: Tue, 22 Oct 2013 23:56:03 +0200	[thread overview]
Message-ID: <20131022215603.GA5554@suse.cz> (raw)


I am standing for the Linux Foundation Technical advisory board.

Since I'm not attending LinuxCon EU, nor the Kernel Summit, I won't be
there for the TAB election at the evening event either, hence I'll try
to introduce myself in this email.

My first encounter with Linux was Slackware in 1993 with kernel 0.99,
installed from a stack of floppies, and while it was still very young,
the possibility to improve it was a reason to forget about DOS, Xenix,
SINIX, SCO UNIX and LynxOS that I was using back then.

And I did. Initially just a few patches to the (now gone) ARCnet
drivers, then a joystick driver rewrite, eventually a rewrite of the
whole input subsystem and a bunch of work on USB. I rewrote a bunch of
IDE drivers. For a few years I was maintaining the Input and HID
subsystems of the Linux kernel, until my other duties forced me to hand
that over to their present excellent maintainers. I was also a member of
the team that worked on a port of Linux to the x86-64 architecture,
achieving a successful boot when the first silicion was available.

I used Linux to power autonomous robots, figuring out the
limits of its realtime behavior and after a few less than successful
attempts, eventually scored a 4th place in the Eurobot Open robotics
championship.

My day job today is that of a Director of SUSE Labs, a department within
SUSE development that focuses on developing core open source projects:
the Linux kernel, the GNU toolchain, including GCC and glibc and Samba.
My work is to create an environment where open source hackers thrive
inside SUSE, allowing us to contribute to open source projects, while
creating a stable foundation for each release of SUSE's enterprise
distribution.

While the time I can devote to real hacking and coding is limited today,
I still love going very much technical and solving problems by looking
at them from new perspectives: When secure boot came around, I designed
the MOK concept, which allows users to manage their own keys even in the
absence of any help from the platform, returning to them the freedom
that was threatened.

This I'm offering my time, my helping hand and my thoughts to the TAB,
hoping that I can contribute to solving any future problems Linux and
the Linux Foundation may face.

Vojtech Pavlik

                 reply	other threads:[~2013-10-22 22:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131022215603.GA5554@suse.cz \
    --to=vojtech@suse.cz \
    --cc=ksummit-2013-discuss@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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