Let me tell you a little secret — part of my success with OpenBSD has to do with the fact that I read their CVS commit logs.
Imagine if you could track every bug fix, every feature enhancement, every driver addition or every documentation change done by the OpenBSD developers ? Well, you can and it does not have to take up much of your time.
Every single change to the OpenBSD source tree is documented through their source-change mailing list and the OpenBSD project is kind enough to provide ordinary users with read-only access. You can follow the changes done to –CURRENT, the OpenBSD development branch, to see what’s going to be in the next release, to watch how developers tweak the performance of drivers or to learn about changes done to software that you rely on.
The list is low volume so it easy to follow and after a while you get to “know” the different developers. You will often see the same individuals commit changes to the same sections of the OpenBSD source tree, like pf, bgpd or certain network drivers. After a while you start to pay more attention to those developers that work with the parts of the source tree that interest you the most and follow their commits more closely.
I can only encourage people with an interest in OpenBSD to subscribe to the source-change mailing list. The knowledge gained from following that list has saved my butt more often then I like to admit and has prepared me for any changes in the upcoming release that might be of importance to me