Agreed.... I needed to peek OpenBSD code a couple months ago and found it extremely readable. Doing simple tasks can be a better path leading to new kernel engineers.
Just posting your task list on this list isn't a commitment to coach new developers, but can provide a solid material to start coding. Obviously patches will be subject to peer review. Even if a patch isn't approved, the coder should have learned something new and useful. On 10/30/07, n0g0013 <[EMAIL PROTECTED]> wrote: > On 30.10-20:26, Miod Vallat wrote: > > [ ... ] That's when you need as much support as possible. And > > that's the kind of support I, as an individual, can not provide. > > i believe the task list itself would be positive , even if not much > happens around it. they are good for the community as well as the > codebase. > > you are not commiting yourself to mentoring and tutoring every idiot > who wants a crack at the kernel, you're simply saying, "look if you > think you're good enough to do the work, here are some things that i > know, from my experience, need done". the learning and effort comes > from interested parties. this sort of delegation does work in other > projects, perhaps if we have a good list we can figure out how to make > it work here too. > > -- > t > t > w
