x/text/unicode/bidi - how to draw attention to two bugs?

[Patrick]

Hello all,

I have opened two issues for the bidi package in the text repository that are clearly bugs. I have provided an analysis for both bugs and a pull request for one. Except for some housekeeping, these issues seem to get no attention.

How is it possible to draw attention to the reports? Both fixes are not nice-to-have feature requests but pointing out (and fixing) incorrect behaviour of the implemented algorithm.

https://github.com/golang/go/issues/71809

https://github.com/golang/go/issues/72089

I know that these are not in the core, so they are of lower priority, but perhaps I can offer more insight on what is going wrong?

I hope it is not silly to ask here... 

 Patrick

[Andy Balholm]

On both of them, someone did a mention of @mpvl (Marcel van Lohuizen), so I assume he is the primary maintainer of the package, and everyone else is waiting for him to do something.

Andy

[Jason E. Aten]

Hi Patrick,

Not to discourage you from pressing for fixes, but 9 times out of 10 I have to just end up forking

open source projects to fix bugs and then just use my own fork. This is the fast path.

Perhaps you've already intuited this. Just to let you know you aren't alone in the experience.

Often the best you can do is to post a link (say, in an Issue on the original)

to your fork with fixes so others can find it, and maintainers can pull from 

it if/when they get to it, and move on to more interesting work...

This is the beauty of open source at work.

Best wishes.

Jason

[Patrick]

Thank you Jason,

I have already forked the code and fixed it in my code. I don't want to bother the maintainer too much, but I also think this should be fixed for other users. I'll wait a bit longer and then ask again.. 

Patrick

[Patrick]

Hi Andy,

thank you. I guess I just wait a bit longer and then ping the maintainer again... Just wondering if there is a best practice among the non-core go libraries.

Patrick