Changes between Version 79 and Version 80 of Bugtracker

Timestamp:

Aug 13, 2013 6:13:48 AM (11 years ago)

Author:

Michael Thayer

Comment:

More bold bits

Bugtracker

@@ -3 +3 @@
 This site offers a public bugtracker. In case you encounter problems with !VirtualBox or have other suggestions for improvements, you can use this facility to report those issues, which will then be called a "ticket". Each such ticket receives a unique number that you can later refer to in order to see if any progress was made, or add comments to it.  
 
-'''Please be aware''' that although we (the core team) invest a lot of effort into user bug reports, we receive more bug reports than we can read, let alone resolve, so we tend to focus on tickets which seem important to us - because they impact a lot of people, or some people very severely, or paying customers, or look like something which can be fixed quickly.  Just as we cannot make demands of you, neither can you demand that we work on a particular issue, however important it may seem to you.
+'''Please be aware''' that although we (the core team) invest a lot of effort into user bug reports, '''we receive more bug reports''' than we can read, let alone resolve, so we tend to focus on tickets which seem important to us - because they impact a lot of people, or some people very severely, or paying customers, or look like something which can be fixed quickly.  Just as we cannot make demands of you, '''neither can you demand''' that we work on a particular issue, however important it may seem to you.
 
-'''However''', !VirtualBox is open source software.  Fixing bugs is a process of collaboration between reporters who can reproduce and study them and developers who fix them (the two groups can overlap).  And if the core team are not able to work on a particular issue someone else or you yourself can do so and we can integrate the solution if it does not impact other people.  A good bug ticket is a great aid for whoever chooses to work on a problem.
+'''However''', !VirtualBox is open source software.  Fixing bugs is a process of collaboration between reporters who can reproduce and study them and developers who fix them (the two groups can overlap).  And if the core team are not able to work on a particular issue '''you or someone else can also work on it''' and we can integrate the solution if it does not impact other people.  A good bug ticket is a great aid for whoever chooses to work on a problem.
 
 So bearing that in mind, there are a number of things you can do to '''improve the chances of getting your problem solved'''.
  * '''Do some research''' (e.g. using search engines, our [http://forums.virtualbox.org forums] and [search:?link&q=&ticket=on existing bug tickets]) before creating a ticket.  Your problem may well be known; someone (we or others) may have solved it or be working on a solution; you may find out enough to solve it yourself.
  * You should find out and understand as much about the problem as possible before creating the ticket, so that you can create '''as clear, as complete and as concise''' a description as possible for whoever (us, someone else, yourself) attempts to fix the problem.  Consider using the forums to get help with this.
- * As many problems involve using '''software or operating systems with which we are not familiar''', or do not even have access to, with !VirtualBox, you can help us by using your own knowledge of the software and the help channels available for it to analyse the problem "from the other side" and find out the simplest possible way to reproduce it.
+ * As many problems involve using '''software or operating systems with which we are not familiar''', or do not even have access to, with !VirtualBox, you can help us by using your own knowledge of the software and the help channels available for it to '''analyse the problem yourself''' and find out the simplest possible way to reproduce it.
  * Describe as precisely as you can '''how to reproduce the problem''', bearing in mind that it may be triggered by something special on your own computer system.  It is often next to impossible for a developer to fix a problem that they cannot reproduce.  It may help to find other people with the same problem and compare notes.
  * '''Choose a summary carefully.'''  The bug tracker and ticket notifications are mainly seen by (busy) developers, and unless a summary catches their eye and looks related to the things they as an individual work on the ticket may not even be read.