virtualbox.org

OK, I scanned the Trac documentation which is very useful if I want to set up my own copy of Trac on my own LAMP system. I can also find VB tickets because they are indexed by Google, and once I've found them, I can append my own comments, but can someone point me to the documentation on

1. How to run web queries against the VB Trac instance?
2. How to raise my own ticket?

_________________

PS. I did a few more searches with google: "create ticket site:virtualbox.org" which came up with this reference: VirtualBox — Create New Ticket, and using google Link: searches chained back to VirtualBox — Bucktracker which is referenced by VirtualBox — User accounts which is not referenced by anything!

When you click on "Help / Guide" this takes you to the Trac documentation; NOT this site's guide.

Guy's, you need to be a guru to find your way around this site.

The relevant page is two clicks from the main page: http://www.virtualbox.org/wiki/Bugtracker

I agree that we could set things up better, but I don't think it's that bad right now.

TerryE wrote:VirtualBox — Create New Ticket, and using google Link: searches chained back to VirtualBox — Bucktracker which is referenced by VirtualBox — User accounts which is not referenced by anything!

sandervl wrote:The relevant page is two clicks from the main page: http://www.virtualbox.org/wiki/Bugtracker

Sander, I think that we said the same thing but how do you get to this link from http://www.virtualbox.org? There no link in the menu tree or FAQ "How do I report a bug?" Searching for "Error Report" is no good; you need use a magic phrase like "Bug Tracker" and the link you give is buried in the search returns.

I don't want to labour a point that I've already raised in "Guys, is it time to take a new look at your support model?", but this was a serious point that I feel merited a response from one of you.

Well, we don't want to make it too easy to file a bug report. If we make it similar to one-click shopping, you can imagine what will happen.

I suppose I could add it to the FAQ.