[opensuse] Novell Please make Bugzilla for OpenSuse really Open.
I's like to suggest that bugs related to openSuse be made available to the internet as a whole by allowing them to be crawled and indexed by google, yahoo, and any other search engines that want them. There is a lot of good information, including solutions to problems that appear in the bugzilla data base that can not be found on google simply because google is not allowed to crawl Novell's bugzilla. A google search like this: unable to burn dvd k3b does not show Bug 242009, or ANY other results from Novell's bugzilla even though a bugzilla search will show 87 hits. Searching with google's site specific search will always show results like: Your search - dvd k3b site:bugzilla.novell.com - did not match any documents. I don't think an "open" distribution should require searching in a specific place. Bugzilla itself has limited search capabilities when compared to google. Bugs frequently have relevance beyond a specific distro. Note:--- I realize that the Novell Bugzilla also contains bugs related to proprietary packages and confidential bugs. However it would seem that a script could echo all non proprietary bugs to another server, (or simply build a page of links such that the crawlers could find them). -- _____________________________________ John Andersen
On Sunday, 4. February 2007 00:49:29 John Andersen wrote:
I's like to suggest that bugs related to openSuse be made available to the internet as a whole by allowing them to be crawled and indexed by google, yahoo, and any other search engines that want them.
I would rather enjoy a Bugzilla speed-up rather than it being even slower because of bots crawling it all the time... :-)
I realize that the Novell Bugzilla also contains bugs related to proprietary packages and confidential bugs. However it would seem that a
Those are only visible when you're logged in and have the right privileges. Bye, Steve -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007, Stephan Binner wrote:
On Sunday, 4. February 2007 00:49:29 John Andersen wrote:
I's like to suggest that bugs related to openSuse be made available to the internet as a whole by allowing them to be crawled and indexed by google, yahoo, and any other search engines that want them.
I would rather enjoy a Bugzilla speed-up rather than it being even slower because of bots crawling it all the time... :-)
Well perhaps Novell can use all that money they got from Microsoft to buy some new hardware. Are you calling for donations in this regard? -- _____________________________________ John Andersen
On Feb 04, 07 23:12:46 -0900, John Andersen wrote:
On Sunday 04 February 2007, Stephan Binner wrote:
On Sunday, 4. February 2007 00:49:29 John Andersen wrote:
I's like to suggest that bugs related to openSuse be made available to the internet as a whole by allowing them to be crawled and indexed by google, yahoo, and any other search engines that want them.
I would rather enjoy a Bugzilla speed-up rather than it being even slower because of bots crawling it all the time... :-)
Well perhaps Novell can use all that money they got from Microsoft to buy some new hardware. Are you calling for donations in this regard?
First step firt, please. There is no need to suggest solutions as long as Novell management does not know there is a problem. cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
I's like to suggest that bugs related to openSuse be made available to the internet as a whole by allowing them to be crawled and indexed by google, yahoo, and any other search engines that want them.
I agree with this suggestion and also with Darryl's additional reason in a separate message, so would like to understand how to make progress. The discussion at the moment does not seem to be going anywhere. Stephan Binner wrote:
I would rather enjoy a Bugzilla speed-up rather than it being even slower because of bots crawling it all the time... :-) Well perhaps Novell can use all that money they got from Microsoft to buy some new hardware. Are you calling for donations in this regard?
Juergen Weigert wrote:
First step firt, please. There is no need to suggest solutions as long as Novell management does not know there is a problem.
Do you mean that Novell management need to be informed of (a) a performance problem with bugzilla or (b) the lack of indexing of bugzilla ? Should Suse employees inform Novell management or should general Suse users? What channels should be used to make such report/request? Is Novell actually likely to do anything? If they do not, is there an alternative strategy of forking the bugzilla and running an open version for opensuse? Having a bugzilla for a supposedly open project organized in such a way that users and potential contributors cannot see some bugs seems to me to be a serious and fundamental flaw in an open project! Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 06 Feb 2007 11:25:24 +0000, Dave Howorth wrote:
Having a bugzilla for a supposedly open project organized in such a way that users and potential contributors cannot see some bugs seems to me to be a serious and fundamental flaw in an open project!
Keep in mind that bugzilla is used for *all* Novell products, many of them closed source (eg. Netware, Border manager etc.). There are also our enterprise products like SLED and SLE where customers must pay for support and maintenance. So access *must* be restricted. But access to bugs pertaining to openSUSE releases are freely accessable. So I don't see where there's a flaw. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
But access to bugs pertaining to openSUSE releases are freely accessable. So I don't see where there's a flaw.
and then three minutes later you wrote:
Yes, this is bothersome and should IMHO be changed, even if that means that developers would have to keep parallel bugs, one open and one not.
So which is it Philipp? Is there a problem or not? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 07 Feb 2007 10:52:22 +0000, Dave Howorth wrote:
So which is it Philipp? Is there a problem or not?
There is a problem but not where you stated that it would be :) Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
On Wed, 07 Feb 2007 10:52:22 +0000, Dave Howorth wrote:
So which is it Philipp? Is there a problem or not?
There is a problem but not where you stated that it would be :)
I'm not amused. I don't think you read my message properly. My statement on which you commented was based on Darryl's message which was exactly about the problem to which you responded. FWIW, I also think that open indexing is also desirable for the bug system of an open project. google et al should be allowed to index the bug reports. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello,
* Philipp Thomas
But access to bugs pertaining to openSUSE releases are freely accessable. So I don't see where there's a flaw.
The problem is -- and I hit that problem myself before I was at suse -- that some openSUSE bugs get closed as duplicate, and the duplicate is a SLE{S,D} bug. Regards, Bernhard
Hi, * Bernhard Walle (bwalle@suse.de) [20070207 12:43]:
The problem is -- and I hit that problem myself before I was at suse -- that some openSUSE bugs get closed as duplicate, and the duplicate is a SLE{S,D} bug.
Yes, I do know that and I do think we'd need a policy to only never close an openSUSE bug in such cases specifically because the SLE bug won't be public anymore. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-02-07 at 12:43 +0100, Bernhard Walle wrote:
Hello,
* Philipp Thomas
[2007-02-07 10:42]: But access to bugs pertaining to openSUSE releases are freely accessable. So I don't see where there's a flaw.
The problem is -- and I hit that problem myself before I was at suse -- that some openSUSE bugs get closed as duplicate, and the duplicate is a SLE{S,D} bug.
Since SLE[S,D] is based on openSUSE why not mark the SLE[S,D] bug as a duplicate of the openSUSE one instead? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 07 Feb 2007 07:37:04 -0500, Kenneth Schneider wrote:
On Wed, 2007-02-07 at 12:43 +0100, Bernhard Walle wrote:
Since SLE[S,D] is based on openSUSE why not mark the SLE[S,D] bug as a duplicate of the openSUSE one instead?
Because you then loose the ability to discuss with partners and customers in private, which is crucial. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-05 01:01, Stephan Binner wrote:
On Sunday, 4. February 2007 00:49:29 John Andersen wrote:
<snip>
I realize that the Novell Bugzilla also contains bugs related to proprietary packages and confidential bugs. However it would seem that a
Those are only visible when you're logged in and have the right privileges.
Operative phrase "have the right privileges." However, too often does a bug get marked as a duplicate of a bug that is restricted to Novell employees and enterprise customers, even when it is present in versions 9.3 through 10.2. It would be nice, for example, to be able to know if there is any progress in the Yast firewall module bug, where you cannot change the allowed services on the external interface. This is rather different from John's suggestion/problem, but is nevertheless a major source of frustration for anyone using the bugzilla. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 05 Feb 2007 11:31:32 -0600, Darryl Gregorash wrote:
However, too often does a bug get marked as a duplicate of a bug that is restricted to Novell employees and enterprise customers, even when it is present in versions 9.3 through 10.2.
Yes, this is bothersome and should IMHO be changed, even if that means that developers would have to keep parallel bugs, one open and one not. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07-02-2007 at 11:45, Philipp Thomas
wrote: On Mon, 05 Feb 2007 11:31:32 -0600, Darryl Gregorash wrote: However, too often does a bug get marked as a duplicate of a bug that is restricted to Novell employees and enterprise customers, even when it is present in versions 9.3 through 10.2.
Yes, this is bothersome and should IMHO be changed, even if that means that developers would have to keep parallel bugs, one open and one not.
That can not be a real suggestion now.. I don't believe you're serious in this. If a DEV has to start to work on twice the same bug, and administering all this work.. will he ever have time to fix bugs? I had very good experience with BugZilla.. whenever I hit a bug that's closed because it was initially opened for a EnterPrise product, I drop the dev a message... most of the time the referred one get's opened very quick afterwards... Maybe a solution would be to have BugZilla itself check if the linked BugZilla entry is available and give a report to Admins as soon as a linked one would point to a closed ( non public) bug report. For sure we should NOT put more work on the DEVs... keep them doing what they can do bets: fixing (and introducing new) bugs :-0 Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 07 Feb 2007 10:49:27 +0100, Dominique Leuenberger wrote:
On 07-02-2007 at 11:45, Philipp Thomas
Yes, this is bothersome and should IMHO be changed, even if that means that developers would have to keep parallel bugs
That can not be a real suggestion now.. I don't believe you're serious in this.
Oh yes, I am. But I guess this would be a very small number of bugs.
I had very good experience with BugZilla.. whenever I hit a bug that's closed because it was initially opened for a EnterPrise product, I drop the dev a message... most of the time the referred one get's opened very quick afterwards...
Yes, I know that this works. But a reminder for developers to please *not* do it in the first place wouldn't be a bad thing.
Maybe a solution would be to have BugZilla itself check if the linked BugZilla entry is available and give a report to Admins as soon as a linked one would point to a closed ( non public) bug report.
I don't think so. Remember that bugs in *all* Novell products are tracked in bugzilla. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Bernhard Walle
-
Darryl Gregorash
-
Dave Howorth
-
Dominique Leuenberger
-
John Andersen
-
Juergen Weigert
-
Kenneth Schneider
-
Philipp Thomas
-
Philipp Thomas
-
Stephan Binner