From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: tech-board-discuss@lists.linux-foundation.org
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB nomination
Date: Mon, 12 Nov 2018 22:09:32 +0200 [thread overview]
Message-ID: <4182231.IhO9L5F7xp@avalon> (raw)
Hello,
I would like to stand for the TAB election.
Governance and conduct have recently become a very hot topic in our community.
Only the timing should have caught us by surprise, as problems in those areas
have been known for a long time. During the past few years I reflected upon
those issues and on many occasions discussed them with developers and
maintainers from different subsystems. There was a large consensus that we
were not doing great, but at the same time helplessness (and sometimes
despair) were prevalent. I would like to turn those negative emotions into
positive actions to help our community.
While not a political correctness activist, I believe in the balance between
freedom of thoughts and expression, and respect and civilized interactions
between humans. As such, I would like to improve the feedback and decision
processes in the Linux kernel to give everybody a chance to be heard and be
part of our community. This is why I would like to stand for the election.
In addition to governance and conduct, I have long thought that our
maintenance process is flawed. The Linux kernel has grown over the past 27
years in what is largely seen as unique in free software and software in
general. With my very first contact with Linux kernel development nearly 20
years ago, and my first sizable contribution in 2005, I have witnessed, from
the inside, the community evolving. We have collectively brought the Linux
kernel into the 21st century and turned this hobbyist project into a
professional project without forgetting where we came from. We can't stop
there.
The Linux kernel is probably, in most areas, more welcoming today than it has
ever been. Despite this, interactions between developers and maintainers
generate lots of frustration. On the positive side, this means we have lots of
room for improvement. Several subsystems have experimented with alternatives
to the historical maintenance scheme, with various levels of success, but we
largely remain a hierarchical community with a traditional power structure. I
believe we could improve this by giving more power to developers, for the
greater good of the community, and would like to bring that vision to the TAB.
This is why I would like to stand for the election.
--
Regards,
Laurent Pinchart
next reply other threads:[~2018-11-12 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 20:09 Laurent Pinchart [this message]
2018-11-12 20:36 ` [Ksummit-discuss] [Tech-board-discuss] TAB nomination Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 6:12 [Ksummit-discuss] " 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-10 20:52 Dan Williams
2018-11-10 18:44 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=4182231.IhO9L5F7xp@avalon \
--to=laurent.pinchart@ideasonboard.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).