# Codeberg

Community-operated Git hosting for projects aligned with a nonprofit free-software mission.

ID: codeberg
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/codeberg/

## Why: the goal or problem

A public cycling tool helps riders find quieter routes. Volunteers improve its openly licensed code. They want a nonprofit free-software community to operate collaboration instead of maintaining their own server.

## How: work toward a solution

Publish an eligible project on Codeberg. A contributor forks it, proposes a route-display fix and opens a pull request. Project maintainers review and merge; Codeberg’s operators maintain the hosting service.

## What: the concept

Codeberg is a nonprofit community service powered by Forgejo and built around Git. Gitea is software you can operate yourself. Check project eligibility and resource policies; community hosting is not a promise of unlimited resources.

[Source](https://docs.codeberg.org/getting-started/what-is-codeberg/)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

The deciding priority is a nonprofit free-software community operating the service. GitHub may fit an existing contributor network; Gitea fits owning your instance. Codeberg uses Forgejo, a separate software project. Compare review workflow, integrations, service policies and migration needs; nonprofit operation does not guarantee every requested feature.

## Applications

Cycling volunteers collaborate on the route tool’s code through forks and PRs. Project maintainers decide which changes to merge; service operators keep the collaboration platform running. The example concerns code, not uploading private ride traces. Its public license and purpose must fit the service’s rules.

## Implementation & cautions

Read current eligibility, private-content and resource policies before creating a project. Check automation and storage suitability for real workloads rather than assuming unlimited free capacity. Retain a recovery and migration plan: Git history, issue discussions and service configuration are different records. Test the destination’s import support if moving.

## Evidence

- [Codeberg: What is Codeberg?](https://docs.codeberg.org/getting-started/what-is-codeberg/) — Nonprofit community-operated service, free-software mission and Forgejo distinction. (Checked: 2026-09-27)
- [Codeberg FAQ](https://docs.codeberg.org/getting-started/faq/) — Project suitability and service-use constraints. (Checked: 2026-09-27)
- [Codeberg: Pull requests and Git flow](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/) — Branch, fork and pull-request collaboration. (Checked: 2026-09-27)