tboerger

For those who are using prometheus and also use apt-dater to control updates of multiple servers I have created a new tool to automatically generate the hosts configuration file. Hopefully this not only useful to me :)

I really love this move! I'm glad that I'm part of the community and free contributors 8)

You can compare it with that. It's just built up entirely transparent and open and backed by a non-profit organization.

But some (like Gitea) are working on it to start hosting it on their own. Gitea will also get federation features to make contributions between independent Gitea instances possible.

But even when it starts to host, it will get GitHub OAuth2, just to keep the barrier small to receive contributions.

The best way to compare the features could be https://docs.gitea.io/en-us/comparison/ which is a really fair comparision.

Edit: This list have been created on best efford, if you find any wrong information a pull request is always welcome.

Seems like that, the number of developers is always growing, but AFAIK none of them is a frontend engineer.

Gitea got code and issue search, the code search just needs to be enabled within the config because the indexing process takes up more resources, that's why it's disabled by default.

https://github.com/go-gitea/gitea/issues/1612 https://github.com/go-gitea/gitea/issues/1299 https://github.com/go-gitea/gitea/issues/184

These issues and some others pop up if you search for federated.

There are multiple tracking issues on the gitea tracker for federated features, so hopefully gitea will provide features like that.

Ok, let me rephrase that, if you like to run the JVM do it :)

If you like to run java services you could do that...

It just means Gitea now also got the emoji reactions like Github already got.

I remember this question via discuss, and I personally said that this list will be anyway always out of date.

If you want to compare Gogs and Gitea you have to compare the feature list.

Please provide constructive feedback on the docs issue tracker, or even better create pull requests to improve the documentation.

Everything including the website, documentation, blog, Hugo theme and so on is public available and also opensource.

There are enough people and companies that don't trust these american companies, or they are forced to keep code within there network... Not everybody wants to give his stuff into the hands of others ;)

At least for Gogs and Gitea nobody gets payed at all, same for lots of other opensource projects. So of course it's hard to pay some frontend engineer if none contributes to the project :)

As you can see on https://github.com/go-gitea/gitea/issues/1029 and on another comment here it's still in the works to host gitea development on gitea instead of github.

But nobody in the team wants to do the switch if not all features are available that we rely on today at github.

I wouldn't say that directly, maybe it gains more trust because it's serving on their own code, but maybe this could also decrease the contributions because the people got to authenticate on just another system to contribute something.

We will see how well this works out, most required features are already there, the remaining will follow soonish.

Go is used a lot in China. And even the initial author of Gogs and the guy who initialized the fork are Chinese :).

Maybe this is the case because free projects not backed by a company can't pay a professional frontend engineer :)

Gitea pairs even better since Gitea supports the CI status API.

Ok, of course I'm opinionated as a Drone plugins maintainer and former Gitea owner :P

Something have not been mentioned at all, Gitea still got support for OAuth2 which have been simply dropped by Gogs because "nobody needs that".

Beside that Gitea still got more really useful features compared to Gogs. But Gitea will always focus on Git hosting and won't bundle with CI, Chat and all that stuff what Gitlab does. There are enough tools you can easily connect to get features that Gitlab got, only if you need it.

Why do you think gitea doesn't care about code quality? To improve the code quality we even include linting and things like vet into the ci process. Beside multiple refactorings to improve the quality. Gogs got more than 1k lint errors, gitea got none ;)

Who of the gitea developers is harsh?

We are aware of that issue, and hopefully we will find a proper solution to improve the load time for bigger repos.

As already said, nearly all people in the org are former Gogs contributors, the owners have been elected by the other people who joined the effort, everybody who has contributed 4 pull requests can join the maintainers team of gitea, the owners will be elected every year by the community, EVERY scripting for the infrastructure and the website and so on its entirely published. The only thing that is a secret shared between the current owners are the secrets for the services like github tokens, github oauth or email credentials. Everything else is open, accessible by everybody.

After the integration of the missing features like OAuth2, protected branches, ci status and some others we will start dog-fooding, than Github will just stay as a mirror for contributors that don't want to login to our gitea instance.

We will integrate OAuth2 and after that we also want to integrate federated pull requests so that you can create pull requests from other gitea instances as well.

Thanks! When @lunny finishes the outstand pull request feature it should be a real alternative as it is damn lightweight. There are already plans to im prove the UI as well :)