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.
I'm glad to see someone from github is actually replying on HN and not ignoring this. Thumbs up
Not just anyone - Jono literally wrote the book on building developer communities: http://www.artofcommunityonline.org/
It is also freely available as PDF - http://artofcommunityonline.org/Art_of_Community_Second_Edit...
He also founded and hosted a fantastic Linux podcast a long time ago: http://www.lugradio.org/
You are far too kind. Thanks!
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.
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.
Re:Dear GitHub
by martin-adams on Thursday January 14, 2016 @06:10PM
(#10905537)
I personally prefer someone to at least acknowledge someone now owns the issues than to wait in silence while they gather the right people and formulate a concrete response. That doesn't happen quickly in some cases and the silence can exacerbate the issue, which ironically is why this hit HN in the first place.
- Note the feedback.
- Bring in the right folks to consult with on your end.
- Write a public response with concrete information (should be first interaction).
- Finally, reach out to the authors of this post. Perhaps, getting them more clarity on your roadmap and your thought process will go a long way in resolving matters like this with high profile maintainers.