On 04/19/10 13:02, Christiano F. Haesbaert wrote:
I know this has been discussed before, yet I call for your attention.
This post seems like a genuine attempt on getting pointers on starting
hacking in OpenBsd. I remember doing the same a while ago.
How about having a very simple per-developer(or project) wish-list/todo-list ?
I guess this would encourage people to code, usually the first step is
the hardest after you code some stuff you can can usually walk by
yourself.
For example, Claudio once said that not needing a route for multicast
addresses would be nice, but that's somewhere on the mailing lists
archives so very few people are aware of that, having it explicit in a
todo-list could speed things up IMHO.
I also know he (as every developer) is busy with more important
things, so "publishing" these small tasks would also give the
developers more time to focus on the big/important issues.
No, I'm not trolling, just an idea.
You are going to get a negative response. Which is too bad.
We all have to start somewhere.
OpenBSD kernel plus userland plus ports is a really big playing field.
It is also a very big field of different skills of many kinds.
I have seen "Stop your whining and submit a patch!" a few hundred times
at least on this list.
I recently "whined" about something I saw as broken, trying to be
helpful. When that wasn't enough, I spent several hours figuring out
what was needed in two ports to get their man pages and also figured out
that their perldocs were also broken. It was harder than I thought, but
I learned many little pieces of information. I was able to submit a
patch for each one, and was able to get a fix upstream on another, my
patch was used upstream.
Pretty small potatoes, but I did it because I "knew" something was
broken. Us newbies NEED to know what is broken AND is at our level to
learn how to fix. I needed more help submitting a correct diff than with
fixing the actual problem. I did not need anyone to help me patch!
