This seems generic, anyone in github with an issue mentioning openmandriva is listed here.
For my part i was not aware of a place already created for issues. But it’s a good thing for testing process. My idea would be keeping Bugzilla as official tool and a small team test Github issues, until the migration is approved, or rejected. It should be indeed a short time (as the request is long, it was even asked before when we used openproject, before github had project management)
Well, Github, and by extension some alternatives like gitlab, are known to be very userfriendly. Success of Github comes from its userfrienlyness. Attracting users and developers is certainly a good reason to use Github.
If the question is, do we want to depend on a non FOSS service provider, I’m indeed not in favour. There are two things: first we need (I think we need) a tool that integrate every thing into a single environment, both for sysadmin maintainance and development workflow. Is Github the best solution, from a FOSS pov no, but at our current situation yes. It gives visibility to us. See we are even in the UNESCO software heritage.
Github’s api is open, it will be easy, when we are ready, to migrate with a totally FOSS alternative (Gitlab or whatever), and when we do, all is migrated.
Our developers are already in Github, a part of them is almost only in Github. OTOH our users or visitors mainly come to Discourse/forum, and it would be easy to create this workflow:
A user create a post in forum support category, if support team considers it’s a bug, a issue can be opened in github and a single link in discourse to the issue (or even the commit, comment, card etc) create a linkback in github, making it easy for developers to follow the discussion inside discourse from github, and for users to see how the dev are working on the issue. No need to say that for QA it should be easier because there is no third party software where you need another account, not dynamically linked to the others.