Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination
Date: Tue, 13 Nov 2018 01:46:31 -0200	[thread overview]
Message-ID: <20181113014631.7cf11233@silica.lan> (raw)

Hi,

I've been actively working at the Linux Kernel since 2005, not only as a
developer but also maintaining the Media subsystem with due care. At the
time I started doing it, on my spare time, we started with about 30 patches
merged per Kernel release, having a consistent sustainable  grow along this
time. We have now about 400-500 patches per merge window, being one of the
most active development community. I also didn't miss a single merge window.

I've also been participating at the Kernel Summits and on other LF events 
for quite a while, and having organized/participated events specific for
the media development since 2007, as I believe that face to face meetings
help a lot to make our community stronger and helps to solve problems and
get consensus on themes that would otherwise require a lot of time and
efforts to do via other means.

I'm feeling that it is now the time to give one step further and to
offer my contributions as a TAB member.

I believe I can add value to TAB, as it sounds clear to me that we
want to give a message that the Kernel community is a welcomed place 
for everyone, and not just for the US/EU white people. I believe that 
having a South American representative that was very welcomed at the
Kernel community, with does a great job and that strongly believe that 
we've being doing a great job over those years to accept good code,
no matter about physical and cultural aspects of the developer will
help to spread the message that we welcome everyone that can write
good Kernel code and can behave inside an open source community.

I also believe that I can contribute to attract more developers that
don't match a specific stereotype and help to conduct discussions
that will help our community to grow on a sane way.

Cheers,
Mauro

             reply	other threads:[~2018-11-13  3:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  3:46 Mauro Carvalho Chehab [this message]
2018-11-13  4:31 ` [Ksummit-discuss] TAB Nomination Steven Rostedt
2018-11-13  4:48   ` Chris Mason
  -- 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-12 20:09 Laurent Pinchart
2018-11-10 20:52 [Ksummit-discuss] TAB Nomination 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=20181113014631.7cf11233@silica.lan \
    --to=mchehab@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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).