Live data from Hacker News

Dear GitHub

github.com

91–100 of 491 posts

Re: Dear GitHub

#91
post #76
post #7

Issue spam (in the literal sense) definitely needs addressed as well: https://pbs.twimg.com/media/CYI31g1UQAUXQbs.png

It's my project, why can't I just delete issues like any other bug tracker?

The issues were deleted in fairly short order, but their notifications were still sent out to all repository watchers and persisted beyond the issue deletion. Also, most issues were generated mere seconds apart from accounts less than a day old.

So the issue isn't that GitHub didn't let them clean up the issues after the fact, but that there were no a) rate limiting options, b) user reputation options, or c) issue submission filtering options.

Any one of those three would have reduced the impact significantly.

Re: Dear GitHub

#92
+1 to the notification spam. Being @sam on github sucks sometimes. And as far as I can figure out there's no way to set watching/following/notifications to opt-in only.

So every time someone who knows a "Sam" uses @sam incorrectly in an issue I get notified, have to unsubscribe, ignore, and leave a polite message to let them know they're doing it wrong.

It's really lame that they've never fixed this.

Re: Dear GitHub

#93

I do not operate a popular OSS project, but I have experienced the +1 spam and it sucks. The suggestions, in my opinion seem rational. Interesting side note: With the exception of Selenium, most of signees are maintainers of JS/HTML OSS projects. I wonder if we could objectively compare JS to projects in terms of the problems mentioned in the document. For example, there is a strong correlation between +1'ers and JS…

I noticed that most of the signers are maintaning JS/HTML projects too.

I wonder if those types of projects are more likely to have these problems (larger userbase? Less experienced userbase? just different userbase?)? It could also just be a coincidence that they knew each other because they work on similar things, and a group of people who knew each other are the ones who wrote the letter.

Re: Dear GitHub

#94

I do like Github, and I understand how it makes the entire process of maintaining a code repo a lot easier, but what I'd genuinely like to know is why don't big projects just move to their own thing? I understand that there isn't a single solution that exactly matches what Github has, and that maintaining your own git server + git management/issues/etc.. app is a pain, but I see it as the only real solution. Developi…

> I understand that there isn't a single solution that exactly matches what Github has, and that maintaining your own git server + git management/issues/etc.. app is a pain

You outlined exactly why people don't build their own or use another system. Github is the best there is. That doesn't mean it doesn't have problems, but if your company/project/expertise isn't focused in collaborative development and/or version control, you're just distracting yourself by building your own.

The authors are not saying "we can build a better Github." They have complaints and would like them resolved, but don't see a good way of having that happen.

Re: Dear GitHub

#95

I do like Github, and I understand how it makes the entire process of maintaining a code repo a lot easier, but what I'd genuinely like to know is why don't big projects just move to their own thing? I understand that there isn't a single solution that exactly matches what Github has, and that maintaining your own git server + git management/issues/etc.. app is a pain, but I see it as the only real solution. Developi…

[deleted]

Re: Dear GitHub

#97
It's 2016, and GitHub is stagnant.

GitHub used to bill itself as "Social Coding", but the "Network" graph has not seen ANY updates since its original introduction in April of 2008. Issues has seen very few updates. Even the OSS projects that GitHub uses internally have grown stagnant as GitHub runs on private, internal forks and maintainership passes to non-GitHub-employed individuals (e.g. https://github.com/resque/resque/issues/1372).

The word "Social" no longer appears on GitHub's landing page. They're chasing some other goal...whatever it is.

Re: Dear GitHub

#98
post #27
post #16

Earlier quoted context omitted.

> I feel like there is a great opportunity right now for anyone to make a Github replacement. There is GitLab, which is good and is FOSS in addition.

I'm maintaining a GitLab instance for my team at work and it's been really great for us. I am pretty disappointed that the CE version doesn't include GitLab Pages, though, as that was the one feature I missed most from GitHub and GitLab Enterprise is outside of our budget at this time.

At a previous company, we did this in GitLab with a simple post receive hook that just checked out the gh_pages (or gl_pages) branch on a webserver configured w/ rewrite to serve at a proper path. We even were able to do one better and allow PHP since it was self hosted and we trusted the committers.

Re: Dear GitHub

#99
post #67

Earlier quoted context omitted.

I just wish that bitbucket's UI was half as smooth as Github. Sure, it's not terrible, but it has a lot of rough edges.

I'm completely comfortable calling BitBucket's UI/UX terrible.

Not just bitbucket, but most of Atlassian's products, IMO. We switched from Slack to Hipchat at work recently, and the rough edges constantly irritate me.

Re: Dear GitHub

#100
post #6

I feel like there is a great opportunity right now for anyone to make a Github replacement. Sounds like a lot of these features are sorely needed at the moment. Why has Github been complacent?

> I feel like there is a great opportunity right now for anyone to make a Github replacement. Sounds like a lot of these features are sorely needed at the moment. Why has Github been complacent?

Network effects strong enough to slow the growth of any competitor long enough for GitHub to adapt.

Post reply on HN