Live data from Hacker News

Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

forgejo.org

11–16 of 16 posts

Re: Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

#11
post #9
post #8

Earlier quoted context omitted.

Forgejo is an ideological fork (not a bad thing) that has chosen to rule out staying abreast of the significantly higher rate of development happening upstream. Consider it to be like Pale Moon instead of Firefox. Gitea has a great active community and remains MIT license with no CLA.

Yes I know that, this is on every page. The functional differences are not, that's why I am asking about those.

I can't say what Forgejo has over Gitea, but I can tell you Forgejo is missing everything from the 888 merged PRs in Gitea 1.23: https://github.com/go-gitea/gitea/releases/tag/v1.23.0-rc0

Repo license support, integrated Arch package repository, automatic issue suggestions, and the new review+homepage UIs would be notable ones for me.

Re: Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

#12
post #4

re my commentary nine months ago: I thought Gitea was fairly safe, as they were not requiring a CLA. ( https://news.ycombinator.com/item?id=39680587 ) They still seem to only require a DCO, so I don't think they're gearing up for a commercialization rugpull... yet? Some of the forgejo devs apparently believe that a collective copyright header is the same thing as a copyright assignment: https://github.com/go-gitea/gi…

You can check the technical velocity already, and it's extremely in Gitea's favour,

Re: Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

#14
The spirit of forgejo is great, but the whole CI component of both Gitea, forgejo und Github is absolute garbage. Just compare it to GitLab and it becomes clear.

Why the hell are Actions and 20GB "containers" used? It all makes simple command line installs in a container so hard to do. Actions overcomplicate simple stuff like git clone by burying it in mountains of TyseScript to the point of no recognizability or transparency. And having an external dependency on someone others otherworldly wrapped shell script. A singe-purpose container does not exist in that type of world which utterly defeats the whole point of using containers.

Is there a similar CI implementation to GitLab out there?

Re: Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

#15

The spirit of forgejo is great, but the whole CI component of both Gitea, forgejo und Github is absolute garbage. Just compare it to GitLab and it becomes clear. Why the hell are Actions and 20GB "containers" used? It all makes simple command line installs in a container so hard to do. Actions overcomplicate simple stuff like git clone by burying it in mountains of TyseScript to the point of no recognizability or tra…

I still use Drone with Gitea and it works great. I wrote a little adapter [1] so it can run VMs with Qemu, in case I need to build untrusted code (or on a different OS).

I don't know why they picked the GitHub thing for their CI.

[1]: https://github.com/remram44/drone-runner-qemu

Re: Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo

#16
post #15

The spirit of forgejo is great, but the whole CI component of both Gitea, forgejo und Github is absolute garbage. Just compare it to GitLab and it becomes clear. Why the hell are Actions and 20GB "containers" used? It all makes simple command line installs in a container so hard to do. Actions overcomplicate simple stuff like git clone by burying it in mountains of TyseScript to the point of no recognizability or tra…

I still use Drone with Gitea and it works great. I wrote a little adapter [1] so it can run VMs with Qemu, in case I need to build untrusted code (or on a different OS). I don't know why they picked the GitHub thing for their CI. [1]: https://github.com/remram44/drone-runner-qemu

Interesting, thank you!
Post reply on HN