On Sat, Nov 03, 2007 at 12:16:50PM +0100, Karel Kulhavy wrote: > On Wed, Oct 31, 2007 at 09:49:03AM -0600, Theo de Raadt wrote: > > > > surely there must be _some_ merit to creating a list of lower level > > > > development tasks (as dictated by those with experience to judge) to > > > > encourage people to enter the development cycle. > > > > > > The most amusing thing about this thread is that such a list has been > > > published for years (it's somewhat short right now, but there's some > > > simple stuff in it) and is the first search hit when you search on one > > > of the obvious queries on google. > > > > Surely they are too busy whining at us for lists, to actually search > > for the lists. > > > > I'll say it again more clearly -- all of you whiners just plain suck. > > Who do you mean with whiners? People who report bugs? Those people save you > work, because instead of having to run time-consuming tests to find the > problems, you just rake the problem reports in from these people.
The problem is that people have limited spare time to look into OpenBSD matters, and these threads often don't result in much happening. Sending bug reports and such information is of course useful, but isn't related to the discussion at hand. > > > We know you'll never write diffs, and it is up to you to prove us > > I fixed some bugs in BRL-CAD (a 30 year old oldschool C-only 3D modelling > system from the US Army) because BRL-CAD people are friendly and helpful. > Instead of "you suck", they tell you "this XX you wrote cannot work because of > YY". > > I asked here for janitor list, got a reply that it doesn't exist. I looked > into the PR database into documentation section but there were 0 hits. I > looked > into other sections but that seemed to be complicated, I don't want to invest > significant time into learning OpenBSD internals at the moment. Try fix something that bothers you, that is the way most people get involved. In terms of kernel code, drivers are mostly seperate from everything else and don't require an understanding of all the internals to work on.
