All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Jiang, Dave" <dave.jiang@intel.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"Verma, Vishal L" <vishal.l.verma@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"zwisler@kernel.org" <zwisler@kernel.org>
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Sun, 18 Nov 2018 09:12:54 +0200	[thread overview]
Message-ID: <20181118071254.GG24359@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20181116033947.5689b51c@silica.lan>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Fri, Nov 16, 2018 at 03:39:47AM -0800, Mauro Carvalho Chehab wrote:
> Em Thu, 15 Nov 2018 11:43:51 -0800
> Joe Perches <joe@perches.com> escreveu:
>
> > On Thu, 2018-11-15 at 19:40 +0000, Luck, Tony wrote:
> > > > I would recommend to remove this section at all.
> > > > New maintainers won't come out of blue, but will be come
> > > > from existing community and such individuals for sure will see
> > > > and judge by themselves to whom they trust and to whom not.
> > >
> > > Perhaps this is more of a hint to contributors than to maintainers
> > > (see earlier discussion on who is the target audience for these documents).
> > >
> > > It would help contributors know some names of useful reviewers (and
> > > thus this list should be picked up by scripts/get_maintainer.pl to help
> > > the user compose Cc: lists for e-mail patches).
> >
> > Trusted reviewers should be specifically listed
> > in the MAINTAINERS file with an "R:" entry.
> >
> > get_maintainers should not look anywhere else.
>
> I know that making get_maintainers to look elsewhere can make it more
> complex and slower, but IMHO, by having a per-subsystem profile, this is
> unavoidable.
>
> The thing is that touching at a single MAINTAINERS file every time a new
> reviewer comes is painful. Also, MAINTAINERS file format doesn't allow
> adding free text explaining the criteria for someone to become a
> reviewer.

You are pointing to the actual problem -> someone needs to maintain such
lists, Removal of persons from that list won't be easy task too.

>
> IMO, having reviewers on a per-subsystem file, where one could explain
> the criteria for being added there will make easier to attract more
> reviewers.
>
> Cheers,
> Mauro

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leon@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Joe Perches <joe@perches.com>, "Luck, Tony" <tony.luck@intel.com>,
	"Jiang, Dave" <dave.jiang@intel.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"Verma, Vishal L" <vishal.l.verma@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"zwisler@kernel.org" <zwisler@kernel.org>
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Sun, 18 Nov 2018 09:12:54 +0200	[thread overview]
Message-ID: <20181118071254.GG24359@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20181116033947.5689b51c@silica.lan>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Fri, Nov 16, 2018 at 03:39:47AM -0800, Mauro Carvalho Chehab wrote:
> Em Thu, 15 Nov 2018 11:43:51 -0800
> Joe Perches <joe@perches.com> escreveu:
>
> > On Thu, 2018-11-15 at 19:40 +0000, Luck, Tony wrote:
> > > > I would recommend to remove this section at all.
> > > > New maintainers won't come out of blue, but will be come
> > > > from existing community and such individuals for sure will see
> > > > and judge by themselves to whom they trust and to whom not.
> > >
> > > Perhaps this is more of a hint to contributors than to maintainers
> > > (see earlier discussion on who is the target audience for these documents).
> > >
> > > It would help contributors know some names of useful reviewers (and
> > > thus this list should be picked up by scripts/get_maintainer.pl to help
> > > the user compose Cc: lists for e-mail patches).
> >
> > Trusted reviewers should be specifically listed
> > in the MAINTAINERS file with an "R:" entry.
> >
> > get_maintainers should not look anywhere else.
>
> I know that making get_maintainers to look elsewhere can make it more
> complex and slower, but IMHO, by having a per-subsystem profile, this is
> unavoidable.
>
> The thing is that touching at a single MAINTAINERS file every time a new
> reviewer comes is painful. Also, MAINTAINERS file format doesn't allow
> adding free text explaining the criteria for someone to become a
> reviewer.

You are pointing to the actual problem -> someone needs to maintain such
lists, Removal of persons from that list won't be easy task too.

