Hi Brandon!

that's another interesting question I have been asking myself for some years now. I've always tried finding a good book about FreeBSD's internal online (something updated), I never really bumped into any updated ones [4.x something maybe?], most books out there were mainly for sysadmins and for the developers' guide .. nada. (atleast for me, am not a really good developper who could just keep tons in the head, if i need something to change i'll just find /usr/local/src|xargs grep 'whatineed' and from there figure what to change and do it pretty much with trial and error).

I believe a really good source and api documentation project would help a lot :p (user level/admin docs are already perfect for FreeBSD). but with the amount of people we can have for that a complete source documentation can definitely do a lot of good and no harm. Someone just needs to break every section up and assign a piece /section to be documented.

A bit like this book : http://blog.rlove.org/2010/07/linux-kernel-development-third-edition.html [reading that just made me confident enough to know which is which and what does what internally in linux and even a layman like me was able to know what to modify where].

We lack such good development guides for FreeBSD.

I believe such a project would require only that long time developpers to break the tasks as in set what architecturally stands where, and assigns the 'read the code and figure it out what each piece does' to other people, e.g people who can understand codes but doesn't have much of a clue of the internal api and way of doing things. ( I'll take myself for example while i do code, i can read code, but unless something is assigned, i don't really know what to do and ends up doing other things. /*some people are lazy, unless given something to do*/)

wanted to mention that also.