211–220 of 241 posts
Earlier quoted context omitted.
At least for Gogs and Gitea nobody gets payed at all, same for lots of other opensource projects. So of course it's hard to pay some frontend engineer if none contributes to the project :)
It's harder to get a frontend engineer to contribute, than the other engineers who do?
Quick comparison from GitHub stats and READMEs: Gogs: 24,564 stars, 602 issues, has a features list. https://github.com/gogits/gogs Gitea: 5,971 stars, 733 issues, doesn't have a features list. https://github.com/go-gitea/gitea Gogs features (from README): Activity timeline SSH and HTTP/HTTPS protocols SMTP/LDAP/Reverse proxy authentication Reverse proxy with sub-path Account/Organization/Repository management Add/Re…
Earlier quoted context omitted.
> Gogs author didn't want to incorporate proposed changes into Gogs, so a bunch of other developers forked Gogs This sounds like a reasonable way for forking though. I mean what is open source for if you can't go and and implement your own features if you so desire. Sounds to me like both sides are at fault.
I don't know enough of the details to really tell you, but it was more hostile then just that. I heard the maintainer went on hiatus and that's when they forked it - like there was some drama going on, it wasn't just a "I'd like to incorporate my changes here" and more of a "HEY LOOK THE DEV LEFT, WE'RE THE NEW GOGS" kinda thing. Check out some of the other comments in this thread, they explain it better.
I would gladly switch back once Gogs is no longer vulnerable to the Bus-Problem.
Earlier quoted context omitted.
I was also wondering this, plus kind of expecting it to be hosted on gitea. Being hosted on github lowers my confidence.
Gitea has a TODO list for hosting Gitea on Gitea. See https://github.com/go-gitea/gitea/issues/1029
Most compilers I'm aware of gets compiled by themselves. I think it's great for two things:
1) Show how serious the compiler is - compiler code tends to be complicated 2) Free real life testing
I was expecting Gitea to be hosted on Gitea for the same reasons. Was trying to offer criticism but got downvoted immediately, ahh HN =)
Earlier quoted context omitted.
> [...] programmers asking why git has problems with their newly requested LFS and a 40gb video file they decided to store. The thing is, git, as our industry uses it, is not really a good tool for keeping artifacts , and "video" sounds like an artifact, not a source file. I'd like to see more artifact repositories, especially the ones that you can talk to from command line or from a Python/Ruby/whatever script. I ha…
What is your artifact repository called and what are the main features? I'd love to check it out.
From the features, GrailBag stores files along with key:value pairs as metadata (not surprising), has a command line client to list/modify/upload/download/delete the artifacts, and has a Python module for doing the same from a more sophisticated script.
Additionally there is an interpreter of a simple language that describes directory tree where artifacts will be deployed (which artifacts to download, how to name the files, what directories and symlinks to create). This way you can write a cron script that deploys whatever you have in the repository, e.g. in a cold-standby server scenario (two servers having the same configuration, but one shut down and only powered on when the first one fails; on the first run of the cron task, the spare server downloads all the missing files, including whatever got stored while the server was shut down).
Quick comparison from GitHub stats and READMEs: Gogs: 24,564 stars, 602 issues, has a features list. https://github.com/gogits/gogs Gitea: 5,971 stars, 733 issues, doesn't have a features list. https://github.com/go-gitea/gitea Gogs features (from README): Activity timeline SSH and HTTP/HTTPS protocols SMTP/LDAP/Reverse proxy authentication Reverse proxy with sub-path Account/Organization/Repository management Add/Re…
Gitea is a disreputable and hostile fork of gogs. You should stick to gogs.
Frankly, I'd have expected better from the creator of sway. As someone who is not involved in either project, I see two active projects, which offers more choice to users, makes it less likely for both projects to go away, offer competition and all around be in the spirit of open-source.
Often I hear, "if you don't like it, fork it" and then when it gets forked, you get called hostile? Doesn't make sense to me from a rational perspective - nobody forces you to adopt Gitea or Gogs if you don't want to.
I might be the only one here, but I wish Gitlab had stayed on providing the best git / issues solution instead of bloating it further and further into CI/CD and more. After all, Gitlab started as an open source alternative to github and that’s what I really wish for and while I understand how Gitlab needs to differentiate itself from Github, the direction is causing some of the issues. My two cents...
I agree, I've been using Gitlab and it has been very unreliable. It has become too bloated.
Is there any fundamental reason why no tool offers a federated alternative to GitHub? I mean, the distributed nature of git is ripe for federation, but why aren't issues, releases and pull requests federated? Maybe even some deeper integration with git itself, such as seeing new remotes on federated servers and fetching them. This may sound redundant to GitHub, which currently centralizes everything, but different pr…
Thanks for mentioning this here, I've been trying to raise this whenever I can, but not a lot of people seemed to care enough about this, hope this gets more visibility.
devops sysadmin here. I started with gitlab about a year ago and can honestly say I wish I had taken gogs/gitea instead. The main problem for me is gitlabs utter dearth of somewhat counterproductive features. Git LFS support is almost a cruel joke in gitlab as git operations under the hood now take inexorably more ram to complete. In turn im rewarded with more traditional RCS programmers asking why git has problems w…
I had a class last semester that submitted everything through Gitlab and when we tried to run unit tests to test for the correct code, it would hang for 7-8 minutes. Very frustrating. Happened on all the assignments so was not just a one time thing.
Was this on a self-hosted instance or on GitLab.com?
We'd love to make sure this doesn't happen again.
Gitea will get much more recognition for their great efforts once they are self-hosted. https://github.com/go-gitea/gitea/issues/1029