From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> To: Kees Cook <keescook@chromium.org> Cc: ksummit-discuss@lists.linuxfoundation.org, Linux Media Mailing List <linux-media@vger.kernel.org> Subject: Re: [Ksummit-discuss] single maintainer profile directory (was Re: [PATCH] media: add a subsystem profile documentation) Date: Tue, 17 Sep 2019 10:28:17 -0300 [thread overview] Message-ID: <20190917102817.263517b5@coco.lan> (raw) In-Reply-To: <201909162032.F4462D3@keescook> Hi Kees, Em Mon, 16 Sep 2019 20:35:45 -0700 Kees Cook <keescook@chromium.org> escreveu: > On Fri, Sep 13, 2019 at 01:19:21PM -0300, Mauro Carvalho Chehab wrote: > > Document the basic policies of the media subsystem profile. > > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> > > --- > > > > That's basically a modified version of: > > https://patchwork.linuxtv.org/patch/52999/ > > > > Applied to the new template > > > > Documentation/media/index.rst | 1 + > > .../media/maintainer-entry-profile.rst | 140 ++++++++++++++++++ > > One idea I proposed to Dan at the Maintainer's Summit was to collect all > the profiles is a single directory in Documentation/, No matter where the profiles will physically be stored, its contents belong to subsystem-specific documentation, and should be visible at the same index file as the kAPI docs is located, as anyone interested on submitting patches for a subsystem should be aware about the subsystem specific policies and details. So, my vote is to store them at Documentation/*/<subsystem> (together with the kAPI book). > since there are > two ways someone would want to read profiles: > > 1) a single profile, based on a MAINTAINERS entry which includes the path That is the common case. The problem is that the MAINTAINERS file currently doesn't generate html output. This is not a problem for "old school" devs, but a newbie wanting to collaborate to a single specific subsystem may not notice - or understand - the importance of the MAINTAINERS file[1]. [1] btw, that's why I submitted a RFC, several years ago, a patch converting it to ReST - and later - another patch that would be parsing its contents and producing a ReST output. That's, by far, the most relevant usecase for the profiles, as the audience is the ~4k Kernel developers. > 2) all of them, to study for various reasons I suspect that only core people will have interest on study them. Those people are more skilled, and can easily find all those files with a simple grep: $ grep "^P:\s" MAINTAINERS|cut -d':' -f2- or $ git grep "^P:\s" MAINTAINERS|cut -d: -f3- If, for whatever reason, he would prefer an HTML output [1], he could even create an index file with all of those with something like: $ for i in $(grep "^P:\s" MAINTAINERS|cut -d':' -f2-); do j=${i/rst/html}; echo "<a href=\"$j\">$j</a><br/>"; done >Documentation/output/index_profiles.html We might, instead, teach the Documentation/Makefile to create something like the above, but, IMHO, that would just add more complexity to the build without a good reason. [1] I doubt that core devs would prefer seeing this in html form, but some variant of the above could be used, for example, to create symlinks for all profile docs into a "study" directory. > The #2 case is helped by having them all in one directory with a single > index.rst, etc. Then similar profiles are able to merge, etc. Thanks, Mauro _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> To: Kees Cook <keescook@chromium.org> Cc: Linux Media Mailing List <linux-media@vger.kernel.org>, ksummit-discuss@lists.linuxfoundation.org, Dan Williams <dan.j.williams@intel.com> Subject: Re: single maintainer profile directory (was Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation) Date: Tue, 17 Sep 2019 10:28:17 -0300 [thread overview] Message-ID: <20190917102817.263517b5@coco.lan> (raw) In-Reply-To: <201909162032.F4462D3@keescook> Hi Kees, Em Mon, 16 Sep 2019 20:35:45 -0700 Kees Cook <keescook@chromium.org> escreveu: > On Fri, Sep 13, 2019 at 01:19:21PM -0300, Mauro Carvalho Chehab wrote: > > Document the basic policies of the media subsystem profile. > > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> > > --- > > > > That's basically a modified version of: > > https://patchwork.linuxtv.org/patch/52999/ > > > > Applied to the new template > > > > Documentation/media/index.rst | 1 + > > .../media/maintainer-entry-profile.rst | 140 ++++++++++++++++++ > > One idea I proposed to Dan at the Maintainer's Summit was to collect all > the profiles is a single directory in Documentation/, No matter where the profiles will physically be stored, its contents belong to subsystem-specific documentation, and should be visible at the same index file as the kAPI docs is located, as anyone interested on submitting patches for a subsystem should be aware about the subsystem specific policies and details. So, my vote is to store them at Documentation/*/<subsystem> (together with the kAPI book). > since there are > two ways someone would want to read profiles: > > 1) a single profile, based on a MAINTAINERS entry which includes the path That is the common case. The problem is that the MAINTAINERS file currently doesn't generate html output. This is not a problem for "old school" devs, but a newbie wanting to collaborate to a single specific subsystem may not notice - or understand - the importance of the MAINTAINERS file[1]. [1] btw, that's why I submitted a RFC, several years ago, a patch converting it to ReST - and later - another patch that would be parsing its contents and producing a ReST output. That's, by far, the most relevant usecase for the profiles, as the audience is the ~4k Kernel developers. > 2) all of them, to study for various reasons I suspect that only core people will have interest on study them. Those people are more skilled, and can easily find all those files with a simple grep: $ grep "^P:\s" MAINTAINERS|cut -d':' -f2- or $ git grep "^P:\s" MAINTAINERS|cut -d: -f3- If, for whatever reason, he would prefer an HTML output [1], he could even create an index file with all of those with something like: $ for i in $(grep "^P:\s" MAINTAINERS|cut -d':' -f2-); do j=${i/rst/html}; echo "<a href=\"$j\">$j</a><br/>"; done >Documentation/output/index_profiles.html We might, instead, teach the Documentation/Makefile to create something like the above, but, IMHO, that would just add more complexity to the build without a good reason. [1] I doubt that core devs would prefer seeing this in html form, but some variant of the above could be used, for example, to create symlinks for all profile docs into a "study" directory. > The #2 case is helped by having them all in one directory with a single > index.rst, etc. Then similar profiles are able to merge, etc. Thanks, Mauro
next prev parent reply other threads:[~2019-09-17 13:28 UTC|newest] Thread overview: 227+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-11 15:48 [Ksummit-discuss] [PATCH v2 0/3] Maintainer Entry Profiles Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 15:48 ` [Ksummit-discuss] [PATCH v2 1/3] MAINTAINERS: Reclaim the P: tag for Maintainer Entry Profile Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-13 15:37 ` [Ksummit-discuss] " Mauro Carvalho Chehab 2019-09-13 15:37 ` Mauro Carvalho Chehab 2019-09-13 15:37 ` Mauro Carvalho Chehab 2019-09-11 15:48 ` [Ksummit-discuss] [PATCH v2 2/3] Maintainer Handbook: " Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 17:34 ` [Ksummit-discuss] " Verma, Vishal L 2019-09-11 17:34 ` Verma, Vishal L 2019-09-16 12:35 ` Jani Nikula 2019-09-16 12:35 ` Jani Nikula 2019-09-16 12:35 ` Jani Nikula 2019-10-01 13:55 ` Jonathan Corbet 2019-10-01 13:55 ` Jonathan Corbet 2019-10-01 13:55 ` Jonathan Corbet 2019-10-01 18:17 ` [Ksummit-discuss] " Martin K. Petersen 2019-10-01 18:17 ` Martin K. Petersen 2019-10-01 18:17 ` Martin K. Petersen 2019-11-07 20:13 ` [Ksummit-discuss] " Jonathan Corbet 2019-11-07 20:13 ` Jonathan Corbet 2019-11-07 20:13 ` Jonathan Corbet 2019-11-08 2:41 ` [Ksummit-discuss] " Dan Williams 2019-11-08 2:41 ` Dan Williams 2019-11-08 2:41 ` Dan Williams 2019-09-11 15:48 ` [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS: " Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 15:48 ` Dan Williams 2019-09-11 17:42 ` [Ksummit-discuss] " Vishal Verma 2019-09-11 17:42 ` Vishal Verma 2019-09-11 17:42 ` Vishal Verma 2019-09-11 17:45 ` Dave Jiang 2019-09-11 17:45 ` Dave Jiang 2019-09-11 18:43 ` [Ksummit-discuss] " Dan Carpenter 2019-09-11 18:43 ` Dan Carpenter 2019-09-11 18:43 ` Dan Carpenter 2019-09-11 22:11 ` Jens Axboe 2019-09-11 22:11 ` Jens Axboe 2019-09-11 22:11 ` Jens Axboe 2019-09-12 7:41 ` Dan Williams 2019-09-12 7:41 ` Dan Williams 2019-09-12 7:41 ` Dan Williams 2019-09-12 8:24 ` Miguel Ojeda 2019-09-12 8:24 ` Miguel Ojeda 2019-09-12 10:18 ` Joe Perches 2019-09-12 10:18 ` Joe Perches 2019-09-12 10:18 ` Joe Perches 2019-09-12 11:02 ` Joe Perches 2019-09-12 11:02 ` Joe Perches 2019-09-12 14:17 ` Dan Williams 2019-09-12 14:17 ` Dan Williams 2019-09-12 14:51 ` Joe Perches 2019-09-12 14:51 ` Joe Perches 2019-09-12 14:42 ` Miguel Ojeda 2019-09-12 14:42 ` Miguel Ojeda 2019-09-13 7:09 ` Jonathan Corbet 2019-09-13 7:09 ` Jonathan Corbet 2019-09-13 7:09 ` Jonathan Corbet 2019-09-13 11:48 ` Dan Carpenter 2019-09-13 11:48 ` Dan Carpenter 2019-09-13 11:48 ` Dan Carpenter 2019-09-13 12:18 ` Dan Williams 2019-09-13 12:18 ` Dan Williams 2019-09-13 12:18 ` Dan Williams 2019-09-13 15:00 ` Randy Dunlap 2019-09-13 15:00 ` Randy Dunlap 2019-09-13 15:00 ` Randy Dunlap 2019-09-13 15:46 ` Rob Herring 2019-09-13 15:46 ` Rob Herring 2019-09-13 15:46 ` Rob Herring 2019-09-13 16:42 ` Joe Perches 2019-09-13 16:42 ` Joe Perches 2019-09-13 16:42 ` Joe Perches 2019-09-13 19:32 ` Rob Herring 2019-09-13 19:32 ` Rob Herring 2019-09-13 19:32 ` Rob Herring 2019-09-13 17:57 ` Geert Uytterhoeven 2019-09-13 17:57 ` Geert Uytterhoeven 2019-09-13 17:57 ` Geert Uytterhoeven 2019-09-16 12:42 ` Jani Nikula 2019-09-16 12:42 ` Jani Nikula 2019-09-16 12:42 ` Jani Nikula 2019-09-17 16:16 ` Jason Gunthorpe 2019-09-17 21:59 ` Dan Williams 2019-09-17 21:59 ` Dan Williams 2019-09-17 21:59 ` Dan Williams 2019-09-13 21:44 ` Martin K. Petersen 2019-09-13 21:44 ` Martin K. Petersen 2019-09-13 21:44 ` Martin K. Petersen 2019-09-16 7:01 ` Dan Carpenter 2019-09-16 7:01 ` Dan Carpenter 2019-09-16 7:01 ` Dan Carpenter 2019-09-16 17:08 ` Martin K. Petersen 2019-09-16 17:08 ` Martin K. Petersen 2019-09-16 17:08 ` Martin K. Petersen 2019-09-16 17:15 ` Mark Brown 2019-09-16 17:15 ` Mark Brown 2019-09-13 2:11 ` Aneesh Kumar K.V 2019-09-13 2:11 ` Aneesh Kumar K.V 2019-09-13 5:00 ` Greg KH 2019-09-13 5:00 ` Greg KH 2019-09-11 20:30 ` Joe Perches 2019-09-11 20:30 ` Joe Perches 2019-09-11 20:30 ` Joe Perches 2019-09-13 16:19 ` [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation Mauro Carvalho Chehab 2019-09-13 16:19 ` Mauro Carvalho Chehab 2019-09-13 16:19 ` [Ksummit-discuss] " Mauro Carvalho Chehab 2019-09-17 3:35 ` [Ksummit-discuss] single maintainer profile directory (was Re: [PATCH] media: add a subsystem profile documentation) Kees Cook 2019-09-17 3:35 ` single maintainer profile directory (was Re: [Ksummit-discuss] " Kees Cook 2019-09-17 13:28 ` Mauro Carvalho Chehab [this message] 2019-09-17 13:28 ` Mauro Carvalho Chehab 2019-09-17 16:33 ` [Ksummit-discuss] single maintainer profile directory (was " Kees Cook 2019-09-17 16:33 ` single maintainer profile directory (was Re: [Ksummit-discuss] " Kees Cook 2019-09-18 11:23 ` [Ksummit-discuss] single maintainer profile directory (was " Mauro Carvalho Chehab 2019-09-18 11:23 ` Mauro Carvalho Chehab 2019-09-18 17:39 ` Kees Cook 2019-09-18 17:39 ` Kees Cook 2019-09-18 18:35 ` Mauro Carvalho Chehab 2019-09-18 18:35 ` Mauro Carvalho Chehab 2019-09-21 19:13 ` Jonathan Corbet 2019-09-21 19:13 ` Jonathan Corbet 2019-09-21 19:45 ` Mauro Carvalho Chehab 2019-09-21 19:45 ` Mauro Carvalho Chehab 2019-09-23 22:45 ` Kees Cook 2019-09-23 22:45 ` Kees Cook 2019-09-18 12:36 ` [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation Laurent Pinchart 2019-09-18 12:36 ` Laurent Pinchart 2019-09-18 13:57 ` Mauro Carvalho Chehab 2019-09-18 13:57 ` Mauro Carvalho Chehab 2019-09-18 17:27 ` Laurent Pinchart 2019-09-18 17:27 ` Laurent Pinchart 2019-09-18 18:48 ` Mauro Carvalho Chehab 2019-09-18 18:48 ` Mauro Carvalho Chehab 2019-09-19 7:08 ` Dan Carpenter 2019-09-19 7:08 ` Dan Carpenter 2019-09-20 5:29 ` Joe Perches 2019-09-20 5:29 ` Joe Perches 2019-09-20 14:09 ` Daniel Vetter 2019-09-20 14:09 ` Daniel Vetter 2019-09-19 6:56 ` Dan Carpenter 2019-09-19 6:56 ` Dan Carpenter 2019-09-19 7:22 ` Geert Uytterhoeven 2019-09-19 7:22 ` Geert Uytterhoeven 2019-09-19 8:49 ` Jani Nikula 2019-09-19 8:49 ` Jani Nikula 2019-09-19 8:58 ` Geert Uytterhoeven 2019-09-19 8:58 ` Geert Uytterhoeven 2019-09-19 9:52 ` Jani Nikula 2019-09-19 9:52 ` Jani Nikula 2019-09-20 14:53 ` Laurent Pinchart 2019-09-20 14:53 ` Laurent Pinchart 2019-09-20 14:59 ` Doug Anderson 2019-09-20 14:59 ` Doug Anderson 2019-09-21 8:56 ` Jani Nikula 2019-09-21 8:56 ` Jani Nikula 2019-09-23 15:58 ` Doug Anderson 2019-09-23 15:58 ` Doug Anderson 2019-09-23 16:04 ` Jonathan Corbet 2019-09-23 16:04 ` Jonathan Corbet 2019-09-19 9:52 ` Mauro Carvalho Chehab 2019-09-19 9:52 ` Mauro Carvalho Chehab 2019-09-25 17:13 ` Joe Perches 2019-09-25 17:13 ` Joe Perches 2019-09-25 18:40 ` Kees Cook 2019-09-25 18:40 ` Kees Cook 2019-09-26 15:14 ` Joe Perches 2019-09-26 15:14 ` Joe Perches 2019-09-26 15:53 ` Kees Cook 2019-09-26 15:53 ` Kees Cook 2019-09-26 16:02 ` Joe Perches 2019-09-26 16:02 ` Joe Perches 2019-09-26 16:24 ` Kees Cook 2019-09-26 16:24 ` Kees Cook 2019-09-26 10:25 ` Geert Uytterhoeven 2019-09-26 10:25 ` Geert Uytterhoeven 2019-09-18 13:59 ` [Ksummit-discuss] [PATCH v2] " Mauro Carvalho Chehab 2019-09-18 13:59 ` Mauro Carvalho Chehab 2019-09-18 14:07 ` André Almeida 2019-09-18 14:11 ` [Ksummit-discuss] " Mauro Carvalho Chehab 2019-09-18 14:11 ` Mauro Carvalho Chehab 2019-09-11 16:40 ` [Ksummit-discuss] [PATCH v2 0/3] Maintainer Entry Profiles Martin K. Petersen 2019-09-11 16:40 ` Martin K. Petersen 2019-09-11 16:40 ` Martin K. Petersen 2019-09-12 13:31 ` [Ksummit-discuss] " Bart Van Assche 2019-09-12 13:31 ` Bart Van Assche 2019-09-12 13:31 ` Bart Van Assche 2019-09-12 15:34 ` Joe Perches 2019-09-12 15:34 ` Joe Perches 2019-09-12 15:34 ` Joe Perches 2019-09-12 20:01 ` Bart Van Assche 2019-09-12 20:01 ` Bart Van Assche 2019-09-12 20:01 ` Bart Van Assche 2019-09-12 20:34 ` Joe Perches 2019-09-12 20:34 ` Joe Perches 2019-09-12 20:34 ` Joe Perches 2019-09-13 14:26 ` Rob Herring 2019-09-13 14:26 ` Rob Herring 2019-09-13 14:26 ` Rob Herring 2019-09-13 18:42 ` Joe Perches 2019-09-13 18:42 ` Joe Perches 2019-09-13 18:42 ` Joe Perches 2019-09-13 19:17 ` Mauro Carvalho Chehab 2019-09-13 19:17 ` Mauro Carvalho Chehab 2019-09-13 19:17 ` Mauro Carvalho Chehab 2019-09-13 20:33 ` Joe Perches 2019-09-13 20:33 ` Joe Perches 2019-09-13 20:33 ` Joe Perches 2019-09-13 12:56 ` Matthew Wilcox 2019-09-13 12:56 ` Matthew Wilcox 2019-09-13 13:54 ` Mauro Carvalho Chehab 2019-09-13 13:54 ` Mauro Carvalho Chehab 2019-09-13 13:54 ` Mauro Carvalho Chehab 2019-09-13 14:59 ` Guenter Roeck 2019-09-13 14:59 ` Guenter Roeck 2019-09-13 14:59 ` Guenter Roeck 2019-09-13 22:03 ` Martin K. Petersen 2019-09-13 22:03 ` Martin K. Petersen 2019-09-13 22:03 ` Martin K. Petersen 2020-04-29 13:55 ` Roman Bolshakov 2020-04-29 13:55 ` Roman Bolshakov 2019-09-12 13:10 ` Bart Van Assche 2019-09-12 13:10 ` Bart Van Assche 2019-09-12 13:10 ` Bart Van Assche
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=20190917102817.263517b5@coco.lan \ --to=mchehab+samsung@kernel.org \ --cc=keescook@chromium.org \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-media@vger.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: linkBe 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.