I can't speak for PingCAP in general, but I know that many of PingCAP's Rust projects are part of the TiKV org [1], which is explicitly trying to become more community-oriented as part of their move into the CNCF (I work for PingCAP on TiKV). This message won't reach far, but if somebody finds themselves having difficulties contributing to TiKV or communicating with TiKV maintainers, and they speak up on the TiKV slack, somebody will definitely take notice and try to help.
Not knowing the specifics of your experience, it might help to consider that most of PingCAP are Chinese, and some communicate in English better than others. In public forums like the issue tracker, they write in English to include the global software development community, but for some it is quite challenging.
I'm hopeful that the PingCAP process will improve and their projects will become easier to contribute to.
Sure, you might had the feeling that you were not treated in the most friendly way, but after 2 loooong years, after the feedback from PingCap's core team member, maybe time to just move on? If you really find PingCap is not friendly enough to the issues you raised (which is never the case to me or anyone I am aware of), you should probably start your own much more user friendly open source project and set an example for everyone.
> You raised the exact same issue 2 years ago on NH, that issue got fully addressed by both PingCap's core team member and other NH users.
Not only was it fully addressed, but it was fully addressed in a polite manner which makes the OP's comment even more bizarre. I've evaluated Pingcap stuff before in the past and I've seen them posting on HN quite a few times as well. I don't think I've ever seen an instance of them being rude. In fact, their comments are usually quite informative and helpful.
Briefly looking into closed TiDB issues, I also see no instances of rudeness or issues being closed without comment.
OP, what is your motive for defaming Pingcap?
Some comments [1]:
"@winkmichael Thanks for your feedback! Could you send me the log of tidb-server?"
"The sets statements missing a , should be /! instead of /!."
"@winkmichael Sorry, I misunderstood your issue because the * is eaten by Markdown format. I clicked edit button, then got the original text.
The error message line 6 is the line of a single statement, not the file. So the statement that failed to parse is not included, probably it's the CREATE TABLE statement.
Do you still have that dump file?"
"@winkmichael we haven't heard anything from you on this issue in a long time, and we're unable to reproduce it without some more information, so I'm going to close it now. If you run into anything like this again, please open up a new issue and we'll be happy to take a look!"