The release of the collaborative development platform Forgejo 8.0 has been published, which has completely separated from the Gitea system into a self-sufficient project since February (previously, Forgejo developed as a synchronized fork). The project allows users to deploy a system for collaborating on Git repositories, similar to GitHub, Bitbucket, and GitLab. The fork was created in 2022 following attempts to commercialize Gitea and the transfer of management to a commercial company. Forgejo continues to apply principles of independent management and community oversight. The project code is written in Go and is distributed under the MIT license. Under Forgejo, operates hosting Codeberg.org.
Key features of the platform include low resource consumption (it can be used on a Raspberry Pi or inexpensive VPS) and a straightforward installation process. Standard project management capabilities are provided, such as task management, issue tracking, pull requests, a wiki, tools for coordinating developer groups, release preparation, package deployment automation in repositories, access rights management, integration with continuous integration platforms, code search, authentication via LDAP and OAuth, repository access via SSH and HTTP/HTTPS protocols, webhooks integration for Slack, Discord, and other services, support for Git hooks and Git LFS, as well as tools for repository migration and mirroring. The use of the ActivityPub protocol for connecting individual projects in a federated network is also notable. servers developers in a federated network.
Key Changes:
- Work has been done to remove non-free dependencies. In the web interface implementation for rendering a chart of the most active participants, a non-free JavaScript library, GSAP, was used. In the new version, the code linked to this library has been replaced with a new implementation using the chart.js library.
Additionally, the audit revealed two more components with incompatible licenses, used for supporting the APA (American Psychological Association) citation format and in the experimental engine for rendering flowcharts based on the elkjs library. Support for the APA format has been temporarily removed (it is recommended to use the more common BibTeX format), and the elkjs engine has been excluded from the Mermaid library.
- The ability to manually invoke action handlers with user-defined data through the web interface has been provided.
- By default, the option allowing users to self-register on the platform is disabled during installation (only administrators can add users). It is expected that this change will reduce the number of unmonitored installations that allow spammers to add their accounts.
- The capability to hide files and archives automatically generated for releases in the interface has been introduced to prevent confusion with user-uploaded archives (for instance, in some projects, the archive with the source code for a release is uploaded separately by developers and differs from the automatically generated one).
- A policy has been approved to minimize random changes to the user interface, which aims for the interface to evolve as much as possible without disrupting the established order based on user needs and analysis of their work, rather than on unverified assumptions that a particular change would be beneficial.
- Support for Microsoft SQL Server has been discontinued due to the problematic integration of proprietary systems into automated testing tools (which would lead to Forgejo's dependency on non-free software, contradicting the project's principles) and the absence of users utilizing Forgejo on Microsoft SQL Server.
- The ability to upgrade to Forgejo 8 from systems based on Gitea 1.21 and newer releases has been introduced.
Source: opennet.ru
