From: Dan Williams <dan.j.williams@intel.com>
To: Tech Board Discuss <tech-board-discuss@lists.linux-foundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] TAB Nomination
Date: Sat, 10 Nov 2018 12:52:03 -0800 [thread overview]
Message-ID: <CAPcyv4gq8CRCnZqWmNqupWzFOkqfDanUwCttwvxwj=zQqGwDfQ@mail.gmail.com> (raw)
Please add my name to the list of nominees for this year's TAB elections.
The responsibilities of a TAB member were a mystery when I ran
unsuccessfully in 2015, and were still unclear when I was elected in
2016. The common thread of motivation to try again in 2016 and stand
now in 2018 remains. It remains, tempered, but also strengthened by
the events of the past TAB term. The motivation is my perception is
that there is more work to be done to help scale maintainer resources,
and keep pace with the growth of new contributors and new problem
spaces.
I signed-off on the Code of Conduct as a starting point for a wider
discussion. I perceived that in some areas the project was falling
short of the Code of Conflict's stated of goal of fostering "be
excellent to each other" discourse, or that interactions were not
living up to the Management Style sentiment that "it's best to
remember not to burn any bridges, bomb any innocent villagers, or
alienate too many kernel developers". A baseline conduct document
frees us up to apply focus to wider process discussions. It seeks to
address exceptional cases and makes space to continue the work of
optimizing our day-to-day processes.
It has become clear to me that the "TA" in TAB is less about about
technical advice, and more about performing the role of a Trusted (by
the community) Adviser. Select people to the TAB that you trust to act
in the best interests of the long term health of the Linux Kernel
project. It is my hope that the past 13 years of my active
participation in the project has demonstrated an ability to listen and
respond to community concerns, and advocate for the health and
sustainability of the project.
next reply other threads:[~2018-11-10 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 20:52 Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 6:12 [Ksummit-discuss] TAB nomination Andy Lutomirski
2018-11-13 6:58 ` Steven Rostedt
2018-11-13 7:09 ` Andy Lutomirski
2018-11-13 19:06 ` Chris Mason
2018-11-13 3:46 [Ksummit-discuss] TAB Nomination Mauro Carvalho Chehab
2018-11-13 4:31 ` Steven Rostedt
2018-11-13 4:48 ` Chris Mason
2018-11-12 20:09 [Ksummit-discuss] TAB nomination Laurent Pinchart
2018-11-10 18:44 [Ksummit-discuss] TAB Nomination Laura Abbott
2018-11-08 5:14 [Ksummit-discuss] TAB nomination Kees Cook
2018-11-07 16:54 Shuah Khan
[not found] <340499F8-3113-4C8E-946B-3C33A1C4E3A7@fb.com>
2018-11-06 23:42 ` Olof Johansson
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='CAPcyv4gq8CRCnZqWmNqupWzFOkqfDanUwCttwvxwj=zQqGwDfQ@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).