[Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers

John W. Linville linville at tuxdriver.com
Fri May 2 20:33:22 UTC 2014


On Fri, May 02, 2014 at 09:42:12PM +0200, Jiri Kosina wrote:
> Is our tree too flat? This might turn into just a question to Linus than 
> really a discussion topic.
> 
> It seems to me (and it has been the case for a few past years, so it's 
> probably not an issue at the end of the day) like there are many places 
> where we are violating a natural tree-like hierarchy our development model 
> has, with many people sending pull requests directly to Linus instead of 
> going through sub-maintainers. Is this really a problem? If so, how to 
> deal with it?

Probably only Linus can decide if the maintainer tree is too flat.
That would largely be reflected in his own feelings about "free time",
his capacity for "big picture" stuff, etc -- I won't speculate too
much on that.  Still, it probably is a good idea to ensure a certain
amount of depth both for maintaining everyone's sanity and for insuring
against the 'eaten by raptors' problem.

The wireless tree that I run feeds up to Dave Miller rather than going
to Linus.  I also have a number of trees that others maintain and push
through me, including the mac80211 and bluetooth trees among others.
I'm not sure how many people are in the position I am in, although
I suspect that there are a few more around than there used to be?
Anyone?  Bueller?

Adding levels to the maintainer tree can introduce some problems,
of course.  Merging latency is probably obvious, as well as simple
matters like making sure everyone manages their trees in a compatible
way for merging operations.  There are many ways to use git, and some
cause problems for up- or down-stream trees...

Anyway, I'd love to see more of a discussion here.

John

P.S.  It's always good to see an early topic where I feel like an
expert... :-)
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


More information about the Ksummit-discuss mailing list