Mailinglist Archive: opensuse-project (300 mails)

< Previous Next >
Re: [opensuse-project] bugzilla resolution "OBSOLETE"
On 2012/05/16 19:44 (GMT) Jim Henderson composed:

On Wed, 16 May 2012 21:29:57 +0200, Per Jessen wrote:

I'm bothered more by SUSE having been disgorged from Novell that it
doesn't have a separate bug tracker to keep SLEx& openSUSE users from
more easily getting overwhelmed trying to use it. cf.
https://bugzilla.novell.com/show_bug.cgi?id=753203

"You are not authorized to access bug #753203." ??

This is an example of what I meant in another thread earlier today: http://lists.opensuse.org/opensuse-project/2012-05/msg00196.html

It doesn't allow me to unrestrict access as Carlos suggested I could.

So it's a bug that Felix submitted with a number of UI requests for
Bugzilla that could make it easier for openSUSE users to use.

The bug itself is outside the scope of the bug management process,
though. Felix, if you want to discuss this on the list, please start a
separate thread. :)

I honestly do not see a reason for having two separate copies of the
same infrastructure.

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.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
To contact the owner, email: opensuse-project+owner@xxxxxxxxxxxx

< Previous Next >