Projects

Overview of Codeberg Projects and their status. Help in mostly every domain greatly appreciated.

The goal of this is to give a clearer overview of different responsibilities at Codeberg, including a separation of teams if possible.

Please understand that projects at Codeberg are usually moving independent of each other, giving them maximum flexibility under the umbrella of Codeberg. This also means: If you feel like one project is not working the way you want, either consider joining the team, or discussing the matter in the Community Issue Tracker.

Description of fields:

• Status: [active, inactive] + [working, partly limitations, not working] explains if a project is active and making progress or not
• Maintainers: How many (x/y determine that there might not be as many as wanted)? Enough?
• Discussion: links to project communication hubs (mainly chats)
• Limitations: Is there a restriction determining if you can help?
• Stack: Which experiences could come handy?

Software Projects

Forgejo

• Status: active, working
• Members: Own governance
• Discussion: #forgejo:matrix.org
• Limitations: none, feel free to join!
• Comments: Nice collaboration and progress!
• Stack: Go, Less, JavaScript

Codeberg Pages

• Status: active, partly working
• Maintainers: 2 (see README), more human power welcome
• Discussion: #gitea-pages-server:matrix.org
• Limitations: none, feel free to join!
• Comments: There is an overwhelming problem with stability which the existing team is not able to tackle
• Stack: Go

Moderation / Administration Systems

• Status: inactive, not working
• Maintainers: 1+ (strategic decisions outstanding)
• Limitations: none, feel free to join!
• Comments: We need to make strategic discussions how to continue with Forge federation. If you are interested to participate, please let us know.
• Stack: Go, TypeScript

Registration Server

• Status: inactive, partly working
• Maintainers: none! (help from Core members still expectable)
• Limitations: none, feel free to join!
• Comments: Changes in the data format that is incompatible with scripts that consume data downstream blocks current progress. Forming a team and discussing this with the member management team is appreciated.

Member Management + Bookkeeping

• Status: inactive, not working
• Maintainers: 1
• Limitations: The current codebase requires access to sensitive data, although this could be cleaned upon request
• Comments: Help appreciated
• Stack: PHP, Go, Python

Community Projects

These projects do not require coding experience in order to contribute.

Documentation

• Status: active, working
• Maintainers: some
• Discussion: #codeberg-documentation:matrix.org
• Limitations: none, feel free to join!
• Stack: Writing :), JavaScript

Community Issue Tracker Maintenance

Maintaining the public issue tracker and forwarding reports as appropriate.

• Status: active, mostly working
• Maintainers: some
• Limitations: none, feel free to join!

Contributing to Codeberg + Events

Managing contributions to various projects via the Matrix channel, and eventually organizing events like the Hackathon.

• Status: active, mostly working
• Maintainers: none (currently self-organized)
• Discussion: #contributing-to-codeberg:kle.li
• Limitations: none, feel free to join!

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 "Limitations" sections.

In case of upstream projects, maintaining the service also includes collecting and forwarding bug reports to upstream development.

Pages Server

Please see the initial Codeberg Pages team, who also care about the hosting.

Weblate

• Status: active, working
• Maintainers: 1 / 2
• Discussion: #codeberg-translate:bubu1.eu
• Limitations: requires access to the container (feel free to ask!)
• Stack: Debian GNU/Linux, Docker

Woodpecker CI

• Status: active, mostly working
• Maintainers: 1 / 2
• Discussion: #codeberg-ci:obermui.de
• Limitations: requires access to the container (feel free to ask!)
• Stack: Debian GNU/Linux, Docker, LXC

Code Search

• Status: not started yet
• Maintainers: none!
• Limitations: requires access to the container (feel free to ask!)
• Comment: Starting this project is appreciated. The core team will assist you and provide the computing resources necessary.

Forgejo

• Status: active, working
• Maintainers: 2 / 2
• Limitations: Granting more people access to the current core user data is currently not an option, sorry. Feel free to assist in the "Contributing to Matrix" channel, though, or asking as an e.V.-member.

Core Technical Infrastructure

• Status: active, mostly working
• Maintainers: 2 / 3
• Limitations: Access to root machines is currently preserved to elected members of Codeberg e.V., which have a legal obligation to work in line with the goals of the association.

Internal projects

For reference, these projects are managed internally by the Codeberg e.V..

End-User Support

• Status: not established
• Maintainers: none!
• Limitations: Currently either requires access to user data, or progress with the moderation tools. Please apply as a Codeberg member if you want to push this project forward.

Moderation

• Status: active, not fully working
• Maintainers: 10 members, few active
• Limitations: Applying for the role within Codeberg e.V. is necessary

Member Management

• Status: active, working
• Maintainers: 4 (board + presidium members)
• Limitations: Access to user data is preserved to elected members of Codeberg e.V., which have a legal obligation to work in line with the goals of the association.