Comment by Sir_Cmpwn
9 years ago
That's his prerogative. Learn patience. Not all PRs have to be merged on your schedule. As a FOSS maintainer myself this sort of behavior sickens me and reeks of entitlement. Gogs is worse off for your involvement.
9 years ago
That's his prerogative. Learn patience. Not all PRs have to be merged on your schedule. As a FOSS maintainer myself this sort of behavior sickens me and reeks of entitlement. Gogs is worse off for your involvement.
Forking when you're unhappy about something and can't come to an agreement is EXACTLY what OSS is about. Saying this as another OSS maintainer.
I would completely understand and agree if they had a rational reason for forking, but they don't. I have a very low opinion of unwarranted forks.
Why does somebody forking need to justify that their fork is warranted based on your standards?
1 reply →
> Not all PRs have to be merged on your schedule
Considering how fast GitLab is moving, if Gogs/Gitea wants to remain relevant, they really have to move at a much faster pace than they use to. Judging by Unknwon's comment in this issue
https://github.com/gogits/gogs/issues/1304
it seems like Gogs is driven by a passion and it doesn't matter at the end if he is the only user. As he puts it
> Gogs isn't a business, making it is what I love to do
I'm not sure if his stance has changed, since this issue was from July. I'm also not sure, if he fully realizes he is sitting on a potential golden goose. The market for Git hosting in Enterprise is still very much up for grabs.
>Considering how fast GitLab is moving, if Gogs/Gitea wants to remain relevant.
Gogs is written in Go, easy to install, light on features and is lightning fast.
Gitlab is mostly Ruby (with some Go), a mess to install, heavy on features, and (at least gitlab.com) extremely slow.
I don't see how they compete at all.
They compete in the mindshare sense. If a company is determined to treat Git hosting as commodity product, they are going to look at gitlab, gogs/gitea, gitbucket, and a bunch of other solutions.
As you point out, you either go with fast vs feature rich.
GitLab is working towards making things faster and easier to install. Is Gogs/Gitea working towards making it more feature rich?
If Gogs market are hobbyist who want to run it on a Raspberry PI, then I don't see GitLab being a threat. If Gogs wants to be solution that larger companies would consider using, then they are going to have to compete with GitLab's, which means introducing more features.
This Gitea fork appears to be a desire to move faster with more features. I've posted this in another response, but this a diff from the point of divergent to the latest commit for each master branch.
Gogs (69 commits with 106 diffs):
https://gitsense.com/gogs-gitea/gogs-diff.png
Gitea (528 commits with 2,062 diffs):
https://gitsense.com/gogs-gitea/gitea-diff.png
I obviously haven't gone through a lot of the diffs, but the changes appear to be formatting/commenting like this:
https://gitsense.com/gogs-gitea/gitea-changes-example1.png
with others adding more functionality like this:
https://gitsense.com/gogs-gitea/gitea-changes-example2.png
No matter what, it looks like there maybe no turning back for both groups. Hopefully this is not the case.
Hey, thanks for the feedback. We're aware of issues people experience with latency on GitLab.com and we're working to make it better. You can see some of the history regarding this issue here: https://gitlab.com/gitlab-com/infrastructure/issues/59
This issue was updated this morning with a plan to speed things up: https://gitlab.com/gitlab-com/infrastructure/issues/947
I will continue to use gogs, forking is not correct.
The maintainer cares about code quality, it seems like gitea does not
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 ;)
One of the few developers getting paid to work on Gogs is (was?) on payroll at GitLab.
Your mindset is totally whack. Gogs does not have to compete with GitLab, it can fill its own niche. Who are you to tell him how to use his "golden goose"? Why does it need to be a business? Jesus christ.
I am not saying it is a golden goose. I am saying it has potential to be. If he wants to work at his own pace, then all the power to him but this path most likey wont lead to anything but a hobby project.
He can't expect others to not want to push for greater git mindshare. Gogs is licensed under mit and he has absolutely no say in how others want to evovle it. This is how permissive licenses work.
1 reply →
So gogs can be that and gitea can be something else, why are you still thinking that they don't have a good reason for their fork if they have different ideas about which niche they want to serve.
5 replies →
yes, but it can, and if people want it to, it should. besides, why wouldn't you want it to be a business? businesses make money, which can pay for development of new features and better support for users. sounds like a win to me.
> That's his prerogative
Sure. 100%. It's up to him for how he wants to run an OSS project.
In the same way, if people in the community have different ideas they're more than welcome to fork. If you don't want that to happen, either listen more to the community or don't open source a project.
It's his prerogative to do that, it's theirs to fork the project.