I just setup the Gogs docker image the other day to play with, and it seemed pretty painless to me.
Edit: I just found https://blog.gitea.io/2016/12/welcome-to-gitea/ which somewhat answers this - essentially a different governance model and more development, but not any major functional differences.
Why are people eager yo forget that users are also members of the 'community'?
The link shows how to run the app, not how to run it as a daemon. That said, the answer is platform specific, although it would be useful to have some common examples.
See this other thread: https://news.ycombinator.com/item?id=13452025
For fast questions and talking there's a Gitter chat room: https://gitter.im/go-gitea/gitea
For feature requests and bugs go to https://github.com/go-gitea/gitea/issues
It's because Go doesn't use gcc or LLVM for linking - it has its own built in linker that doesn't depend on the host system, so cross-compiling is totally trivial. I have no idea why gcc wasn't written like that.
* how does the pull-request/code review UI look? didn't see any examples on https://try.gitea.io/ or main website
* mobile/responsive UI would be really nice for small screens
https://try.gitea.io/gitea/gitea/pulls/2
Looks pretty much like github to me.
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.
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.
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?
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.
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.
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.
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.
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.
However, Unknwon, responded here [0], let me point out his main reason for not merging back:
> Gitea won't be merged back to Gogs, it's not about merging work is huge and hard, it's the differences of fundamental philosophy. I personally do not like to push hard to release new features, but make code neat and clean, it's not good for business, but Gogs isn't a business, making it is what I love to do.
[0] https://github.com/gogits/gogs/issues/1304#issuecomment-1246...
Is Github making the kind of money they aimed to when they raised all of that VC money? What about Gitlab and Atlassian?
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.
1. Someone else hosting, securing & backing up all your repos.
2. Someone you pay to blame when there are issues and hopefully with the incentive to fix quickly.
1. Someone else is hosting, securing & backing up all your repos.
2. You are at the mercy of someone else when there are issues to fix quickly.
Did anyone try it and how does it compare to Github, to Gitlab (hosted/free and entreprise) ?
I really like Gogs, but it is true that while I admire @Unknwon's drive, the project needs more maintainers.
It's a far more compelling story if a project like this is self hosting compared to hosting on what is essentially a competitor in the same space.
I found this page useful when setting up Gogs as a Windows service:
The author is also not unwilling to collaborate. Just look at the history of accepted PRs for example. However, he is unwilling to give others wider access and control over the direction of Gogs (which is totally his right):
> This happened not before trying to convince @Unknwon about giving write permissions to more people, among the community. He rightly considered Gogs his own creature and didn’t want to let it grow outside of him, thus a fork was necessary in order to set that code effectively free.
As to whether it stings I'm not sure. They had conversations around this topic and the conclusion was that a fork was what's needed for what (part of) the community wanted. Though it's possible for the original author to see this as a slap in the face I hope he sees it more as a huge testament to what he's achieved with Gogs so far.
This is how it is suppose to work, and many times BOTH projects will be stronger for it.
Prime example is the Split and then merge of NodeJS and IOJS because of that fork NodeJS is much stronger project today.
> In my point of view, it's a sign of success of Gogs that Gitea forked it. Gogs is under MIT license and there is no problem with me totally that Gitea is developing its own version. It happens often in open source community(when you are not satisfied with upstream version, I fork a lot actually). [0]
[0] https://github.com/gogits/gogs/issues/1304#issuecomment-1246...