Publish a post about Forgejo

This commit is contained in:
Konstantin Nazarov 2024-09-09 01:50:22 +01:00
parent 346db7677f
commit bbabd0844a
Signed by: knazarov
GPG key ID: 4CFE0A42FA409C22
2 changed files with 43 additions and 10 deletions

View file

@ -1,16 +1,10 @@
Subject: Projects
Open-source tools and projects: [git.sr.ht/~knazarov](https://git.sr.ht/~knazarov/)
Open-source tools and projects: [git.sr.ht/~knazarov](https://git.knazarov.com/knazarov)
Highlights:
* [My own programming language with a VM and garbage collector](https://git.sr.ht/~knazarov/valeri) (work in progress)
* [My own programming language with a VM and garbage collector](https://git.knazarov.com/knazarov/valeri)
* [A swiss-army script for planning team's work on GitHub](https://git.sr.ht/~knazarov/git-plan)
* [Homebrew tap for qemu with support for 3d accelerated guests](https://github.com/knazarov/homebrew-qemu-virgl)
* [Plain-text note taking system](https://git.sr.ht/~knazarov/notes.sh)
* [Markdown-to-html in awk](https://git.sr.ht/~knazarov/markdown.awk)
Work-related:
* [Tarantool Cartridge](/projects/tarantool-cartridge)
* [Tarantool Data Grid](/projects/tarantool-data-grid)
* [Plain-text note taking system](https://git.knazarov.com/knazarov/notes.sh)
* [Markdown-to-html in awk](https://git.knazarov.com/knazarov/markdown.awk)

View file

@ -0,0 +1,39 @@
X-Date: 2024-09-09T00:11:04Z
X-Note-Id: 9782c269-1cb9-476f-bdce-b964020b3674
Subject: Let's try Forgejo code forge
X-Slug: lets_try_forgejo_code_forge
About 2 years ago I've moved my personal projects from GitHub to [SourceHut](https://sr.ht/).
And now I think it's time to move to [Forgejo](https://forgejo.org/). I still like how
SourceHut works overall and its minimalism, but the community aspect is more important.
One of the big selling points of GitHub is that it acts like a social network, where it's
very easy for contributors to open issues or pull requests. Nowadays it would be very hard
to find a software engineer without a GitHub account, if only because it is required to
search code within repositories. Gating search behind registration was a really clever tactic
(but I digress).
The point is - GitHub has a really low-friction process for contributions, and alternative
code forges don't. Now, you may argue that people who want alternative forges should just
all get behind one vendor (like GitLab) and all use that one. But I will disagree with you.
First because git is a decentralized version control system and making it a "walled garden"
just feels wrong. Second, and more important reason is because trying to make a huge centralized
forge is almost necessarily a for-profit business. And we all know how it goes if you have
a monopoly or a duopoly.
The only reasonable solution to solving issues arising from fragmentation is federation,
in the same sense it's implemented in Mastodon. Imagine being able to go to anyone's code forge
and being able to open an issue or pull request there without an account, by using an already
existing account on the forge you prefer yourself. This is similar to how you can comment
Mastodon posts on certain instances.
Forgejo is one of the contributors currently driving the effort on code forge federation. See
[their FAQ](https://forgejo.org/2023-01-10-answering-forgejo-federation-questions/). They
are not the only ones, but at the current stages they are probably the best positioned to
reach practical results. And this is the key reason I believe it's worth supporting them and
trying out their product: if it works well - we will all benefit from a more diverse and
less locked-down ecosystem.
To "walk the walk", I've copied my repositories to [git.knazarov.com](https://git.knazarov.com/knazarov),
my personal Forgejo instance. This is where my work will live from now on, unless I find any
unsolvable critical problems.