Last I looked github issues had no good way to express dependencies between issues, which is used a lot in gecko's bugzilla. So you may be right, but I'm not a

Last I looked github issues had no good way to express dependencies between issues, which is used a lot in gecko's bugzilla. So you may be right, but I'm not a MoCo employee so I won't be part of any decision about that. Also consider the cost of moving all the tooling that exists to github (in the specific context of gecko): a migration needs to bring a lot of benefits, especially if you take into account that gecko's canonical repo is a mercurial one, not git. Improving onboarding for new contributors would be nice for sure, but "order of magnitude more contributions" seems optimistic. I mostly expect there would be tons of low quality issues filed.