Comment by ahacker15

9 years ago

We can for sure understand that one is not available all time. Everyone has a life, and sometimes need many weeks away, etc.

This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going.

Before the first time he went AFK, he even removed write access from the 2 or 3 other people that had it.

26 comments

ahacker15

Reply
sangnoir  9 years ago

> This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going

Others don't need write access "to keep the project going" unless they intend to ship releases without him/her- they can make PRs and the maintainer will merge them when they are back. Perhaps the Gitea committers want a more predictable release cadence?

I agree that a fork is probably the best solution here, due to the impedance mismatch, the forkers don't seem to be fans of the BDFL model. Additionally, "community" is a much wider term than how you used it, it's not just other contributors but also includes users and bug reporters. I wish Gitea the best of luck, but I'll remain a Gogs user.

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.

  • Mithaldu  9 years ago

    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.

    • Sir_Cmpwn  9 years ago

      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.

      2 replies →

  • sdesol  9 years ago

    > 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.

    • awill  9 years ago

      >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.

      2 replies →

    • Sir_Cmpwn  9 years ago

      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.

      9 replies →

  • madeofpalk  9 years ago

    > 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.