Ksummit-Discuss Archive on lore.kernel.org
 help / color / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: tech-board-discuss@lists.linuxfoundation.org
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination for Theodore Ts'o
Date: Thu, 5 Sep 2019 17:51:54 -0400
Message-ID: <20190905215154.GA7469@mit.edu> (raw)

I've worked on the Linux Kernel still 1991, and have worked on the tty
subsystem, serial driver, real-time linux, ext2/3/4 and e2fsprogs.  I
served on the board of the Free Standards Group (one of the
predecessor organizations to the Linux Foundations), as well as
Usenix, and have served on the program committee of many conferences
including Usenix ATC, FAST, Vault, LinuxCon, and the Linux
Kernel/Maintaiiner's Summit.

If I am re-elected to the TAB, I'd like to work with the various
conferences and workshops to better balance the technical work that
gets done at these events, so that members of our community can meet
with the people they need to meet, in a product setting, without
certain conferences --- such as the Linux Plumbers Conference ---
becoming heavily oversubscribed and over-crowded.  In my opinion, this
means we need to create or strengthen a strong technical conference
which meets in the first half the year, which can serve as a Linux
Systems Conference as vital and as exciting as the LPC is in the
second half of the year.  Clearly, we have a lot more technical work
that we would like to do that can be accomodated by having a single
really great conference once a year!

I am also interested in helping to reinvigorate the Linux Foundation's
Core Infrastructure Initiative (CII).  No, it's not completely dead,
in that even in 2019, it's still funding some great work, but it
certainly has the appearance of "Pining for the Fjords".  We need to
improve its fund-raising capacity, remove cobwebs from its web site,
and make sure it can be more responsive to proposals sent to it.
While this isn't a TAB function, I think there are opportunities for
the TAB as a body, and for individual TAB members, to help the CII
be as successful as it was when it first started.

                 reply index

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

Reply instructions:

You may reply publically 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=20190905215154.GA7469@mit.edu \
    --to=tytso@mit.edu \
    --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

Ksummit-Discuss Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/ksummit-discuss/0 ksummit-discuss/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ksummit-discuss ksummit-discuss/ https://lore.kernel.org/ksummit-discuss \
		ksummit-discuss@lists.linuxfoundation.org
	public-inbox-index ksummit-discuss

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.linuxfoundation.lists.ksummit-discuss


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git