01. Getting Started

Start as a User Before You Contribute to Open Source

Your first Open Source step can be using the software. Learn how to try a project, notice friction, and turn that experience into helpful feedback.
Table of Contents
In: 01. Getting Started

If you are new to Open Source, it is easy to think your first step has to be writing code. It does not. One of the most useful ways to begin is to become a thoughtful user of an Open Source project.

Using the software helps you understand what it does, who it serves, where it is confusing, and what kind of help would actually matter. This is especially important for projects built for public benefit, such as education, accessibility, security, or civic tools. Software for Progress Foundation supports Open Source developers because useful software should reach the people who need it. That work starts with understanding the software from a real user’s point of view.


Using the software is part of Open Source

Open Source is not only a place where developers publish code. It is a way for people to share, improve, and sustain software in public. Some people maintain the code. Some write documentation. Some report bugs. Some answer questions. Some simply use the tool and explain what was hard to understand.

For a beginner, this is good news. You do not need permission to start learning. You can begin by finding a project, trying it carefully, and paying attention.

When you use a project first, you learn things that are hard to see from the code alone:

  • What problem the project is trying to solve.
  • Who the likely users are.
  • What setup steps are clear or confusing.
  • What features are easy to discover.
  • Where the project might exclude people because of language, cost, device limits, or accessibility barriers.

Those observations can become useful contributions later. But at the beginning, your job is simple: use the project with care.


Pick a project you can understand as a user

Your first project does not have to be famous. In fact, a smaller project may be easier to understand. Look for software where you can describe the purpose in one sentence.

For example:

  • An Open Source flashcard app for students studying vocabulary.
  • A browser extension that warns users about suspicious links.
  • A tool that helps people create accessible documents.
  • A civic website that explains local public meeting agendas.

Choose something where the public benefit is visible. If you care about education, try a learning tool. If you care about accessibility, try software that removes a barrier. If you care about security, try a tool that helps people stay safer online.

A good beginner project has a clear README, recent activity, and a way to report issues. You do not need to judge the whole codebase yet. You are only checking whether you can try the software and learn from the experience.


Try the project like a real person would

Once you choose a project, do not jump straight into fixing things. First, act like a new user.

  1. Read the project description.
  2. Find the installation or usage instructions.
  3. Follow the instructions exactly as written.
  4. Notice where you hesitate, guess, or get stuck.
  5. Try one common task the software is meant to support.

If the project is a web app, try creating an account only if that is required and appropriate. If it is a command-line tool, run the simplest example. If it is a library, try the shortest sample from the documentation.

The goal is not to prove you are smart. The goal is to see what a new user sees. Beginner confusion is not a personal failure. It is useful information.


Keep a beginner notebook

As you try the project, keep short notes. Do this before you open an issue or contact anyone. Your notes will help you separate facts from frustration.

Write down:

  • What you expected: “I expected the install command to start the app.”
  • What happened: “The command finished, but I did not know what to open next.”
  • Where you looked: “I checked the README and the docs folder.”
  • Your environment: “I used Windows 11, Firefox, and Node 22.”
  • What helped: “The screenshot on the homepage made the goal clear.”

This notebook does not need to be fancy. A text file is enough. The habit matters more than the tool.

Good notes turn a vague complaint into something maintainers can understand. Instead of saying “the docs are bad,” you can say, “I followed the setup section, but after step three I did not know which command launched the local server.” That is much easier to act on.


A concrete public benefit example

Imagine you try an Open Source tool that helps teachers create accessible worksheets. The tool lets a teacher upload a document and get suggestions for better headings, alt text, and reading order.

You follow the setup guide and get the app running. Then you try to create your first worksheet. You notice three things:

  • The README explains developer setup well, but does not show what a teacher should do first.
  • The button text says “Process,” but you are not sure whether it will change the file or only review it.
  • The results page uses color alone to show which items need attention.

You have not written code yet, but you have learned something valuable. A teacher with limited time might leave before understanding the tool. A color-only warning might create an accessibility barrier. A safer button label could reduce fear.

These are not abstract opinions. They connect directly to whether the software can help people. That is the heart of public benefit Open Source: useful tools must be understandable and reachable, not just technically available.


Turn your user experience into a first contribution

After you use the project and take notes, choose one small next step. Keep it modest. Beginners build trust by being specific and respectful.

You might:

  • Open an issue that describes one confusing setup step.
  • Suggest a clearer sentence for the README.
  • Report an accessibility barrier you observed.
  • Ask whether maintainers would welcome a small documentation pull request.
  • Share a reproducible bug with your environment details.

Do not send a long list of everything you think is wrong. Start with one useful observation. If maintainers respond, listen carefully. They may already know about the issue. They may have constraints you cannot see yet. They may point you to a better place to help.

Your first contribution is not a test of your worth as a developer. It is a first conversation with a project.


What to avoid when starting as a user

A thoughtful user is helpful. A demanding user can drain a project. Remember that many Open Source maintainers are volunteers or people working with limited support.

Avoid these beginner mistakes:

  • Do not demand a feature before understanding the project’s purpose.
  • Do not assume confusion means the maintainers did not care.
  • Do not report “it does not work” without details.
  • Do not compare the project harshly to a commercial product with a large team.
  • Do not offer to rewrite everything as your first interaction.

Instead, be clear, kind, and specific. That tone helps projects become more sustainable, because maintainers can act on your feedback without spending extra energy decoding it.


TL;DR

Your first Open Source step can be using the software. Pick a project with a purpose you understand, try it like a real user, and take notes on what is clear or confusing.

Then turn one observation into a small, respectful contribution. This is how beginners can help Open Source projects become more usable, accessible, and sustainable. Code matters, but so does the experience of the people the software is meant to serve.

Written By
Cory Fail
Cory Fail leads the Software for Progress Foundation, helping developers build Open Source tools for education, accessibility, and social good through mentorship and community support.
Comments
More From Software for Progress Foundation
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to Software for Progress Foundation.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.