What's different between Gitea and Gogs?<p>I just setup the Gogs docker image the other day to play with, and it seemed pretty painless to me.<p>Edit: I just found <a href="https://blog.gitea.io/2016/12/welcome-to-gitea/" rel="nofollow">https://blog.gitea.io/2016/12/welcome-to-gitea/</a> which somewhat answers this - essentially a different governance model and more development, but not any major functional differences.
If you're like me and were staring at Gitea's web site thinking, "dang, how do I run this as a daemon," Gogs (from which Gitea forked) has a nice page on doing this: <a href="https://gogs.io/docs/intro/faqs.html" rel="nofollow">https://gogs.io/docs/intro/faqs.html</a>
For those who want to try the project online, just go to <a href="https://try.gitea.io" rel="nofollow">https://try.gitea.io</a><p>For fast questions and talking there's a Gitter chat room: <a href="https://gitter.im/go-gitea/gitea" rel="nofollow">https://gitter.im/go-gitea/gitea</a><p>For feature requests and bugs go to <a href="https://github.com/go-gitea/gitea/issues" rel="nofollow">https://github.com/go-gitea/gitea/issues</a>
Another great thing is, they offer a lot of binary releases, especially for ARM platforms, so it works out of the box on e.g. Synology NAS (the Marvell based ones).
I like it. At my work(big corp that built a wall for for all engineering work and prevents engineers from using SAAS), this will be very helpful as it is a single binary built from open source Go. I'll try hosting our team's internal scripts and tools through this.
I'm eagerly looking for a solution good enough to let me ditch our current paid/hosted service. Gitea seems like it's getting <i>really</i> close, but a couple concerns linger:<p>* how does the pull-request/code review UI look? didn't see any examples on <a href="https://try.gitea.io/" rel="nofollow">https://try.gitea.io/</a> or main website<p>* mobile/responsive UI would be really nice for small screens
This time looking at this, I notice they have Dockerfile.rpi.<p>the kicker for moving to gogs from gitlab was that gogs had a prebuilt official rpi image... but it was several version behind the x86 one. I have no issues building images myself, but usually it feels like a lot of hoops to jump through to make things work on rpi. Having an rpi dockerfile really just makes me feel extra comfortable about things - not having to worry about weird x86 only dependencies and having to resolve them myself.
That's great! Zero-dependencies services are much appreciated.<p>In line with recent discussion how Maintainers Don't Scale [0] I think that software like this is a bit of an answer for dev-tools.<p>I think that kernel developers prefer tools that they can reasonably understand. Eventually tools that are easy to host (while having certain mindset). That's why most kernel related web services are probably written in Perl, in C (cgit) or in Python to some extent. I think Ruby on Rails or Java is not compatible with this mindset. Maybe Go is?<p>When I am thinking of self-hosted web facing services myself I have similar mindset. Every time I see that it's written in Java, Ruby or Node.js I pass. For certain it's many times counter productive, but I can't (or don't want to) help myself.<p>I tried to find the source behind LKML, but it's hard because most searches containing LKML will be just kernel related. It probably is written in Python as the developer behind LKML is a Python developer.<p>[0] <a href="https://news.ycombinator.com/item?id=13444560" rel="nofollow">https://news.ycombinator.com/item?id=13444560</a>
I have been using takezoe/gitbucket for a while now and have been happy with it , gitea seems to be the new kid on the block :), its also impressive to note that DigitalOcean has sponsored their hosting. One advantage I see with Gitea is that it uses Go and this will give it the power of scaling. Congratulations to the team and I look forward to the evolution of gitea
I read through the Gogs repo and there didn't seem to be any organized 'community' of users or talk of a fork. The author was away for a couple of weeks to come back to this news.<p>Is open source about contribution or just forking? At the moment it seems the the best way to open source is to be a well funded project with tons of resources and people specifically to manage the community because of intense expectations with projects declared dead even for one week of inactivity by some users.<p>What I am increasingly noticing with small teams or one man projects is if the project gains some popularity some 'community' folks pop up who first place an oppressive burden of expectations on the author and then try to fork the project. There is some element of misuse of the word 'community' by a small clique of people.<p>Why are community expectations so high, is continuous development and an ever expanding feature set the only way to develop? I think a culture of undue pressure is being created on open source authors and projects.
This space is becoming so full of open source offerings, I wonder if or how long the enterprise solutions can stay afloat.<p>Is Github making the kind of money they aimed to when they raised all of that VC money? What about Gitlab and Atlassian?<p>I realize that Github and the like have distinguishing features, such as issue trackers, but I can't imagine open source will lag far behind forever.
I fail to understand the difference between Gogs and Gitea?<p>Did anyone try it and how does it compare to Github, to Gitlab (hosted/free and entreprise) ?