I would just love if they could add target _blank on all the links in comments and issues. I'm constantly navigating away from the issue to view links in question and then realizing the tab with the issue is gone.
Dear GitHub
101–110 of 491 posts
Re: Dear GitHub
#102I work at a large company with a central GitHub Enterprise instance, and we use GitHub as a code-reviewing and code-hosting platform. Everything else (including build-automation) is integrated through web-hooks to Atlassian tools for many of the reasons noted in this letter. It works for us, but I am hopeful that GitHub will listen and maybe someday we can have everything on there.
Re: Dear GitHub
#103I 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?
For a very large percentage of young developers I work with, "Git" and "GitHub" are synonyms. GitHub has made themselves literally synonymous with version control to a large number of people. That's a lot of social momentum that a competitor has to overcome. In light of that, it's not that surprising at all that GitHub has become complacent.
Re: Dear GitHub
#104All this problems seem to me like good problems to have.
They all seem to stem from the fact that github is too successful. And too many people are on github and too many people are using it, often in wrong ways.
Of course github should solve them all. But still, it's still better to have problems with too many people and too much interest, than have the opposite problem - dying platform that people are leaving (see: sourceforge and Google Code).
Re: Dear GitHub
#105Do the undersigned send any money to github? It might be better to phrase your demand in the form of a question, "how much can we pay you to do this work for us?"
Yes, I do. If it was OSS I would PR the feature personally.
Re: Dear GitHub
#106I like GitHub issues as they are. I wouldn't like to force people to adhere to a particular format when reporting problems. I find it strange that some project maintainers get annoyed when people use the issues section to post questions. What's wrong with that? A question can reveal design failures about your software... Maybe if your software was better designed, people wouldn't be asking the question to begin with.…
>I wouldn't like to force people to adhere to a particular format when reporting problems.
The thing is, if they implemented issue formatting in the way the posted document describes, the default would be exactly what it is now. Giving maintainers more control can't possibly be a bad thing.
Re: Dear GitHub
#107I 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…
It's a momentum thing I think. A big part of the Github platform mirrors a social media platform. When you meet a developer, you check out what they're up to on Github just like you might check on a friend's status on Facebook. Like Twitter, it's a way to get your name out there.
Also, I don't want to have to maintain an account on a Gitlab (or equivalent) server for every project. Anyone who has enough interest to troll through issues on a project or open an issue already has a Github account. It lowers the barrier to entry for your project.
The final thing is just name recognition. People trust code from Github. They shouldnt, but a Github URL legitimizes your project more than git.abrakadoodle.io.
Re: Dear GitHub
#108It'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…
Yeah, I'd honestly like for a website that actually focused on "Social Coding" rather than the Enterprise Money that GitHub is focusing on. Tbh, that is what GitLab, Bitbucket does also which is why they really are only effective as replacements rather than improvements upon.
I wonder if threads like this keep popping up if people will say "Fuck it" and build an OSS Github clone that focus on being the Reddit of Code/Git rather than another Version Control Enterprise product.
I'd do it but I'm an asshole, not a community builder.
EDIT:
Since I'm in the edit window and its complaining I submit too fast:
Tbh, the problem with Kallithea SCM and Trac is they aren't really built to generate network effects. They both suffer from the same problem as literally every other unsuccessful Github competitor has:
1) You need something built to generate a network effect first, other considerations second, to successfully compete.
2) You need to then leverage that network to chase Corporate money.
GitHub seems to be neglecting #1 in favor of #2 and that imbalance is an opportunity if someone can exploit it. However, that requires someone who is good at being a community builder rather than a software dev.
Re: Dear GitHub
#109I've felt the same way. The worst bit is notifications, so I get a notification that someone replied to an issue I opened. How do I get there? It's not in my notification page, I have to go to the email and click the link from there. Things get missed.
GitHub needs to step it up. They got to the top first, but can they stay there?
Re: Dear GitHub
#110I 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…
+1 isn't spam. It's valuable. However the implementation of how people can +1 an issue that's very important to them is the point. There should be a voting system.
Spam would indicate that +1 adds no value.. But it does! If I have an issue with no comments, no indication of its importance to the users, then I would deprioritize that issue over another one that has lots of activity.