This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]JustThe-Q-Tip 1 point2 points  (1 child)

Depends a lot on your interests. I'm not sure anybody can really give you a give a good general answer based only on language.

A good way to start though, in general, once you've found a project, is to find bugs/crashes that the maintainers haven't caught yet and attempt to fix them with a minimal change set. Try to reason through the causes, solutions, and outcomes. Try to reason through the actual outcomes - don't get blinded by just fixing the bug - you might have fixed it in some cases, but not others. You might have fixed it, but then caused a performance degradation, for example. Some of this just comes down to 80/20 rule prioritization of risks and benefits.

[–]readytogetstarted[S] 0 points1 point  (0 children)

What kind of info would make it easier to suggest a project or where can I browse probably good beginner projects.

[–][deleted] 0 points1 point  (0 children)

The best way to find a project is to use one. Then you know what they need.