On Wed, 16 May 2012 17:22:12 -0400, Felix Miata wrote:
From a technical standpoint, there really isn't any other than perhaps to increase the flexibility for us to make modifications to the UI.
Bugs with restricted access such as the above warn about discussion of sensitive information without defining what information is sensitive, with the result that essentially the whole bug should be considered sensitive and not open to outside discussion. This is antithetical to the FOSS openSUSE, and an important reason why I believe SUSE needs a separate bug tracker from that which Novell uses for things other than SUSE. IIRC, RedHat/Fedora has no corresponding limitation.
RedHat/Fedora have different goals than SUSE itself does, though. I agree that principally bugs related to openSUSE and the openSUSE infrastructure should be open to the public. The question of access need not lead to a large scale "it must be separated" move, because again, that's not an undertaking to be taken lightly, going to take considerable effort and resources to migrate the existing data (and I don't think we want to lose that history), and really beyond the scope of streamlining the bug reporting/resolution process. That's not to say visibility isn't important. But when there is a visibility issue, we should report it and find out why it's been restricted - and get the restriction lifted unless there is a compelling reason for it to not be lifted (and I'd say those should be fairly few and far between). Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org