Outreachy drivers/staging patch restrictions

Outreachy drivers/staging patch restrictions

[Alison Schofield]

Hi Greg, Hans,

We are preparing to kick off the next contribution period for
Outreachy Interns. (March 25 - April 22)

Last round we ran with one restriction:
>> Do not send patches for drivers/staging/media/atomisp

Hans handled drivers/staging/media (except for atomisp) and
Greg picked up all the rest.

Will that work in the upcoming round?
Anything else contributors should be aware of for this round?

Thanks for your support,
Alison

Re: Outreachy drivers/staging patch restrictions

[Hans Verkuil]

Hi Alison,

On 23/03/2022 17:48, Alison Schofield wrote:
> Hi Greg, Hans,
> 
> We are preparing to kick off the next contribution period for
> Outreachy Interns. (March 25 - April 22)
> 
> Last round we ran with one restriction:
>>> Do not send patches for drivers/staging/media/atomisp
> 
> Hans handled drivers/staging/media (except for atomisp) and
> Greg picked up all the rest.
> 
> Will that work in the upcoming round?

Actually, I think it is best to skip drivers/staging/media altogether.

I have a lot less time for code review this round, and in addition
the media staging drivers are usually not a good match for code cleanups:
usually they are either already in very good shape and just stuck
in staging because they are waiting for some missing core functionality,
or they are being deprecated.

Regards,

	Hans

> Anything else contributors should be aware of for this round?
> 
> Thanks for your support,
> Alison
> 

Re: Outreachy drivers/staging patch restrictions

[Alison Schofield]

On Wed, Mar 23, 2022 at 06:35:52PM +0100, Hans Verkuil wrote:
> Hi Alison,
> 
> On 23/03/2022 17:48, Alison Schofield wrote:
> > Hi Greg, Hans,
> > 
> > We are preparing to kick off the next contribution period for
> > Outreachy Interns. (March 25 - April 22)
> > 
> > Last round we ran with one restriction:
> >>> Do not send patches for drivers/staging/media/atomisp
> > 
> > Hans handled drivers/staging/media (except for atomisp) and
> > Greg picked up all the rest.
> > 
> > Will that work in the upcoming round?
> 
> Actually, I think it is best to skip drivers/staging/media altogether.
> 
> I have a lot less time for code review this round, and in addition
> the media staging drivers are usually not a good match for code cleanups:
> usually they are either already in very good shape and just stuck
> in staging because they are waiting for some missing core functionality,
> or they are being deprecated.

Got it. We'll restrict driver/staging/media completely.
Thanks for letting me know!

> 
> Regards,
> 
> 	Hans
> 
> > Anything else contributors should be aware of for this round?
> > 
> > Thanks for your support,
> > Alison
> > 
> 

Re: Outreachy drivers/staging patch restrictions

[Greg KH]

On Wed, Mar 23, 2022 at 09:48:15AM -0700, Alison Schofield wrote:
> Hi Greg, Hans,
> 
> We are preparing to kick off the next contribution period for
> Outreachy Interns. (March 25 - April 22)
> 
> Last round we ran with one restriction:
> >> Do not send patches for drivers/staging/media/atomisp
> 
> Hans handled drivers/staging/media (except for atomisp) and
> Greg picked up all the rest.
> 
> Will that work in the upcoming round?

Note that I am not on any outreachy mailing lists anymore, so the
interns will have to remember to properly cc: the staging list and me
and the other results of get_maintainer.pl.

And I agree, no drivers/staging/media/ changes please.  I just ignore
them all anyway :)

thanks,

greg k-h