>
> IMO, having reviewers on a per-subsystem file, where one could explain
> the criteria for being added there will make easier to attract more
> reviewers.
>
> Cheers,
> Mauro

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leon@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Joe Perches <joe@perches.com>, "Luck, Tony" <tony.luck@intel.com>,
	"Jiang, Dave" <dave.jiang@intel.com>,
	"ksummit-discuss@lists.linuxfoundation.org" 
	<ksummit-discuss@lists.linuxfoundation.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"Verma, Vishal L" <vishal.l.verma@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"zwisler@kernel.org" <zwisler@kernel.org>
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Sun, 18 Nov 2018 09:12:54 +0200	[thread overview]
Message-ID: <20181118071254.GG24359@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20181116033947.5689b51c@silica.lan>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Fri, Nov 16, 2018 at 03:39:47AM -0800, Mauro Carvalho Chehab wrote:
> Em Thu, 15 Nov 2018 11:43:51 -0800
> Joe Perches <joe@perches.com> escreveu:
>
> > On Thu, 2018-11-15 at 19:40 +0000, Luck, Tony wrote:
> > > > I would recommend to remove this section at all.
> > > > New maintainers won't come out of blue, but will be come
> > > > from existing community and such individuals for sure will see
> > > > and judge by themselves to whom they trust and to whom not.
> > >
> > > Perhaps this is more of a hint to contributors than to maintainers
> > > (see earlier discussion on who is the target audience for these documents).
> > >
> > > It would help contributors know some names of useful reviewers (and
> > > thus this list should be picked up by scripts/get_maintainer.pl to help
> > > the user compose Cc: lists for e-mail patches).
> >
> > Trusted reviewers should be specifically listed
> > in the MAINTAINERS file with an "R:" entry.
> >
> > get_maintainers should not look anywhere else.
>
> I know that making get_maintainers to look elsewhere can make it more
> complex and slower, but IMHO, by having a per-subsystem profile, this is
> unavoidable.
>
> The thing is that touching at a single MAINTAINERS file every time a new
> reviewer comes is painful. Also, MAINTAINERS file format doesn't allow
> adding free text explaining the criteria for someone to become a
> reviewer.

You are pointing to the actual problem -> someone needs to maintain such
lists, Removal of persons from that list won't be easy task too.

>
> IMO, having reviewers on a per-subsystem file, where one could explain
> the criteria for being added there will make easier to attract more
> reviewers.
>
> Cheers,
> Mauro

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2018-11-18  7:12 UTC|newest]

