Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dear GitHub

github.com

Post reply on HN
Print view View original

241–250 of 491 posts

Re: Dear GitHub

#241

Post by ars »

semi-extrinsic wrote: post #124
maxaf wrote: post #78

Earlier quoted context omitted.

There's an old story about this man who stood quietly next to a closed door in Moscow, said nothing to no one, and did nothing else of interest. Eventually others joined him, and before long a queue has formed. No one knew what they were standing in line for. Monkey see - monkey do.

One of Milgram's experiments (not the infamous one) tested this, using people standing on the sidewalk looking up. https://youtu.be/P0e6zG8IbE8

He might think he's testing conformance, but he actually just tested curiosity.

Re: Dear GitHub

#243

Post by peterfpf »

krschultz wrote: post #130
jonobacon wrote: post #116

Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre, My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in. Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pa…

An open question is how the community should provide feedback. Trello provides a decent example of how to do it well [1], but GitHub feels like a black box. I've been on GitHub since 2008 and I have been paying every month for years, but other than emailing support I have no idea how to vote for a feature request. My personal pet peeve is not being able to mark a public repo as 'deprecated'. There are a lot of other…

I normally put a big "[DEPRECATED]" notice at the beginning of the README. This normally doesn't go unnoticed.

Another good example is harthur's "[UNMAINTAINED]" [1]

[1] https://github.com/harthur/brain

Re: Dear GitHub

#244

Post by ajsharp »

anarchy8 wrote: 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?

> Why has Github been complacent?

Management, money, growth.

Re: Dear GitHub

#245

Post by chei0aiV »

zanny wrote: post #235
Osiris wrote: post #173

The author mentions that if GitHub was open source, they would implement these features themselves. Gitlab[1] is an open source repository manager that supports local installs as well as public hosting at gitlab.com. If author appreciates open source, perhaps they should put their efforts into improving an existing open source option rather than relying on a proprietary solution. [1] https://gitlab.com/gitlab-org/git…

This. When you are tired of github, start using gitlab, and realize your mistake going forward and stop making it, over[1], and over[2], and over[3]. [1] http://sourceforge.net/ [2] https://code.google.com/ [3] https://bitbucket.org/

Sourceforge runs Apache Allura, which is open source.

Re: Dear GitHub

#246

Post by joelhooks »

jessaustin wrote: post #231
scrollaway wrote: post #227

Earlier quoted context omitted.

Where are you getting that they don't dogfood the issue tracker? It's a private tracker (private repository) but from what I've seen in the Github blog, they do... it wouldn't make much sense if they didn't.

If they're using it, they're doing so in completely different fashion than everyone else. That is, it's not public for viewing, submitting, commenting, etc. Indeed TFA indicates exactly the sorts of pain points that would be missed by those using the tool in such a radically different way than everyone else. If someone at GH had to wade through all the damn +1's then something would have been done about them years ag…

95% of all my github activity is in private repositories.

Re: Dear GitHub

#247

Post by vrv »

jonobacon wrote: post #116

Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre, My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in. Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pa…

One suggestion is to improve the permissions system. For example, third-party github plugins that interact with the github system (e.g., setting labels, responding to comments) require "write permissions" which gives those systems "push" access to the underlying repo. Simply separating the git repository access control from the github UI / issues / pull requests access control system would be very helpful. I'm sure there are many other examples of where the permissions system needs some finer-grained access.

Edit: Essentially the same as reported here: https://github.com/isaacs/github/issues/268

Re: Dear GitHub

#248

Post by simoncion »

peterfpf wrote: post #243
krschultz wrote: post #130

Earlier quoted context omitted.

An open question is how the community should provide feedback. Trello provides a decent example of how to do it well [1], but GitHub feels like a black box. I've been on GitHub since 2008 and I have been paying every month for years, but other than emailing support I have no idea how to vote for a feature request. My personal pet peeve is not being able to mark a public repo as 'deprecated'. There are a lot of other…

I normally put a big "[DEPRECATED]" notice at the beginning of the README. This normally doesn't go unnoticed. Another good example is harthur's "[UNMAINTAINED]" [1] [1] https://github.com/harthur/brain

> I normally put a big "[DEPRECATED]" notice at the beginning of the README.

Aye. Some folks in the discussion linked to by krschultz complain that "People sometimes don't read the README and -thus- don't notice deprecation warnings.". To them I ask: "What makes you think that those sorts of people will notice anything less than an overlay that prevents them from interacting with the Github UI for that particular repo?".

Re: Dear GitHub

#249

Post by chei0aiV »

ggreer wrote: post #137
monkmartinez wrote: post #42

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 maintain a C repo[1] and user idiocy is much lower than what I've seen in JS projects of similar popularity. Still, I agree with these criticisms of GitHub. I hate +1 spam enough to delete such comments. Sometimes I even ban those who do it. I'm frustrated by people who open idiotic issues[2][3][4][5]. I procrastinate on bad pull requests because my options are: 1. Close the PR with little or no comment. People the…

SourceForge fixed the +1 issue recently.

Re: Dear GitHub

#250

Post by duncan_bayne »

mynewtb wrote: post #57
ben174 wrote: post #24

Earlier quoted context omitted.

By their very nature, git repos are one of the easiest things to migrate. Simply point at a new remote and push, and that's really it. It means that, unlike many other services, I could see GitHub being completely abandoned almost over night. If something better came along.

You would lose the issues.

+1
Post reply on HN