Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is gogs dead? #1304

Closed
jsieler opened this issue Jun 1, 2015 · 33 comments

Comments

@jsieler
Copy link

commented Jun 1, 2015

Is the project mainly dead? Since over a month there is nothing new... Anyone knows?

@fuxiaohei

This comment has been minimized.

Copy link
Contributor

commented Jun 1, 2015

we are waiting for @unknwon coming back from US. He's a student.

If something gets worse, we will make new plan for gogs in June or July.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 1, 2015

@fuxiaohei accepting for contributors for accepting pull requests would already help. Or just opening the contribution to the long missing feature for pull requests :)

@fredghostkyle

This comment has been minimized.

Copy link

commented Jun 1, 2015

@fuxiaohei Do we have a ETA to when he's back? Also, just because you're missing your leader doesn't mean nothing gets done. That might sound mean and really harsh but it's true.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 1, 2015

If more people would have write access, yes... We will get an answer really pretty soon, i think tomorrow.

@vheuken

This comment has been minimized.

Copy link

commented Jun 2, 2015

@tboerger I don't see why that prevents work from getting done. Why can't someone just fork it and merge pull requests to that fork, then merge that into the main repository when @unknwon gets back?

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 3, 2015

@srgvg

This comment has been minimized.

Copy link

commented Jun 4, 2015

What's the problem with @unknwon being in the states? Don't they have internet access there?

What's the deal with go-gitea exactly? A real fork? The project repo doesn't even mention it's a fork from here. What are your intentions @tboerger ? If it would be possible to avoid a rename..

Unrelated: can we have a mailing list and an official irc room? Github issues s**k for support stuff.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 4, 2015

go-gitea will mention that, just give us sone time. There is already the official Gitter chat :)

@redelman

This comment has been minimized.

Copy link

commented Jun 12, 2015

Since gogs has been forked to go-gitea, does that mean that gogs is indeed dead? Wondering if I should bother updating my gogs at work to go-gitea.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 12, 2015

@redelman we need a little bit more time to get a new stable release of gitea out of the door, afterwards it makes sense.

@iraycd

This comment has been minimized.

Copy link

commented Jun 12, 2015

This topic is trending on Hacker News. https://news.ycombinator.com/item?id=9708832

@jonhermansen

This comment has been minimized.

Copy link

commented Jun 13, 2015

It seems pretty ridiculous that people are complaining about a lack of updates for free (as in beer) software. "Be the change you wish to see in the world", fork the project, make the changes you need, and stop waiting for someone else to do it. Unless I'm misunderstanding something here -- are you guys paying his salary?

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2015

Nobody earns money with gogs/gitea. And it looks like some people on HN thought that i have forked gogs, that's not true, I just started to dive into contribution ;)

@StrangeWill

This comment has been minimized.

Copy link
Contributor

commented Jun 14, 2015

@jh86 It isn't about @unknwon coming in and working for free, it's about one of the project maintainers continuing the project -- sure Gogs can (and has been) forked. There is just little reason for a project to fall off the face of the earth because maintainers are all waiting on a student to come back before touching it.

I'm glad that the fork is happening (only due to the large amount of interest -- I wish development was kept under one roof) -- I was considering having to ditch Gogs over the lack of active development (and am still kind of patchy on that), it's solid software and I'd like to continue contributing to it.

Also I do really appreciate the work @unknwon has done, this project has seriously surpassed the evaluations I've done on other software due to the speed and familiarity it has. Lots of good decisions on his (and the various other contributor's) parts.

@f0086

This comment has been minimized.

Copy link

commented Jun 30, 2015

A month later an still no sign of life here.
Is go-gitea the official fork where the active development happen now?
Time to fold up here?

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jun 30, 2015

@f0086 as we already said, yes it is the official fork. If @unknwon ever comes back we want to merge the changes back to gogs of course.

@bclermont

This comment has been minimized.

Copy link
Contributor

commented Jul 3, 2015

@tboerger he's back 4fca548

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 3, 2015

@bclermont interesting, now let's see if he is open for contributions and maybe write access :)

@bseng

This comment has been minimized.

Copy link

commented Jul 7, 2015

I really hope they merge as gitea documentation always link back to gogs

