Hi Mohit > Do we have a central page for the students where they can see which > FOSS project can be taken up by them (Which were taken up by their > seniors in last 3-5 years) so that they can develop technical skills > and contribute to FOSS projects while they are still in their first to > final year of academic degree/PG course.
In my opinion, you should contribute to a project that you use frequently. Only then will you have a passion to contribute and also a vision for the future of the project (e.g: you can come up with good feature ideas to add because you are a user). Any good you do to the project comes back to you in return! You merely scratch your own itch and benefit several other people around the world (and yourself). As far as the entry level goes -- I have noticed one problem with most people -- they don't know where to start with the project's codebase. FOSS Project codebases are so large, that it is very difficult to find out where you must start. My way around this is that most FOSS projects are written in good English -- If a variable does something, its name reflects it properly. You won't have meaningless int a; or class FooBar obj; in the code, unless it is very obvious as to how it will be used. This way, I read code that is relevant to my problem at hand, understand it "locally", and work on it. I don't think anyone needs to have deep knowledge of languages etc while making bugfixes, so that's the best place to start. Regards Akarsh
-- l...@iitd - http://tinyurl.com/ycueutm
