From: Laura Abbott <laura@labbott.name>
To: tech-board-discuss@lists.linux-foundation.org
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination
Date: Sat, 10 Nov 2018 10:44:12 -0800 [thread overview]
Message-ID: <16D2BBDD-D856-4C94-8B42-4B888531875E@labbott.name> (raw)
I'd like to nominate myself for the TAB. I sometimes blog about the kernel
community and this is a chance for me to actually put my money where
my mouth is.
I've been working in the kernel community long enough at this point that
people know who I am as a Fedora kernel maintainer and a contributor
in the security and ARM areas. I also joined the kernel community recently enough
that I can remember what it was like to be a beginner starting out. I usually
tell people that I've had a fairly positive experience in the kernel community
and I'd like to make sure that everyone can have an even better experience.
The kernel community has certainly grown and changed over the years
and it's important to both reflect on how far we've come and what else we
can do to make things better.
I was certainly in favor of seeing a stronger code of conduct as the previous
code of conflict had deficits in certain areas. I've also learned a lot reading
the objections people had to both the code of conduct itself and how it
was implemented. I strongly believe that a strong code of conduct and
a being a community that values technical excellence are well aligned goals.
Continuing to discuss these issues transparently is an going to be an important
point going forward.
The TAB has worked on a number of tricky issues such as malicious GPL
compliance for the betterment of the kernel community. I'd like to see
the TAB continue to work on issues like the Code of Conduct and also
think about what more can be done to work on building up new contributors
and maintainers to support the existing maintainers. I don't believe I have
all the answers or will always be right but I look forward to the chance to
learn and help serve the kernel community.
Thanks,
Laura
next reply other threads:[~2018-11-10 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 18:44 Laura Abbott [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 20:52 [Ksummit-discuss] TAB Nomination Dan Williams
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=16D2BBDD-D856-4C94-8B42-4B888531875E@labbott.name \
--to=laura@labbott.name \
--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).