Comment by electic

10 years ago

As a software engineer, I am reminded of when I go to Home Depot and ask someone for help and they say, "Oh, I do not know. I am new here...". I think it is best to come prepared with the right answers. As you can see from the doc, there are a lot of maintainers who have signed this. Perhaps:

- 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.

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.

  • 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.

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.

I appreciate the prompt response. Face-to-face at Home Depot you know the message was received. Online it's nice to get an immediate read receipt with the real reply coming later.