Live data from Hacker News

Dear GitHub

github.com

311–320 of 491 posts

Re: Dear GitHub

#311
post #26

Is there an issue tracking system out there that works on top of the Github issue system?

We would love your thoughts on ZenHub.io [1] - fully integrated issue tracking, +1, estimates, burndown charts, kanban boards, even a personal todo list - a lot of the features asked for here, right within the GitHub interface and presented a lot more cleanly than competing products.

Disclosure: I work on ZenHub :)

[1] https://www.zenhub.io

Re: Dear GitHub

#312

Earlier quoted context omitted.

I am not your grand parent poster but I fully agree with you and I'd go further than that. The people who ask for more proprietary features (or should I say anti-features) in Github are encouraging lock-in inside of Github. Github ought to be a hub. I'd like to emphasize on the hub part as it should be one hub out of many. It should not be the center of the software universe any more than AT&T/IBM/Microsoft/Google/Fa…

> Github ought to be a hub. So, I heartily agree that vendor lock-in is bad. [0] However, git doesn't handle mailing lists, or issue trackers, or hands-off repo push access control, or.... So, if you're going to do more than just serving git repos, you're almost certainly going to have to do these things yourself, and you very well might end up doing them in a way that differs from how everyone else is doing them. I…

At the very least, we could try to create standard conventions for vendors like github to adopt

Re: Dear GitHub

#313

Earlier quoted context omitted.

Recently even Python language planned to move its repositories to github.com for network effect, instead of helping projects like kallithea SCM and trac by partnering with software conservancy or gnu. Python should learn a lesson when they decided to move their repository to closed source system like github. But obviously as people use Facebook, developers use github for the same reason, network effect. I hope they c…

> and trac Because, honestly, trac just sucks. It ain't as bad as the stuff Atlassian sells but still... it tries to be a fusion of MediaWiki and Bugzilla, and eh nope.

I still get a few emails a year from Trac instances where there is no support for unsubscribing emails

Re: Dear GitHub

#314

While I applaud the initiative, it's also a pretty strong indictment of the JavaScript / node.js community that there is not even a single non-male OSS maintainer on this list of important JS projects. What is being done in the JS community by those who lead it to make progress on this and who is leading that charge? If the answer is "Nobody", why is that true?

You could open a pull request on the list itself.

Re: Dear GitHub

#315
post #287

Earlier quoted context omitted.

Even if you don't have anything against Github relating to the Horvath incident, there are other things like Github shutting down people's projects because they wrote a doc containing the word "retard." In other words, now they are in the business of regulating the content of open source projects (beyond obvious precautions like not hosting stolen credit card databases, child porn, etc.) They seem to think they're to…

They also removed [0] C Plus Equality [1] project twice. Even Bitbucket [2] and Google [3] also removed it. [0] - https://github.com/FeministSoftwareFoundation/C-plus-Equalit... [1] - https://github.com/ErisBlastar/cplusequality [2] - https://bitbucket.org/FeministSoftwareFoundation/c-plus-equa... [3] - https://code.google.com/p/c-plus-equality/

Good.

Re: Dear GitHub

#316
post #287

Earlier quoted context omitted.

Even if you don't have anything against Github relating to the Horvath incident, there are other things like Github shutting down people's projects because they wrote a doc containing the word "retard." In other words, now they are in the business of regulating the content of open source projects (beyond obvious precautions like not hosting stolen credit card databases, child porn, etc.) They seem to think they're to…

They also removed [0] C Plus Equality [1] project twice. Even Bitbucket [2] and Google [3] also removed it. [0] - https://github.com/FeministSoftwareFoundation/C-plus-Equalit... [1] - https://github.com/ErisBlastar/cplusequality [2] - https://bitbucket.org/FeministSoftwareFoundation/c-plus-equa... [3] - https://code.google.com/p/c-plus-equality/

What was the story behind this anyway? I am having a hard time determining whether this was actually serious or were trying to parody feminist activism.

Re: Dear GitHub

#317

Earlier quoted context omitted.

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.

Ditto. Maybe 98%. I think that's a big part of the disconnect I'm seeing here in the comments. Those of us that live in private repos are likely pretty happy with how things currently work especially since we're the ones paying to use the service. If it wasn't working well for our teams, we'd find somewhere else to spend our money. That being said, we're certainly the minority when it comes to users on the platform.

Re: Dear GitHub

#318

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…

There appears to be a need for some a different class of repository for larger open source software.

Similar to the way twitter provides verified accounts maybe GitHub should consider a tagging these popular repositories to allow for more advanced control over the collaboration project.

When I first read the letter I was a little bit disappointed, one thing I've enjoyed (to an limited extent) is the low barrier of entry to pull requests. The spring boot team especially are extremely patient and understanding when it comes to pull requests.

Hopefully there's enough community will in this to encourage GitHub to make the change, if it does really come down it not being worth the money it would be a disappointing sign.

Re: Dear GitHub

#319

Earlier quoted context omitted.

Yes it is fairly bizarre that Github don't dogfood the issues function. I'm sure they have an internal system that they prefer, but even that internal system could have a public interface. Also, if the internal system is superior then its superior features could be added to the public system so that we could all benefit.

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.

Plenty of private projects use a separate, public Github repository for community reporting of issues, and public tracking of those issues.

Re: Dear GitHub

#320
post #171

Earlier quoted context omitted.

Maybe "complain" is too strong, but he created a GitHub issue –notifying several hundred people– without running ag --version. Heck, he didn't even look at the output of his command. It was immediately obvious to me, from the limited information he provided, that it was a bash alias.

Looks like a genuine mistake. He apologised. You've never done something dumb and didn't realise it?

A mistake, I can understand. But each issue I linked to was not a mistake. Each one was the end result of a series of mistakes stemming from a combination of ignorance, negligence, and (occasionally) incompetence.

Have I done dumb things without realizing? Of course.[1] But in almost 20 years of software development, I have never created issues resembling the ones I linked to. Bug reports are seen by hundreds of people and take up valuable developer time, so I make sure mine are useful.

To use an analogy: Say I'm giving a talk to an audience of a hundred people. I wouldn't do it extemporaneously, without slides, then walk away in the middle of Q&A. And if I did, I wouldn't call it a mistake. I'd call it being a terrible presenter. Yet that's what bad bug reports are like:

User (notifying hundreds of people): "It doesn't work."

Dev: "What version are you using? What error messages do you see? How are you running it?"

User: * crickets *

It's gotten bad enough that I wrote a short post on how to report bugs.[2]

1. https://news.ycombinator.com/item?id=7145451

2. http://geoff.greer.fm/2015/08/15/how-to-write-good-bug-repor...

Post reply on HN