Drew DeVault, author of the user environment and email client , about the implementation of a project hub in his developed collaborative development platform . Developers can now create projects that multiple services, as well as browse existing projects and search among them.
The SourceHut platform is notable for its ability to fully operate without JavaScript, high performance, and organization of work in the form of mini-services in a Unix style. The functionality of a project in SourceHut is formed by separate components that can be combined and used individually, for example, just tickets or just code without a mandatory tie to repositories with tickets. The ability to freely combine resources makes it difficult to determine which resources belong to a project. The project hub solves this problem and allows all project-related information to be gathered in one place. For instance, on a single project page, one can now include a general description and list the repositories, issue tracking sections, documentation, support channels, and mailing lists that belong to the project.
For integration with external platforms, an API and a system for connecting web handlers (webhooks) are provided. Additionally, SourceHut supports wikis, continuous integration systems, email-based discussions, tree-like viewing of mailing list archives, change reviews via the web, and the ability to add annotations to code (attaching links and documentation). Besides Git, Mercurial is also supported. The code is written in Python and Go, and under the GPLv3 license.
it is possible to create public, private, and hidden repositories with a flexible access control system that allows participation in development even from users without local accounts (authentication via OAuth or participation by email). For informing and coordinating vulnerability fixes, a system of private issue reports is provided. Emails sent by each service are encrypted and verified using PGP. Two-factor authentication using one-time TOTP keys is applied for login. Detailed audit logging is maintained for incident analysis.
The built-in continuous integration infrastructure allows
the execution of automated builds in virtual environments on various Linux and BSD systems. Direct transfer of build jobs to CI without storing them in a repository is allowed. Build results are displayed in the interface, sent to email, or transmitted via webhook. For debugging failures, connection to the build environments via SSH is possible.
At the current stage of development, Sourcehut operates faster than competing services, for instance, pages with summary information, commit lists, change logs, code views, issues, and file trees open 3-4 times faster than GitHub and GitLab, and 8-10 times faster than Bitbucket. It is worth noting that Sourcehut has not yet exited the alpha development stage, and many planned features are still unavailable. For instance, there is currently no web interface for merge requests (a merge request is created by submitting a ticket and attaching a link to the forked branch in Git). Another downside is the unusual interface, which may not be familiar to GitHub and GitLab users, but it is simple and immediately understandable.
Source: opennet.ru
