Alternatively, perhaps 'Kernel Janitor' is the wrong way to put it. In
my mind, two of the big wins for OpenBSD are the documentation, and the
fact that the system is but together as a whole, kernel and binaries.
Whilst the kernel itself may be too high a jumping-off point for
inexperienced people, might some of the simpler bits of userspace be a
gentler introduction?
One thing I have noted on the commit list, is the number of commits of
documentation/comment typo fixes, bringing things in line with style(9),
and the like. I will freely admit that I can't code for toffee, but I am
an experienced proofreader, and I can generally pick my way through
existing code and follow what it does. If there were a list of 'These
man pages need proofreading', or 'These source files could do with a
style(9) audit', I could (and would, oh dear...) give hours of my time
to the project.
I would hope that proofreading-type tasks would require minimal
hand-holding from the experienced devs, barring looking at completed
diffs and giving feedback. I would not wish to take away any time from
those more capable than I, but I do believe with a small amount of
assistance I and people like me could make a contribution.
With respect to 'Foolproof guides for new engineers', if anyone is
considering such a thing I would happily help lay them out and collate
them. Perhaps you don't want engineers who would like a foolproof guide
though? :-)
