Codeberg Projects
This document outlines Codeberg's projects and the teams responsible for running them, together with points of contact.
If you are unsure where to start or wish to start a project of your own with other people, feel free to join the Contributing to Codeberg Matrix chat.
Active Software Projects
Forgejo
Forgejo is a self-hosted lightweight software forge. It is hosted on Codeberg and it is also what powers Codeberg.org. If you are missing something on Codeberg's Git hosting platform, it might be a good idea to improve it in Forgejo. Forgejo's team is largely separate to that of Codeberg and has many of its own teams together with documentation oriented towards developers.
- Contact: #forgejo:matrix.org
- Stack: Go, CSS, JavaScript, UI/UX, translations
Codeberg Pages
- Contact: #gitea-pages-server:matrix.org
- Stack: Rust
- Comment: We're writing a new pages server from scratch, as the current one is being retired.
Note that the repository for the new server is not yet public, as it is still in early stages of development.
Registration Server
The registration server, as seen on join.codeberg.org, is what Codeberg's backing non-profit uses to process membership applications.
- Contact: Issue Tracker, @momar
- Stack: Writing, Go, HTML
cibot
This bot is used to process some requests made for gaining access to Codeberg's Woodpecker CI instance automatically, alongside human reviewers.
- Maintainer: @xenrox
- Stack: Go
Community Projects
These projects do not necessarily require coding experience, but benefit from other things like community management, writing or Public Relations Experience.
Public Relations
Codeberg has a working group for matters involving Public Relations—some of us are deeply involved with Codeberg's day-to-day operations, others of us have experience in putting words together for projects and group efforts like ours.
We proofread and author blog posts for Codeberg's blog, as well for our social media accounts.
- Contact: As the group is loosely defined for the time being, please open an issue in our issue tracker if you're interested! (Alternatively, contact @n0toose!)
- Skills: Technical writing, public communication, collaborative writing. Some general involvement with Codeberg is quite helpful, but optional.
Policy
Orchestrating a platform with thousands of users takes effort—rules, policies, dealing with bureaucracy, connecting with other nonprofits in our field and legal inquiries are far from the technical tasks one would expect from nerds, but is slowly turning into a necessity.
If you have experience with public communications, association politics or have knowledge in European legal frameworks, we would love to have you on board. We are not certain whether we want to make an organized team or just form connections and reach out when needed, but either way, we would love to hear from you.
- Contact:
contact [ät] codeberg.orgor @n0toose
Documentation
When people have questions, they often consult docs.codeberg.org first. Although authoring documentation is stereotypically unattractive for developers, we believe that this is very high-impact work that could always use more help and contributions.
Some of Codeberg's Core team members regularly check the repository for new pull requests. We would be happy to have more active maintainers on board.
- Contact: #codeberg-documentation:matrix.org at Matrix
- Skills: Technical writing, JavaScript, static site generators
Community Issue Tracker Maintenance
The Community issue tracker is an asynchronous place for community members to request assistance from other community members.
It needs help in the following areas:
- Responding to inquiries by users.
- Triaging (i.e. labeling issues)
- Forwarding reports to other repositories (e.g. creating feature requests for Forgejo)
Event Calendar
- Maintainers: None. Looking for maintainers and event organizers!
- Contact: Contributing to Codeberg Matrix Channel
Matrix Spaces
Matrix Spaces are collections of chatrooms. Contact one of us you wish to add your room or space to the Projects on Codeberg Matrix space.
Codeberg CI Reviewers
Codeberg runs an instance of Woodpecker CI, but, to gain access to it, one has to issue requests on https://codeberg.org/Codeberg-e.V./requests. A reviewer (or a bot) check the linked repositories for ToS compliance then give access. Given Codeberg's growth, handling requests like this helps the site's administration focus on other tasks.
The requirement to join is an e. V. membership, as such requests are seen as official requests by the non-profit. The process is documented and the commitment is low; members are only expected to react to requests that they come across in their notifications if they feel like it.
- Contact: @gedankenstuecke, @martins-avots
- Backup contacts: @n0toose, @gusted
- Members: @6543, @crapStone, @dawe, @gusted, @mikolaj, @yodbha, @achill, @detpikachu, @gedankenstuecke, @christiano, @g-rppl, @H4K1, @hexaitos, @JavierVilarroig, @kbruen, @mark-pitblado, @martins-avots, @pat-s, @sophieforrest
- Organization: @Codeberg-CI-Reviewers
IRC chatrooms
Apart from Matrix, some members of our community meet on Libera Chat (in the #codeberg channel).
We are currently looking for moderators.
Infrastructure Projects
Some of these require certain access levels to Codeberg's infrastructure. If you are interested and commit a certain amount of time, this can surely be talked about. Please see the "Requirements" and "Comment" sections.
In case of upstream projects, maintaining the service also includes collecting and forwarding bug reports to upstream development.
Many of the scripts that we use to host Codeberg can be found in a specially designated organization.
Codeberg Pages
- Status: Being retired, a replacement server is being worked on.
- Contact: Repository
- Requirements: Some call to build trust
Weblate
- Status: Co-maintainers welcome
- Contact: Matrix: #codeberg-translate:bubu1.eu
- Requirements: Some call to build trust
Woodpecker CI
- Status: Co-maintainers very welcome
- Contact: #codeberg-ci:obermui.de
- Requirements: Some call to build trust, maybe some LXC/Docker experience
Status Page / Monitoring
- Status: Co-maintainers and innovations welcome
- Contact: ?
- Requirements: Some call to build trust
Codeberg's Forgejo instance
- Status: OK, but contributions welcome
- Contact: Repository
- Requirements: Access to production machines limited to very trustworthy people
- Comment: Suggestions (e.g. config improvements, new features etc) and some assistance when investigating issues welcome
Hardware, Ceph, MariaDB
- Status: Experience welcome
- Contact: Skillsharing here
- Requirements: Access to production machines limited to very trustworthy people
- Comment: Feel free to work with us on specific issues, and become a regular maintainer over time
Text is available under the Creative Commons Attribution 4.0 International License; additional terms may apply.