Chris Wanstrocity is an inept leader, social activists roam the halls in self glory about their contributions to the world while Kakul spends money on retreats and hires senior product people who have zero open source or dev ops experience. This company needs intensive care with new leadership asap or they will be doomed, Gitlab is salivating right now.
Dear GitHub
211–220 of 491 posts
Re: Dear GitHub
#212We need world class, modern, distributed bug tracking now. If you google around for this technology, a lot of nice ideas, many using git itself as transport, were poking around, and around 2009 they started falling silent. Why? Because GitHub started up and everyone just buzzed over to it like so many moths to a flame, having learned nothing from places like Sourceforge about what happens when 90% of the open source…
This. I'm a big fan of Github, but it bothers me that this single service is the centerpiece of most OSS projects. We see it every time Github goes down and virtually nobody can be productive anymore.
I hope to see a version control system on top of IPFS some day.
Re: Dear GitHub
#213I think if these people have that many issues with GitHub, they should find a replacement. That's what happened in the Node community and it led to a better Node. That's a big list of complaints and GitHub doesn't have much incentive to fix 'em except to silence a bunch of cry babies that are bitching about a free tool.
Re: Dear GitHub
#214Hi 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 thing I would love to see for my own projects is a way to temporarily completely block off contributions on threads by people who only watched/starred the repository for less than 48 hours or something like this.
When people submit your issue tracker to hackernews/reddit/twitter all hell breaks lose and time gets wasted for nothing.
Re: Dear GitHub
#215I 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 is valuable, it's just the form that Github forces it into (comments) winds up looking spammy. Make it a counter - simple enough.
Re: Dear GitHub
#216I'd settle for just a fix to the (minor) data-loss bug that I reported nearly a year ago, and which still crops up once a month or so.
That, and something for code review. Pull Requests are terrible for code review, and it wouldn't take that much to make them so much better.
Re: Dear GitHub
#217Earlier quoted context omitted.
> 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. There are multiple ways to go around this, OpenID, Mozilla Persona, or any third-party authenticator. > The final thing is just name recognition. Peop…
I just realized that Persona is going to be discontinued. Unfortunate, but alternatives can be whipped up I guess. https://developer.mozilla.org/en-US/Persona > On November 30th, 2016, Mozilla will shut down the persona.org services. Persona.org and related domains will be taken offline.
We're currently working on exactly that. If you want to be part of this, swing by the channel. Details and backlog here:
Re: Dear GitHub
#218Is this a case of the squeakiest wheels getting the grease? What if these problems aren't representative of the overall user base? What if far more people prefer a more simple, minimalistic interface than an ultra-customizeable interface with myriad custom actions and events. I've always appreciated software that deliberately keeps things simple (Basecamp and Workflowly come to mind). It sounds like these people want a full blown Jira/Stash installation.
Re: Dear GitHub
#219I am interested in understanding how much recurring revenue Github is receiving for hosting these projects.
Re: Dear GitHub
#220Earlier 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…
An open question is how the community should provide feedback. Perhaps if Github used their own issues system to gather feedback on Github itself, they'd more rapidly improve it. I'm sure they'd feel a lot of these pain points in a far sharper, more visceral way if they were subjected to them daily.
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.