Mr. Akhiyarov:
I don't know if this is exactly what you are adressing, but I used to answer questions about Cython on SO, as a way to try to help using the technoology. My experience is that, in projects that are 0.x, sometimes the reason for not answering a question is not uninterest, but rather that the question refers to some feature still undeveloped in the technology and the best you could provide is a workaround that might or not be acceptable to other people.
As an example, at some point in Cython you could not declare a pointer to a method as a type (something like, say, ( int ) (MyClass::* method) ( int ) in C++) so my workaround was wrapping it inside a class in C++ that exposes that same pointer - but then every client must have a method that makes it compatible with receiving the pointer that way :/.
Probably not the best, surely not elegant, but it served its purpose.
There were a lot of critics to answers like this, because it involved a lot of C++ writing (which was trying to be avoided in Cython), it was rather hyperbolic, and so on... And in fact, those were valid critics, but, referring to an still undeveloped feature, it is natural some controversy as what is the best way to solve that issue - but that is a discussion I would expect between Cython's developers, not users.
Eventually, as every answer led to pointless discussions I just stopped answering.
I don't really have a suggestion to improve these kinds of situations, but I wanted to point out that, even if interested in answering the questions, sometimes adressing young projects is difficult. I'd be really glad to hear from people who dealt with this issue in a more effective way than I did.
Regards,
Cristián