Forgejo(forgejo.org) |
> We're excited to announce the official launch of the #Forgejo project, a community-driven fork of #Gitea under the stewardship of @Codeberg. Check out https://forgejo.org/2022-12-15-hello-forgejo/ to learn more, including the motivation for the fork, as well as Codeberg's announcement at https://blog.codeberg.org/codeberg-launches-forgejo.html Come and get involved at https://codeberg.org/forgejo/forgejo or in our Matrix room https://matrix.to/#/#forgejo-chat:matrix.org . We aim to be a fully inclusive community and everyone's participation is welcomed.
This project is the soft fork of Gitea that was created in reaction to the open letter [0][1], after Gitea Ltd. was incorporated [2].
[0] https://gitea-open-letter.coding.social
Is is mostly going to Forgejo (other than Gitea Inc employees obviously), mostly staying with Gitea, a mix?
That being said, Forgejo is a soft fork, so they will still benefit from those contributions.
Forgejo was officially launched yesterday...
Also what's a "frequent maintainer"?
If this is a software meant for developing with powerful collaboration tools, where is even just one screenshot of what it looks like? I don't want to sound like a tiktok kid that only cares about form over function, but there's absolutely nothing visual ( or written for that matter ) to illustrate this project.
Do I really have to pull the image, execute it and find out about the looks, features, and how to configure it? No introductory video? No Docs? Heck, not even a screenshot of the main page
At the time of writing the interface will be identical.
1) Very, very operationally-simple deployments are available. It can run with just SQLite, no external services (e.g. database daemons, queuing systems, all the other stuff that GitLab likes to have) whatsoever.
2) It looks and feels more like Github, which is nice if you prefer that UI.
3) The site's far lighter-weight and snappier than GL, when you're using it.
4) You can (probably—workloads vary) serve 1-100 users with the dumbest possible deployment, running on a potato. It's far more resource-efficient than GL—which, it's not hard to be more resource efficient than GL, since it's an absolute beast, but Gitea comes in way under it.
Downsides:
1) Missing some stuff GL offers (like integrated CI)
2) Lacks some features that make serving at enormous scales (of the sort you almost certainly won't hit unless providing a Github/Gitlab-like service to the world) impractical.
3) Fewer just-works 3rd party integrations, especially commercial ones.
It's Esperanto. It's supposed to be written "forĝejo" (forĝi=to forge, -ej-=place, -o=noun). The letter ĝ (for the dʒ sound, like Dj in Django, or J in John) is supposed to be written as gx without diacritics. But I assume "forgxejo" would have confused non-Esperantists even more.
(There are various systems to type without diacritics in Esperanto. Two of the most widely popular ones are to use the letters ‘h’ and ‘x’, and using either of those would be correct. But if one is to be regarded as the ‘default’ choice, it has to be the one with ‘h’, since that’s been codified in the language’s foundation since its early days.)
"Forgejo" is not ideal in Esperanto, because both "for" 'away' and "gejo" 'gay man' are totally valid Esperanto words, and "forgejo" is a valid combination (even though it's hard to understand what "away-gay" should mean); compare "foriri" 'go away' or "forigi" 'do away with, remove' xD
Or how does a soft fork work?
As far as I know they intend to upstream patches they make as well.
And yes, Gitea is still open source and MIT licensed.
I have no real description for a "frequent maintainer", so maybe my wording was incorrect there.
I simply meant someone who contributes to the project often, but I don't have a concrete description for you considering "often" could also be subjective.
A frequent contributor then?
"Maintainer" usually implies some sort of admin rights, e.g. the people merging in the contributions.
Yes, frequent contributors.
So I just invalidated your argument, lol.