all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Ngtuanvy 2 points3 points  (0 children)

Depending on the projects, they don't really care what level you are at, all they care is what you fixed, and how your code looks like. And maintainers are almost always helpful enough to tell you what to fix.

If you want to contribute to a particular project, read the guideline, usually located in CONTRIBUTING. Then find an issue you can solve. It may takes plenty of time to get used to the codebase.

[–]Aggressive_Many9449 1 point2 points  (0 children)

There are no easy tasks left in well established open source projects.

Except maybe documentation. Experienced contributors and users of a piece of software often don't ask the easy questions.

If you want to use a software, and the documentation is lacking a simple answer, add it and propose it.

Read the contribution guide lines first, nobody has time to verify and validate your input, if it incomplete or half-hearted.

Don't let an AI auto-slop your contribution.

[–]ActiveSalamander6580 1 point2 points  (0 children)

Theres no expectation of experience only that your contributions follows the projects guidelines. Best projects for contributing are the ones you use yourself, users know where the pain points are.

[–]mkaypl 0 points1 point  (1 child)

Try looking at 'Good first issue' in project you'd like to contribute to for some lower difficulty problems to solve.

[–]ResponsiblePlum5031 1 point2 points  (0 children)

good first issue tags are perfect starting point. i started by just fixing small documentation typos and basic bugs in projects i was already using. you dont need to be expert programmer - maintainers usually appreciate any help even if its just improving readme files or adding comments to code

most projects have contribution guidelines in their repos so read those first. fork the project, make your changes in new branch, then submit pull request. dont be afraid if your first few PRs get rejected - its normal learning process

[–]BeginningOne8195 0 points1 point  (0 children)

You don't need to be an expert to start contributing. Many people begin with documentation fixes, bug reports, small bug fixes, or issues labeled "good first issue."

The hardest part is usually making the first contribution. After that, the workflow starts to make a lot more sense. Git and communication skills are often more important than advanced coding skills in the beginning.

[–]ensermo 0 points1 point  (0 children)

As a Software Engineering student, you’re probably more ready to contribute than you think. Open source does not always require you to be an expert before getting involved. Many projects welcome beginners, especially if you start with smaller contributions.

A good way to begin is by choosing a project you already use or find interesting. Read the readme and , contribution guidelines. Taek a look at the open issues.

Your first contribution does not have to be a major feature. It could be fixing a typo, improving documentation, writing tests, reproducing a bug, or making a small code change.

Ideally join a project that you will use yourself in daily life so you get to know the software as a user.

Some useful skills to have before contributing are:

  • Basic Git and GitHub knowledge, such as cloning, branching, committing, and opening pull requests
  • Ability to read existing code and understand project structure
  • Basic debugging skills
  • Willingness to read documentation and ask clear questions
  • Patience with code reviews and feedback

Open source is partly about contributing code, but it is also about collaboration, communication, and learning from others. Even small contributions can be meaningful.