non-binding opinion from an integrator:

dubbo is an RPC layer, so it has a lot of integrators on top. It has a
history in github as well, and people are used to doing issues. I
would suggest maintaining github issues as ecosystem-related change
that is in github is far easier to track this way. For example, I've
made many issues in different dubbo repositories, and cross linked to
zipkin seamlessly. I like that it is easy.

Reply via email to