tlambert2 at mindspring.com
Sat Jun 28 01:01:50 PDT 2003
"Simon L. Nielsen" wrote:
> On 2003.06.27 16:10:13 -0700, Joshua Oreman wrote:
> > I currently have a lot of free time and I was wondering whether there was
> > a TODO list of some sort for bugs that need fixing in FreeBSD. I really
> > want to help the project, and I think such a list would make it much
> > easier to do so. If there's no official TODO list, could someone point
> > out some things? I know C/C++, but I'm very unfamiliar with the kernel.
> Great :-) There is always plenty to do. I would suggest looking at the
> PR system and at the 'Contributing to FreeBSD' article which can be
> found at
> Hope you find something interesting to spend some time on.
Give him a commit bit, and he can quickly grind through all the
PR's that already have diff's attached to them, and have just sat
there forever. All he'd need to do was verify that there was a
problem that was being fixed, and the code didn't look like it
would cause damage. If it ends up causing damage anyway, the fix
can always be backed out later. Making send-pr actually result in
code changes would probably be the most valuable thing anyone could
do for the project, and it would give him a chance to read and to
understand a lot of diverse code, in the process, to get up to speed
on writing his own fixes for PR's without fixes attached.
Just my $0.02...
More information about the freebsd-hackers