Re: [patch 0/2] Documentation/process: Add subsystem/tree handbook

["Theodore Y. Ts'o" <tytso@mit.edu>]

On Thu, Nov 08, 2018 at 09:33:47AM -0700, Jonathan Corbet wrote:
> 
> > I thought there was a slot already scheduled on the refereed track,
> > "Towards a Linux Kernel Mainainer Handbook" (Tuesday at 4:45pm) for
> > this purpose?
> 
> My expectation is that this will be an actual talk; it seemed rude to
> assume that Dan had penciled in a block of time for open arguments about
> the tip-tree handbook :)  That said, I'm not feeling a groundswell of
> support for scheduling another session at this point...

Agreed, my apologies to Dan for making that presumption.  My reasoning
for suggesting that his session might be a good one is that many of
the things which are listed as "tip-tree quirks" are things which I
suspect we are discovering are actually things that should go into the
Maintainer Handbook.

I don't know how much time Dan was planning on presenting versus
having a discussion.  If there is a lot of discussion that gets kicked
up, that's why we have TBD/Unconference slots.  (And yes, there may be
conflicts; sorry about that.  On the other hand, better that people
are frustrated that there are too many high quality sessions they want
to attend, as opposed to twiddling their fingers and saying, "well
*this* afternoon is a complete waste of my time."  :-)

I suspect the main places where there will be divergencies between
different trees might be in how individual subsystems weigh various
recommendations when they come into conflict with each other.  We've
seen that already with checkpatch.pl, where in fact the choices about
"lines > 80 characters always BAD BAD BAD" versus "continuation
strings in printk EVEN WORSE" have flipped over time (and so now we
have cleanup patches being submitted which undo the work of different
cleanup patches years earlier :-).  And I have no doubt that this will
be true for things that might go into tree-specific quirks versus
Maintainer Handbook.

In fact, what might make sense is for Maintainer Handbook to have the
general recommendations, and then maybe tree-specific quirks document
might simply say that in terms of the Frobozz tree weighs the
suggestions of guideline Foo over guideline Quux, where as the
Frobnozz tree has a the opposite weighting.

Cheers,

						- Ted