From: Grant Likely <glikely@secretlab.ca>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tech-board <tech-board@lists.linux-foundation.org>,
"lwn@lwn.net" <lwn@lwn.net>
Subject: Re: [Ksummit-discuss] [Tech-board] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Sun, 25 Oct 2015 16:35:54 +0900 [thread overview]
Message-ID: <CACxGe6sLqRVxX1kK-4GTe9ygtQoWDJipAssE7zsd91kx24cqNA@mail.gmail.com> (raw)
In-Reply-To: <20151024214507.1d33eb9a@xps.lwn.net>
On Sun, Oct 25, 2015 at 12:45 PM, Jonathan Corbet <corbet@lwn.net> wrote:
> On Sat, 24 Oct 2015 11:28:19 +0100
> Grant Likely <glikely@secretlab.ca> wrote:
>
>> 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:
>
> Great summary, Grant, thanks.
>
> A few additions of my own...
Oh, yes. I completely agree with the following. Thank you Jon.
>
> - The Linux Foundation tends to ask TAB members if they can give talks at
> events. Even more than free software development in general, TAB
> membership can be good if you don't like buying your own T-shirts!
>
> - The TAB has been named in the kernel's "code of conflict" as the body
> that will receive complaints about harassment or other untoward
> behavior in our community and try to resolve them. Thus far, no such
> complaints have been presented, but TAB members need to be prepared for
> that to happen.
>
> - It has been my feeling for a fair while that the LF could make more use
> of the TAB and its expertise than happens currently. Good TAB members
> might be those who are willing to let the LF know when they have an
> opinion on what the LF should be doing with and for the community. As
> an example, some of us have been pushing for the TAB to help with the
> selection of technical talks at LF conferences; I *think* that we
> provided useful input for LCE this year.
>
> That ties in to my last thought...in my time on the TAB, I've noticed
> that most of the work tends to be done by a relatively small subset of
> the members. Perhaps every committee is like that, in the end. A
> successful TAB member, IMO, is one who is willing to make the time to not
> just attend attend the meetings (which may be at less-than-convenient
> times depending on where you live and travel), but also to commit to
> putting some time into helping out when there's something to be done.
>
> jon
next prev parent reply other threads:[~2015-10-25 7:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:06 [Ksummit-discuss] " 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
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 [this message]
2015-10-24 16:51 ` [Ksummit-discuss] " Dan Williams
2015-10-24 17:37 ` Olof Johansson
2015-10-26 1:06 ` Darren Hart
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=CACxGe6sLqRVxX1kK-4GTe9ygtQoWDJipAssE7zsd91kx24cqNA@mail.gmail.com \
--to=glikely@secretlab.ca \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=corbet@lwn.net \
--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