Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1596384
| From | Stephen Warren <swarren@wwwdotorg.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: outreachy |
| Date | 2017-03-09 22:00 +0100 |
| Message-ID | <tjdke-1Wq-3@gated-at.bofh.it> (permalink) |
| References | <tjd0R-1Nu-3@gated-at.bofh.it> <tjdkd-1Wq-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 03/09/2017 01:51 PM, Scott Branden wrote: > Hi Julia, > > On 17-03-09 12:36 PM, Julia Lawall wrote: >> Hello, >> >> I discussed the issue of outreachy patches for bcm with Greg, and we are >> not convinced that not having the patches CCd to you is such a good idea. >> While we don't want to spam you with noise, some of the applicants are >> starting to make more significant changes that it could be useful for you >> to be aware of. >> >> Could we try a compromise where you are not CCd on whitespace patches, >> but >> you are CCd on patches that actually modify the code? > > All I'm asking is you work through your outreachy patches internal first > to get rid of the most basic mistakes and email traffic it is geerating. > Once that learning process is through then they can be sent out like > any other patches to the kernel mailing lists and maintainers. +1 from me too; I find these patches rather high volume and had to add a filter to keep them out of my primary inbox. I don't know what process is in place, but I would suggest: 1) Senders send everything to the outreachy list, where they are reviewed for basic issues, like learning to use git send-email, learning checkpatch, etc. In this case, only send the patch to the outreachy mailing list and nowhere else. 2) Once a patch has passed review there, then send the patch to the regular kernel mailing list just like any other patch; follow the output of get_maintainers.pl. We have something like (1) inside NVIDIA for new contributors and pre-upstreaming IP review. It helps all the newcomers, but without requiring anyone involved in (2) to change behaviour. The process I suggest is very much inline with the typically suggested "asking questions" process: (1) read docs yourself (2) ask local contacts for help, (3) start asking wider audiences for help.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
outreachy Julia Lawall <julia.lawall@lip6.fr> - 2017-03-09 21:40 +0100
Re: outreachy Scott Branden <scott.branden@broadcom.com> - 2017-03-09 22:00 +0100
Re: outreachy Stephen Warren <swarren@wwwdotorg.org> - 2017-03-09 22:00 +0100
Re: outreachy Greg KH <gregkh@linuxfoundation.org> - 2017-03-09 22:40 +0100
Re: outreachy Florian Fainelli <f.fainelli@gmail.com> - 2017-03-09 23:20 +0100
Re: outreachy Greg KH <gregkh@linuxfoundation.org> - 2017-03-10 07:10 +0100
csiph-web