Snapcraft has at least three unsynced bug lists: <https://bugs.launchpad.net/snapcraft> (currently 425 open bugs) <https://bugs.launchpad.net/ubuntu/+source/snapcraft> (currently 53) <https://github.com/snapcore/snapcraft/issues> (currently 31). This introduces all the usual problems of multiple to-do lists: * It’s harder to tell whether an issue has been reported already, so duplicates are more likely. * It’s harder to to tell which are the most important things to work on. * Someone fixing one bug is less likely to notice when another bug would be best fixed at the same time. Since Snapcraft is a cross-distro tool, it may be necessary to keep at least separate upstream and downstream bug lists. But it may be possible to avoid having two upstream bug lists. Using GitHub for issue tracking is optional. "Issues are tracked on launchpad" <https://github.com/snapcore/snapcraft/issues/100> is a signpost that points people to Launchpad, but it doesn’t explain why GitHub Issues are open for Snapcraft at all. <https://github.com/snapcore/snapcraft/issues/1506#issuecomment-330279314> gives a little more explanation: “We only use github issues here in order to use Projects”. So, one solution would be to find an alternative to using GitHub Projects. Another approach would be to use GitHub exclusively for upstream issue tracking. Things that would lessen the problem: * Mention Launchpad for bug reporting more prominently in the README * Migrate and close all the GitHub issues except for the #100 signpost.