We’d like issues to gain a first-class voting system,
and for content-less comments like “+1” or “:+1:” or
“me too” to trigger a warning and instructions on how
to use the voting mechanism.
Dear GitHub
411–420 of 491 posts
Re: Dear GitHub
#412Earlier quoted context omitted.
So use a real issue tracker. Most of the big ones integrate with github. Why should they reinvent this wheel?
If not to be a hosted software lifecycle tool, what the hell is Github even for?
"Software lifecycle tool" is too vague for a product to have focus and open to too many interpretations as to what it should include. Even limiting scope to issue tracking, there are different points of view on how that should work and several widely-used but rather different software alternatives to choose from.
And how many teams spend the first three months of a project building a custom issue tracker because they don't like any of the off-the-shelf options? Trying to get issue-tracking "right" is a black hole for a company like github. Which is probably why they provide the bare minimum free-form issue and that's it.
Re: Dear GitHub
#413It'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…
How reasonable is it to make issue tracking and social interaction part of the SCM itself [with optional web interface] ? git issues "This needs attention" >> Issue #1 created git issues >> List of issues git issues -u #11 >> Issue #11 up voted >> #11 Important stuff, needs attention git issues -d #6 >> Issue #6 down voted git issues -f #4 >> Issue #4 flagged
Your `.git` directory would become huge pretty quickly and you would have plenty of problems with people commenting on issues without having a repo up-to-date. How would you handle conflicts in that case?
Re: Dear GitHub
#414Earlier quoted context omitted.
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 peop…
Why would you even respond to a bug report that was "it doesn't work."
Such a vague report tells you all you need to know about whether it's going to be worth your time trying to work with the person who submitted it. Close it immediately as non-actionable.
Re: Dear GitHub
#415It'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…
> They're chasing some other goal...whatever it is.
Maybe putting most of their efforts into Atom and Electron?
Re: Dear GitHub
#416Hi 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…
[deleted]
Re: Dear GitHub
#417Many times, I've asked GitHub to add icons for :test:, :doc:, :admin: and a couple others. I use them in commit messages as it helps categorize the type of commit. This has to be the easiest kind of improvement imaginable, but they have never bothered.
Re: Dear GitHub
#418Earlier quoted context omitted.
GitHub pretty please, give us an option to hide our profile from search engines just like Facebook do.
What is the use-case of this?
I have an account that is only for private repos and I don't want that account to appear on search engines for my real name.
I also have a public account that I use for contributing to public projects so it could also help to avoid duplicate accounts in search results.
All accounts should be searchable for username/real name with GitHub's search anyway.
Re: Dear GitHub
#419Hi 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…
Respectfully Jono, I think your reply is symptomatic of the issues at the heart of the matter. GitHub is, whether it expected to be or not, whether it wants to be or not, now at the heart of the OSS community. For the "Director of Community" at a company which plays such an important role in the OSS community, which itself plays an enormously important role in the broader software and civic communities and is populated by abnormally high numbers of passionate and talented contributors, to respond to a HN story with such a high profile by:
1) apologizing for being new
2) extending borderline patronizing praise (the OP likely wanted a response to the issues put forth, not your approval)
& 3) a promise, which you can't necessarily keep, to put eyes on the issue instead of speaking to the issues raised directly.
It's not what I would expect from someone in that role at that sort of company. It's, unfortunately, what I would expect from a company that had the sort of issues raised by the OP.
Re: Dear GitHub
#420Earlier quoted context omitted.
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.
>That being said, we're certainly the minority when it comes to users on the platform. But you're the huge majority of people who give GitHub money. It makes sense not to prioritize the pain points of open-source projects when you lose money by hosting them.
I only pay Github money to host my private repos because their platform also hosts most of the open source projects I use. If enough of those projects leave for a service that does open source better, I'll be happy to follow them. Otherwise I may as well be using Bitbucket or Gitlab.