Thread overview: 173+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  4:53 [Ksummit-discuss] [RFC PATCH 0/3] Maintainer Handbook: Subsystem Profile Dan Williams
2018-11-15  4:53 ` Dan Williams
2018-11-15  4:53 ` Dan Williams
2018-11-15  4:53 ` [Ksummit-discuss] [RFC PATCH 1/3] MAINTAINERS: Reclaim the P: tag for " Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  5:39   ` [Ksummit-discuss] " Mauro Carvalho Chehab
2018-11-15  5:39     ` Mauro Carvalho Chehab
2018-11-15  5:39     ` Mauro Carvalho Chehab
2018-11-15 20:12     ` Joe Perches
2018-11-15 20:12       ` Joe Perches
2018-11-15 20:12       ` Joe Perches
2018-11-15  4:53 ` [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: " Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  5:48   ` [Ksummit-discuss] " Julia Lawall
2018-11-15  5:48     ` Julia Lawall
2018-11-15  5:48     ` Julia Lawall
2018-11-15  7:59     ` Geert Uytterhoeven
2018-11-15  7:59       ` Geert Uytterhoeven
2018-11-15  7:59       ` Geert Uytterhoeven
2018-11-15 13:47       ` Julia Lawall
2018-11-15 13:47         ` Julia Lawall
2018-11-15 13:47         ` Julia Lawall
2018-11-16 12:44         ` Jani Nikula
2018-11-16 12:44           ` Jani Nikula
2018-11-16 12:44           ` Jani Nikula
2018-11-16 17:56           ` Joe Perches
2018-11-16 17:56             ` Joe Perches
2018-11-16 17:56             ` Joe Perches
2018-11-17 14:12             ` Rob Herring
2018-11-17 14:12               ` Rob Herring
2018-11-17 14:12               ` Rob Herring
2018-11-17 17:03               ` Julia Lawall
2018-11-17 17:03                 ` Julia Lawall
2018-11-17 17:03                 ` Julia Lawall
2018-11-20  7:28             ` Jani Nikula
2018-11-20  7:28               ` Jani Nikula
2018-11-20  7:28               ` Jani Nikula
2018-11-15  5:49   ` Mauro Carvalho Chehab
2018-11-15  5:49     ` Mauro Carvalho Chehab
2018-11-15  5:49     ` Mauro Carvalho Chehab
2018-11-15  7:58   ` Geert Uytterhoeven
2018-11-15  7:58     ` Geert Uytterhoeven
2018-11-15  7:58     ` Geert Uytterhoeven
2018-11-15  8:38   ` Jani Nikula
2018-11-15  8:38     ` Jani Nikula
2018-11-15  8:38     ` Jani Nikula
2018-11-15 18:03     ` Tim.Bird
2018-11-15 18:03       ` Tim.Bird
2018-11-15 18:03       ` Tim.Bird
2018-11-15 23:56     ` Tobin C. Harding
2018-11-15 23:56       ` Tobin C. Harding
2018-11-15 23:56       ` Tobin C. Harding
2018-11-15 15:44   ` Mauro Carvalho Chehab
2018-11-15 15:44     ` Mauro Carvalho Chehab
2018-11-15 15:44     ` Mauro Carvalho Chehab
2018-11-16 23:28     ` Randy Dunlap
2018-11-16 23:28       ` Randy Dunlap
2018-11-16 23:28       ` Randy Dunlap
2018-11-17 11:57     ` Hans Verkuil
2018-11-17 11:57       ` Hans Verkuil
2018-11-17 11:57       ` Hans Verkuil
2018-11-16  0:11   ` Frank Rowand
2018-11-16  0:11     ` Frank Rowand
2018-11-16  0:11     ` Frank Rowand
2018-11-16 12:04     ` Mauro Carvalho Chehab
2018-11-16 12:04       ` Mauro Carvalho Chehab
2018-11-16 12:04       ` Mauro Carvalho Chehab
2018-11-16 18:57       ` Dan Williams
2018-11-16 18:57         ` Dan Williams
2018-11-16 18:57         ` Dan Williams
2018-11-18 12:58         ` Mauro Carvalho Chehab
2018-11-18 12:58           ` Mauro Carvalho Chehab
2018-11-18 12:58           ` Mauro Carvalho Chehab
2018-11-18 17:31           ` Dan Williams
2018-11-18 17:31             ` Dan Williams
2018-11-18 17:31             ` Dan Williams
2018-11-18 17:31             ` Dan Williams
2018-11-18 17:31               ` Dan Williams
2018-11-18 17:31               ` Dan Williams
2018-11-18 17:34               ` Dan Williams
2018-11-18 17:34                 ` Dan Williams
2018-11-18 17:34                 ` Dan Williams
2018-11-18 17:44                 ` Mauro Carvalho Chehab
2018-11-18 17:44                   ` Mauro Carvalho Chehab
2018-11-18 17:44                   ` Mauro Carvalho Chehab
2018-11-16 16:47     ` Frank Rowand
2018-11-16 16:47       ` Frank Rowand
2018-11-16 16:47       ` Frank Rowand
2018-11-15  4:53 ` [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: " Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  4:53   ` Dan Williams
2018-11-15  8:03   ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-15  8:03     ` Geert Uytterhoeven
2018-11-15  8:03     ` Geert Uytterhoeven
2018-11-15 14:10     ` Mauro Carvalho Chehab
2018-11-15 14:10       ` Mauro Carvalho Chehab
2018-11-15 14:10       ` Mauro Carvalho Chehab
2018-11-15 16:20       ` Leon Romanovsky
2018-11-15 16:20         ` Leon Romanovsky
2018-11-15 19:09         ` Mauro Carvalho Chehab
2018-11-15 19:09           ` Mauro Carvalho Chehab
2018-11-15 19:35           ` Leon Romanovsky
2018-11-15 19:35             ` Leon Romanovsky
2018-11-15 19:40             ` Luck, Tony
2018-11-15 19:40               ` Luck, Tony
2018-11-15 19:40               ` Luck, Tony
2018-11-15 19:43               ` Joe Perches
2018-11-15 19:43                 ` Joe Perches
2018-11-15 19:43                 ` Joe Perches
2018-11-16 11:39                 ` Mauro Carvalho Chehab
2018-11-16 11:39                   ` Mauro Carvalho Chehab
2018-11-16 11:39                   ` Mauro Carvalho Chehab
2018-11-18  7:12                   ` Leon Romanovsky [this message]
2018-11-18  7:12                     ` Leon Romanovsky
2018-11-18  7:12                     ` Leon Romanovsky
2018-11-16 11:33             ` Mauro Carvalho Chehab
2018-11-16 11:33               ` Mauro Carvalho Chehab
2018-11-16 12:00               ` Jan Kara
2018-11-16 12:00                 ` Jan Kara
2018-11-16 12:00                 ` Jan Kara
2018-11-18  7:00               ` Leon Romanovsky
2018-11-16 20:36         ` Rodrigo Vivi
2018-11-16 20:36           ` Rodrigo Vivi
2018-11-16 20:36           ` Rodrigo Vivi
2018-11-16 23:44           ` Dan Williams
2018-11-16 23:44             ` Dan Williams
2018-11-16 23:44             ` Dan Williams
2018-11-17  0:38             ` NeilBrown
2018-11-17  0:38               ` NeilBrown
2018-11-18 13:11               ` Mauro Carvalho Chehab
2018-11-18 13:11                 ` Mauro Carvalho Chehab
2018-11-18 13:11                 ` Mauro Carvalho Chehab
2018-11-18 13:03             ` Mauro Carvalho Chehab
2018-11-18 13:03               ` Mauro Carvalho Chehab
2018-11-18 13:03               ` Mauro Carvalho Chehab
2018-11-20  8:10               ` Jani Nikula
2018-11-20  8:10                 ` Jani Nikula
2018-11-20 19:31                 ` Dan Williams
2018-11-20 19:31                   ` Dan Williams
2018-11-20 19:31                   ` Dan Williams
2018-11-26 11:12                 ` Mauro Carvalho Chehab
2018-11-26 11:12                   ` Mauro Carvalho Chehab
2018-11-26 11:12                   ` Mauro Carvalho Chehab
2018-11-26 15:55                   ` Joe Perches
2018-11-26 15:55                     ` Joe Perches
2018-11-26 15:55                     ` Joe Perches
2018-11-16 19:13     ` Dan Williams
2018-11-16 19:13       ` Dan Williams
2018-11-16 19:13       ` Dan Williams
2018-11-15 14:30   ` Mauro Carvalho Chehab
2018-11-15 14:30     ` Mauro Carvalho Chehab
2018-11-15 14:30     ` Mauro Carvalho Chehab
2018-11-15 14:51     ` Julia Lawall
2018-11-15 14:51       ` Julia Lawall
2018-11-15 14:51       ` Julia Lawall
2018-11-16 19:20     ` Dan Williams
2018-11-16 19:20       ` Dan Williams
2018-11-16 19:20       ` Dan Williams
2018-11-16  2:58   ` y-goto
2018-11-16  2:58     ` y-goto
2018-11-16  2:58     ` y-goto
2018-11-17  0:32   ` [Ksummit-discuss] " David Woodhouse
2018-11-17  0:32     ` David Woodhouse
2018-11-15  5:56 ` [Ksummit-discuss] [RFC PATCH 0/3] Maintainer Handbook: " Mauro Carvalho Chehab
2018-11-15  5:56   ` Mauro Carvalho Chehab
2018-11-15  5:56   ` Mauro Carvalho Chehab
2018-11-25 10:57 ` [Ksummit-discuss] " Pavel Machek
2018-11-25 10:57   ` Pavel Machek
2018-11-25 20:55   ` [Ksummit-discuss] " Dan Williams
2018-11-25 20:55     ` Dan Williams
2018-11-25 20:55     ` Dan Williams

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=20181118071254.GG24359@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=vishal.l.verma@intel.com \
    --cc=zwisler@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.