From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bash the kernel maintainers
Date: Tue, 12 Sep 2017 11:00:19 +0300 [thread overview]
Message-ID: <3313596.2RcSzL2ip3@avalon> (raw)
Hello,
I have proposed a BoF session for ELCE 2017 titled "Bash the kernel
maintainers" which has been accepted.
The purpose of the session is to gather pain points, suggestions and any other
kind of feedback regarding the kernel maintenance process from developers who
do not attend the Kernel Summit and/or who usually stay silent due to the
false idea that the voice of occasional developers doesn't matter.
The session is scheduled for Monday October the 23rd (https://
osseu17.sched.com/event/ByYK/bash-the-kernel-maintainers-laurent-pinchart-
ideas-on-board). My plan is to submit an article with LWN.net with the
gathered feedback. If there is sufficient interest I can also provide a brief
readout during the maintainers summit.
--
Regards,
Laurent Pinchart
next reply other threads:[~2017-09-12 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 8:00 Laurent Pinchart [this message]
2017-09-15 2:38 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Bash the kernel maintainers Linus Torvalds
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=3313596.2RcSzL2ip3@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ksummit-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).