Revisiting the Bug Council: Fixing GitHub Issues' Shortcomings

The author recounts their experience using BugSplat for project management in early Silicon Valley, adhering to four key principles: all tasks are recorded as bugs, bugs have a unified and detailed schema, each bug is assigned to only one person, and flexible query functionality. The author finds that today's systems like GitHub Issues fall far short of BugSplat's efficiency, lacking a comprehensive schema, having diffuse responsibility, and limited query capabilities. The article concludes by describing how the author's team is improving the open-source project Gitea to address these shortcomings, ultimately achieving the ability to sort bug lists by priority.