From: Christian Brauner <christian.brauner@ubuntu.com>
To: tech-board-discuss@lists.linuxfoundation.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination for Christian Brauner
Date: Sun, 8 Sep 2019 00:57:52 +0200 [thread overview]
Message-ID: <20190907225751.uvecuvpjmfbmqff7@wittgenstein> (raw)
Hey, I'm Christian. I've been involved in the container and namespace
area of the kernel which spans across multiple subsystems for some time.
I maintain the Android binderfs filesystem and the new pidfd api while
being active in various other areas of the kernel. I also I maintain
several large userspace projects and co-organized a few conferences over
the years including this year's All Systems Go in Berlin and the
container's microconference at the Linux Plumbers conference the last
couple of years.
I constantly try to lower the barrier for getting into kernel development,
supervising Linux-focussed bachelor theses and functioning as a mentor.
Even though it's slightly scary, stepping up for TAB nomination to help
maintain, defend, and grow Linux and especially the community around it
is a great way of giving back to a project that has proved invaluable
not just to me personally but to a great deal of people and companies.
The last couple of years I've worked together with various companies
across the industry focusing on container related technologies and
security. Serving on the TAB I intend to use this experience. I also
want to grow the community by helping with projects and programs such as
CommunityBridge that try to bring in new developers and ideas which is
vital to every open source project.
I also hope that stepping up for TAB nomination will encourage more
people to do so in the future and I thank everyone who encouraged me to
do so. :)
Christian
reply other threads:[~2019-09-07 22:57 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=20190907225751.uvecuvpjmfbmqff7@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tech-board-discuss@lists.linuxfoundation.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).