@bclermont

This comment has been minimized.

Copy link
Contributor

commented Jul 7, 2015

I wonder why gitea fork on first commit was to change project name. this will make all merging process harder.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 7, 2015

A quote from @lunny on the gitea Gitter chat:

I have contacted with Unknwon. And he said he will consider to merge gitea back to gogs if the progress is not difficult. And maybe he want to keep gogs simple and he don't want to add more people as contributors.
So I think we can continue gitea and no need to wait for him.

@f0086

This comment has been minimized.

Copy link

commented Jul 7, 2015

What is going on with you @lunny , @fuxiaohei and @slene ? Do you have write access to the repo? There are 18 open pull requests at the moment (and 333 open Issues!). If nobody review/merge the pull requests and the issues gets ignored, the project is doomed in the long term.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 7, 2015

@f0086 as already mentioned above, @unknwon is the only one that have write access to gogs, and this will stay like it is. @lunny and @fuxiaohei created the fork https://github.com/go-gitea/gitea where currently 4 people got write access. It won't take too long, than we will have finished pull requests, wikis are already done, than we will release gitea v0.7

@linquize

This comment has been minimized.

Copy link
Contributor

commented Jul 7, 2015

@unknwon is back recently, but unsure if he knows the fork go-gitea/gitea

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 7, 2015

@stephen-hill

This comment has been minimized.

Copy link

commented Jul 10, 2015

@tboerger

Is there an estimated release date for v0.7?

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 10, 2015

@stephen-hill no estimation, but we need to finish the pull request feature first.

@thoroc

This comment has been minimized.

Copy link

commented Jul 16, 2015

+1

@flomine

This comment has been minimized.

Copy link

commented Jul 24, 2015

Hi all contributors of gogs and gitea.
Do you consider to merge gitea back to gogs or not?

The situation is not clear to me and I think this situation is not good for gogs and gitea ?
Do we have to choose one now ?
Please let me know.

@HLFH

This comment has been minimized.

Copy link

commented Jul 24, 2015

Hi. IMHO, gitea has wiki support, not gogs. I'm waiting for this feature. So, as soon as gitea is released (go-gitea/gitea#22), I'll migrate to gitea, which seems to have a more open governance.

@f0086

This comment has been minimized.

Copy link

commented Jul 24, 2015

@flomine Exactly! If this gogs vs. gitea struggle is going on for another month, I will switch to a completely other platform. This is just unprofessional and ruin the project.

@tboerger

This comment has been minimized.

Copy link
Contributor

commented Jul 24, 2015

@f0086 if you think this is so unprofessional have you ever managed such a complicated situation? Just criticize is pretty easy. Suggest improvements is much more complicated...

We simply have no write access and will not get any write access to gogs. So multiple peaople of us want to push gitea of course. Merging features back will be pretty difficult as nobody knows what gets rejected or accepted by @unknwon as he only reacts rarely to any request...

Currently we are in the middle of the summer, so many people are doing vacation or relax within the summer. Gitea nor gogs are full time projects, nobody gets payed for that, so this is as usual within opensource projects that things take time.

Just relax, gitea will be released as soon as pull requests are finished. You want to contribute something? Go ahead, we are happy to see more contributions! there are enough open issues with lowhanging fruits that can get fixed within the upcoming 0.7 release. Every bigger change can get into 0.8 ;)

@unknwon unknwon added the question label Jul 24, 2015

@unknwon

This comment has been minimized.

Copy link
Member

commented Jul 24, 2015

Apologize for being away for so long. 😳

To finish this thread, there are some words I would like to say:

  • Gogs isn't dead, and it's my bad for being inactive for 3 months. There are reasons cannot be told and understood.
  • The initial reason that I removed write access of @lunny and @fuxiaohei was there is a build failure after merged a PR, and I got e-mail notified. And the reason access was not giving back was that I wasn't able to have enough time review all PRs, and I don't like unfamiliar or not totally understood code is merged into codebase. I believe it's better to keep it as it was and merge when things get to normal like now.
  • 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).
  • 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.

Thank you all, and happy coding!

@unknwon unknwon closed this Jul 24, 2015

@gogs gogs locked and limited conversation to collaborators Jul 24, 2015

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.