From: Grant Likely <glikely@secretlab.ca>
To: Darren Hart <dvhart@infradead.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>,
"lwn@lwn.net" <lwn@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
tech-board <tech-board@lists.linux-foundation.org>
Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Sat, 24 Oct 2015 11:28:19 +0100 [thread overview]
Message-ID: <CACxGe6uGhwo=ueu56VhcWa7p68UH_EJVE+EOczBF5bhjhX=+-A@mail.gmail.com> (raw)
In-Reply-To: <20151022210329.GA5470@vmdeb7>
[Including Rafael who also asked about what being a TAB member means]
On Thu, Oct 22, 2015 at 10:03 PM, Darren Hart <dvhart@infradead.org> wrote:
> On Tue, Oct 06, 2015 at 11:06:47AM +0100, Grant Likely wrote:
> Is there a good description of what is expected of a TAB member? How much time
> is involved? What makes a great TAB member?
>
> I've found: http://www.linuxfoundation.org/programs/advisory-councils/tab
>
> I've read the charter and scanned some of the minutes, but I'd still like to
> hear from some of the "incumbants". Specifically, what makes you successful as a
> member of the TAB?
I've been asked several versions of the same question, and also the
annual "what does the TAB actually do?" question, so I'm going to try
and answer them all in one email:
As the name implies, the primary job of the TAB is to advise the Linux
Foundation board of directors on technical, social and political
issues regarding Linux and Open Source. Our job is to represent the
views of Linux developers and to foster constructive communication
between the Linux Foundation leadership and our community.
A natural by-product of this is that the TAB also acts in the
background to identify and resolve issues for the Linux community
before they become a problem. The TAB tends to be composed of well
respected individuals with good connections throughout our community,
and so we're in a good place to recognize who to talk to when an issue
is raised.
Finally, there are a few projects that the TAB is directly responsible
for. We make sure there is a planning committee for the Linux Plumbers
conference every year. We run a 'buddy' program to help new Linux
Foundation member companies learn how to be fine upstanding Linux
citizens. We are the response team for any issues of harassment or
abuse within the kernel community. In past years we coordinated the
response to UEFI Secure Boot to ensure that Linux would not be locked
out of the consumer PC market, and been active in helping member
companies understand and be comfortable with the licencing obligations
associated with Linux.
A good TAB member is well respected by the community, is a ready
listener, is comfortable discussing both technical and social issues,
and has a good understanding of how the Linux community works. Since
the TAB deals with a wide range of issues, the ideal TAB candidate
should be prepared to consider issues outside of their own area of
expertise. Sometime the most important characteristic of a TAB member
is recognizing when an issue is beyond their depth and go looking for
the right person to consult.
Time commitment wise, The TAB meets once a month for a conference
call, plus any additional time required to deal with TAB business.
Once a year (6 months after the TAB general election) the TAB elects
one member to serve as the chair, and the chair of the TAB is proposed
to the Linux Foundation to serve as a Linux Foundation Director which
has additional time requirements.
One last point, some issues addressed by the TAB are highly sensitive
and any member can request a topic to be kept strictly confidential.
We do this to protect the working relationship we have with industry
bodies, and to protect the companies and individuals involved. Any
prospective TAB member must be comfortable abiding by our
confidentiality rules.
I hope this answers your questions.
g.
next prev parent reply other threads:[~2015-10-24 10:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:06 Grant Likely
2015-10-06 14:21 ` [Ksummit-discuss] [Tech-board-discuss] " Josh Triplett
2015-10-13 8:06 ` Grant Likely
2015-10-11 4:20 ` [Ksummit-discuss] " Ric Wheeler
2015-10-13 8:12 ` Grant Likely
2015-10-13 13:09 ` Sage Weil
2015-10-14 17:48 ` Grant Likely
2015-10-13 5:19 ` Kees Cook
2015-10-13 8:10 ` Grant Likely
2015-10-13 16:11 ` Steven Rostedt
2015-10-15 21:56 ` Rafael J. Wysocki
2015-10-20 0:54 ` Grant Likely
2015-10-20 12:39 ` [Ksummit-discuss] [Tech-board-discuss] " Theodore Ts'o
2015-10-20 23:20 ` Grant Likely
2015-10-25 8:06 ` [Ksummit-discuss] " Grant Likely
2015-10-25 8:43 ` Grant Likely
2015-10-22 21:03 ` Darren Hart
2015-10-23 2:04 ` Neil Brown
2015-10-23 3:00 ` Kristen Accardi
2015-10-23 4:51 ` [Ksummit-discuss] [Tech-board-discuss] " Josh Triplett
2015-10-23 5:54 ` [Ksummit-discuss] " Neil Brown
2015-10-24 10:28 ` Grant Likely [this message]
2015-10-24 15:39 ` Rafael J. Wysocki
2015-10-24 15:58 ` [Ksummit-discuss] [Tech-board] " John W. Linville
2015-10-25 3:45 ` Jonathan Corbet
2015-10-25 7:35 ` Grant Likely
2015-10-24 16:51 ` [Ksummit-discuss] " Dan Williams
2015-10-24 17:37 ` Olof Johansson
2015-10-26 1:06 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 20:33 Chris Mason
2016-11-01 23:18 ` H. Peter Anvin
2014-07-15 21:48 James Bottomley
2014-08-18 20:13 ` James Bottomley
2014-08-19 14:43 ` Randy Dunlap
2014-08-19 13:45 ` Grant Likely
2015-09-29 21:55 ` Kees Cook
2015-09-29 22:00 ` Grant Likely
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='CACxGe6uGhwo=ueu56VhcWa7p68UH_EJVE+EOczBF5bhjhX=+-A@mail.gmail.com' \
--to=glikely@secretlab.ca \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=dvhart@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=rafael.j.wysocki@intel.com \
--cc=tech-board@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