* [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers
@ 2014-05-02 19:42 Jiri Kosina
2014-05-02 20:04 ` Johannes Berg
2014-05-02 20:33 ` John W. Linville
0 siblings, 2 replies; 3+ messages in thread
From: Jiri Kosina @ 2014-05-02 19:42 UTC (permalink / raw)
To: ksummit-discuss
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?
--
Jiri Kosina
SUSE Labs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers
2014-05-02 19:42 [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers Jiri Kosina
@ 2014-05-02 20:04 ` Johannes Berg
2014-05-02 20:33 ` John W. Linville
1 sibling, 0 replies; 3+ messages in thread
From: Johannes Berg @ 2014-05-02 20:04 UTC (permalink / raw)
To: Jiri Kosina; +Cc: ksummit-discuss
On Fri, 2014-05-02 at 21:42 +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?
I don't know about that, but I'm pretty far removed and have been
wondering if it's too *deep*, since a pull request from me to John to
DaveM to Linus can take a very long time to actually get into the
tree ...
This gets to the point where sometimes shortly before the merge window
opens I don't even bother sending fixes to the current tree any more but
just put them into the -next branch marked Cc stable, which has Greg
(rightfully) complaining that there shouldn't be so much stable material
coming into the tree in the merge window since presumably most of that
wasn't actually *developed* in that time)
johannes
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers
2014-05-02 19:42 [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers Jiri Kosina
2014-05-02 20:04 ` Johannes Berg
@ 2014-05-02 20:33 ` John W. Linville
1 sibling, 0 replies; 3+ messages in thread
From: John W. Linville @ 2014-05-02 20:33 UTC (permalink / raw)
To: Jiri Kosina; +Cc: ksummit-discuss
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@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-02 21:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-02 19:42 [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers Jiri Kosina
2014-05-02 20:04 ` Johannes Berg
2014-05-02 20:33 ` John W. Linville
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox