2009/6/2 patrick keshishian <pkesh...@gmail.com>: > On Mon, Jun 1, 2009 at 7:05 PM, PP2P3P5P=P8P9 P.P=P0P: <e.yu...@gmail.com> wrote: >> Hi! >> Personally, i think this is a really good question, because there are many >> people, who are just starting up, and they could be of some help, if they >> knew what to do. I think it would be a great idea of having a general list of >> what needs to be done > > You mean something like the bug database?
Yes, but the tracker is about bugs, there is no such category as enhancement proposal. Maybe, just include such "class"? And i feel there still is a need for a list of what needs to be done, and who is responsible (think most active developers) for what subsystem. That will bring more openness to the development process, and it actually helps. OpenBSD was the first one to have public anon cvs. Having such tools is a normal way of communication in a big open source project, isn't it? Don't get me wrong, i'm not requesting or demanding anything, i'm just throwing me ideas, hoping it would help the community become involved. I know many (three to four, actually ;)) happy OpenBSD users, who would love to contribute, but they don't know where to start with. Reading code that already exist, then writing some new - that's how it always works, but when you are unexperienced and just want to give it a try it really helps when someone points out what to do for you, so you just have to find a way to do it. It's also always good to know that someone needs your code, your work, not that it will be thrown away, it helps motivating. People are all different, and for some of them this is important. Also, one brain is good, ten are much better, so if by any chance i can get an experienced kernel hacker review my idea before i actually code it, i would greatly appreciate that. Am i completely wrong and should shut up? I'm fine with it, just tell me, thanks for your time! -- The best the little guy can do is what the little guy does right
