From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self nomination : mchehab
Date: Thu, 6 Aug 2015 07:04:53 -0300 [thread overview]
Message-ID: <20150806070453.1aa7b496@recife.lan> (raw)
I'd like to nominate myself for the core discussions. As the maintainer of one
of the most active subsystem (media), there are lots of discussions there that
are relevant for me, and related to the maintainership process/workflow.
I'm particularly interested on the recruiting and documentation discussions,
as we always need more people to work at the subsystem. I guess I can help
with the documentation discussions, as I think we're doing a great job at
the media subsystem keeping the userspace API well documented
(Documentation/DocBook/media, e. g. http://linuxtv.org/downloads/v4l-dvb-apis/),
and also keeping a reasonable well documentation of the Kernel internal API, at
least for the main media frameworks (at Documentation/video4linux).
I have a personal interest on security, as I managed to get a CISSP
certification years ago, when I used to maintain the security team of
a big carrier.
I would like to participate on any GPL discussions. From time to time,
we receive large chunks of code from other systems that are re-licensed
as GPL. Also, from time to time, we heard that people might be using our
code on some proprietary stuff.
I may also give my view about mainlining the Kernel on a mobile device,
as I've been active at the Tizen community, and recently got a
maintainership at the Tizen on Yocto trees.
Regards,
Mauro
reply other threads:[~2015-08-06 10:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150806070453.1aa7b496@recife.lan \
--to=mchehab@osg.samsung.com \
--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