OpenSource Together

Command Palette

Search for a command to run...

Journey illustration

Getting Started with
Open Source

Your trusted partner for taking your project from closed to open.

This guide will help you understand the fundamentals, prepare your project, and release it publicly with confidence.

Why Go Open Source?

Open source is more than code — it's a mindset. When you make your project open, you:

Encourage transparency and collaboration

Attract contributors and grow a community

Build credibility for your work or product

Create opportunities for learning and visibility

Your Open Source Experience

Step 1

Assess Readiness

Before going public, review your repository and make sure it's ready to be shared.

Quick checklist

  • Your code is clean and free of sensitive data (API keys, credentials, etc.)
  • You've removed all private or company-specific information
  • The documentation is understandable by someone outside your team
  • The project builds and runs without internal dependencies
  • You've discussed ownership and licensing with your team
Tip: A "clean repo" builds trust. Review your commit history and configuration files before opening the project.
Step 2

Choose the Right License

A license defines how others can use, modify, and distribute your code. Without one, your project is not legally open source.

Popular choices

MIT

Simple and permissive. Ideal for personal and startup projects.

Apache 2.0

Adds patent protection. Common for corporate or large-scale use.

GPLv3

Requires derivatives to remain open. Used for community-driven tools.

Once selected, create a file named LICENSE at the root of your repository.

Step 3

Document Everything

Good documentation is the heart of a healthy open-source project. It lowers the entry barrier for newcomers and encourages contributions.

Essential files to include

README.md

The face of your project. Explains what it is, how to use it, and why it matters.

CONTRIBUTING.md

Guides people on how to propose changes or new features.

CODE_OF_CONDUCT.md

Defines acceptable behavior in your community.

SECURITY.md

Explains how to report vulnerabilities responsibly.

Optional but recommended: add issue and pull request templates in .github/.

Step 4

Structure Your Repository

A clear structure helps others explore and contribute confidently.

Example layout

my-project/
├── src/
├── tests/
├── docs/
├── README.md
├── LICENSE
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
└── SECURITY.md

Keep it simple. The goal is clarity — not complexity.

Step 5

Build for Collaboration

Once your project is public, you're not just sharing code — you're inviting people to join your journey.

Best practices

  • Use Issues and Pull Requests on GitHub to manage contributions
  • Label beginner-friendly tasks with tags like 'good first issue'
  • Automate checks (linting, tests) to maintain quality
  • Be kind and responsive — community health starts with communication
"Open source is not about perfection. It's about progress through collaboration."
Step 6

Manage Security & Maintenance

Opening your code also means maintaining it responsibly.

Recommendations

  • Add a SECURITY.md file with a private contact for disclosures
  • Regularly review dependencies for vulnerabilities
  • Automate tests and CI/CD if possible
  • Communicate updates clearly through releases or changelogs
Responsible open source means balancing transparency with safety.
Step 7

Share and Grow

Your open-source journey doesn't end with the release — it starts there.

  • Announce your project on social media and developer platforms
  • Tag your repo with relevant topics (e.g., 'open-source', 'nextjs', 'community')
  • Engage with early contributors — they are your first advocates
  • Consider joining the OST Verified Program for visibility and recognition

Additional Resources

Build your projects,
find your contributors

Highlighting ambitious open source projects to offer them an initial wave of visibility, committed contributors and support.