Slashdot Mirror


Public Bug Tracking and Open-Source Policy

Observer writes "Bugs in software are nothing new, but when they're discussed in the open, how do open source projects adapt policy? A major regression in the Gnome project's session manager has seen some major distributions choose to refuse to follow the update rather than drop a major feature. Between Gnome's public bug tracker and similar trackers from distributions which released (and still distribute) the buggy version, months of debate provide an interesting case-study in the way front-line users and developers interact for better or for worse. What lessons can be learned here for release planning, bug triage, and marketing for a major open source project?"

1 of 118 comments (clear)

  1. Re:+1 Transparency by Tolkien · · Score: 0, Redundant

    Keep in mind that the end-user will not be exposed to those internal discussions, although they take place in public, open forums.

    Huh? If they're public and open, the end use can see them. What are you talking about?

    My emphasis.

    Wait, you got modded +5 insightful for that? Let me try!