From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] TAB non-nomination
Date: Tue, 13 Nov 2018 21:59:50 +0200 [thread overview]
Message-ID: <2027180.eEsTsxCshK@avalon> (raw)
In-Reply-To: <87r2fogbwp.fsf@intel.com>
Hi Jani,
On Tuesday, 13 November 2018 18:49:58 EET Jani Nikula wrote:
> On Sun, 11 Nov 2018, "Theodore Y. Ts'o" wrote:
> > "Community" is a very slippery term. I will note that there were
> > *many* people who were participating on the threads, sometimes in very
> > non-constructive or in a downright toxic fashion, who had zero commits
> > in recent years. In some cases, it was zero commits, *ever*. I
> > recall doing the research on one prolific author and found that while
> > he did contribute the kernel, it was 3 or 4 commits... ~5 years
> > ago... to a driver.
> >
> > And then there was one person who admitted that while he was just a
> > user, he insisted he had a right to weigh in the issue. They
> > certainly have the right to have that belief, of course. Whether or
> > not maintainers are obliged to cater to people with those beliefs is a
> > very different question, however.
> >
> > There seems to be an assumption that a open, public discussion will
> > always give you the best review. I don't think that's necessarily
> > true. It can often give you a very biased sample from the poeple who
> > are most stridently on one side of the debate or the other, as well as
> > being biased towards those who believe in the "last post wins" style
> > of debate, since they end up speaking most loudly and posting most
> > frequently and most aggressively.
>
> I think it's interesting to note that ksummit-discuss seemed to be a
> much more fruitful list for discussion than LKML in this matter. Would
> we benefit from a non-technical mailing list to accompany LKML?
> Something less "seasonal" than ksummit-discuss.
Or could it be because the list is less known by the general public, and thus
not as targeted by trolls ? Maybe I'm being overly negative there, a new
mailing list might help. We would need to make sure to get people to subscribe
(yet another mailing list...), but on the other hand the much lower traffic
compared to LKML might help regain people who are not subscribed to or just
don't read LKML.
> Could also restrict posting to subscribers only, with public archives,
> and limit subscribers to, say, people in MAINTAINERS and/or some (fairly
> low) number of required commits in the past years.
Limiting subscription to MAINTAINERS would in my opinion keep out too many
people with a real interest and useful feedback to provide. Limiting it to
contributors would be better, even if possibly too limiting. We could
experiment with that though and see how it works out.
In any case, if we want to restrict list subscription (or at least post
rights) to kernel community members, we will need to answer the elephant in
the room question: who is the kernel community ?
> I presume ksummit-discuss had fairly good signal-to-noise because it's not
> well known or publicized.
I should have read your whole e-mail before writing the reply :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-11-13 19:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 0:04 [Ksummit-discuss] " James Bottomley
2018-11-09 0:29 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2018-11-09 3:30 ` [Ksummit-discuss] " Chris Mason
2018-11-09 17:52 ` Shuah Khan
2018-11-09 19:03 ` Theodore Y. Ts'o
2018-11-09 19:23 ` Joe Perches
2018-11-10 21:21 ` Theodore Y. Ts'o
2018-11-10 21:47 ` Joe Perches
2018-11-12 17:15 ` James Morris
2018-11-09 20:17 ` [Ksummit-discuss] better hot-topic discussion processes was: " Jason Cooper
2018-11-10 19:26 ` Chris Mason
2018-11-10 21:55 ` Jason Cooper
2018-11-14 18:25 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-09 19:54 ` [Ksummit-discuss] [Tech-board-discuss] " Frank Rowand
2018-11-10 19:15 ` Chris Mason
2018-11-10 21:59 ` Jason Cooper
2018-11-11 3:18 ` Frank Rowand
2018-11-11 5:57 ` Theodore Y. Ts'o
2018-11-12 4:44 ` NeilBrown
2018-11-12 4:54 ` NeilBrown
2018-11-12 17:00 ` Steven Rostedt
2018-11-13 16:49 ` Jani Nikula
2018-11-13 19:59 ` Laurent Pinchart [this message]
2018-11-14 17:28 ` Mark Brown
2018-11-09 17:19 ` [Ksummit-discuss] " Stephen Hemminger
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=2027180.eEsTsxCshK@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.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