@myale the basic way it works is like this :
community.brave.com is for support, feature requests, contributor onboarding, and conversation around Brave.
github.com is where the code lives and is integral to the developers’ workflow.
When someone comes to us with a problem, regardless of the path they took, if the issue is well defined per our posting guidelines and is reproducible, then we create a github issue so that it can be triaged appropriately.
For timeline info see : When will (any subject) happen?
Triage happens because there are way more users than there are developers and there are a near-infinite number of ways a browser can appear to have an issue based on their combination of browser version, computing hardware, network connection, etc etc.
If folks are technically sharp and willing and able to participate in the investigation of issues, they may go straight to github. We try to keep it less technical and more conversational in community.brave.com.
If any of us point you toward github in a thread then it is just to say that our team has received and understands the issue, it will be triaged, and if you are interested in knowing the progress toward resolution, you can check the milestone value.
No milestone = it is unlikely this will be fixed anytime soon by our team.
As always with early startups processes can change as we adapt to make ourselves more efficient. However, I’ll try to keep an eye out and communicate to the community if there is a big shift.
Hopefully this clarifies things a bit.