[Ksummit-discuss] "Maintainer summit" invitation discussion

[Daniel Vetter]

[Back from a bit of vacation, so I'm just jumping into the middle of
the cross-subsystem/invariant topic branch discussion. I read all the
other mails, but this seems most relevant.]

On Tue, Apr 25, 2017 at 11:10 AM, Lee Jones <lee.jones at linaro.org> wrote:
> Although common place, immutable branches are still treated as the
> last resort.  If patches can be taken via their respective subsystem
> trees without fear of disruption, they are.  Contributors often
> attempt to have their *new* cross-subsystem functionality taken in via
> a single tree (requiring an immutable branch), purely because it's
> convenient and the merge-time becomes deterministic, but we do not
> allow that unless there are hard/unavoidable build-time dependencies.

Honest question, why exactly?

At a quick ignorant glance this seems to trade contributor time
against maintainer time, which in my opinion means you should ramp up
your maintainer training and mentoring to have much more maintainer
time available and make contributing to upstream more attractive. But
drm != other subsystems, I'd like to hear more of why you picked this
tradeoff.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch