Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
contribute:bugs:start [2014/03/05 13:30] – created nick | contribute:bugs:start [2019/02/24 21:22] – [Feature Requests] ochosi | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bug Reporting ====== | + | ====== Bug Reporting |
One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https:// | One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https:// | ||
- | |||
- | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and then submitting a patch file. | ||
- | |||
- | ===== Feature Requests ===== | ||
- | |||
- | Although the philosophy of Xfce is to find the correct balance between features and lightweight, | ||
- | |||
- | This right approach for larger changes is to discuss them on the mailing list first. You might think your idea is brilliant, but there is a high possibility other users. | ||
- | |||
- | Afterwards a bug can be opened in the bug tracker and make sure the // | ||
- | |||
- | Obviously its also nice if you can write a patch that implements the feature, but its not a necessity. | ||
===== Crashes ===== | ===== Crashes ===== | ||
Line 30: | Line 18: | ||
In the description provide a short way to reproduce the crash. Also run the application in a terminal and look if there are console warnings, put those in the bug as well. | In the description provide a short way to reproduce the crash. Also run the application in a terminal and look if there are console warnings, put those in the bug as well. | ||
- | If the developer cannot reproduce it, he might ask for a // | + | If the developer cannot reproduce it, he might ask for a // |
+ | |||
+ | ==== Backtraces ==== | ||
+ | |||
+ | If you do get an Xfce application to crash, it's best to detail exactly what you were doing that led to the crash. In addition, we need the // | ||
+ | |||
+ | The sites below provide guidance from the respective distributions how to remedy this situation so you can provide all the info we need to fix your issue. | ||
+ | |||
+ | In case of panel plugins there is some additional information on [[: | ||
+ | |||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[https:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[https:// | ||
+ | |||
+ | ===== Fixing Bugs ===== | ||
+ | |||
+ | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving | ||
+ | |||
+ | Not familiar with git? [[contribute/ | ||
+ | |||
+ | After you managed to download the source code, check [[:xfce: | ||
+ | |||
+ | ===== Feature Requests ===== | ||
+ | |||
+ | Although the philosophy of Xfce is to find the correct balance between features and lightweight, | ||
+ | |||
+ | The right approach for larger changes is to discuss them on the mailing list, or on #xfce-dev (on freenode) first. You might think your idea is brilliant, but there is a high possibility that there are major downsides. | ||
+ | |||
+ | Afterwards a bug can be opened in the bug tracker. Make sure the // | ||
+ | |||
+ | Obviously it would benice if you could write a patch that implements the new feature. |