News for hackers. Stuff that matters.
Re:Dear GitHub by jonobacon on Thursday January 14, 2016 @06:05PM (#10905511)
My main goal in responding was to acknowledge the issues. This is just the start of the process, and by no means the end.

The next step, as you mention, is to bring the right people in. This is why I want to ensure this is raised with our teams inside GitHub to explore ways to rectify some of these concerns.

Re:Dear GitHub by yohann305 on Thursday January 14, 2016 @06:26PM (#10905636)
I'm glad to see someone from github is actually replying on HN and not ignoring this. Thumbs up
Re:Dear GitHub by malexw on Thursday January 14, 2016 @06:31PM (#10905661)
Not just anyone - Jono literally wrote the book on building developer communities: http://www.artofcommunityonline.org/
Re:Dear GitHub by avinassh on Thursday January 14, 2016 @11:25PM (#10907185)
Re:Dear GitHub by rjtobin on Friday January 15, 2016 @03:29AM (#10907972)
He also founded and hosted a fantastic Linux podcast a long time ago: http://www.lugradio.org/
Re:Dear GitHub by jonobacon on Friday January 15, 2016 @12:50AM (#10907477)
You are far too kind. Thanks!
Re:Dear GitHub by noir_lord on Thursday January 14, 2016 @08:36PM (#10906450)
You did the right thing, fast feedback of "We are looking at it" is often better than later feedback of we did "X".

Linode could take a leaf out your book in terms of dealing with people not entirely happy (if I'm been kind) with the way they deal with stuff.

Re:Dear GitHub by rmc on Friday January 15, 2016 @04:33AM (#10908177)
It's much better for Jono to quickly reply and ack the issue, rather than radio silence while we want for them to completly solve the issue.