Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
contribute:bugs:start [2018/11/17 23:00] – moved "fixing bugs" to the end of the page alexxcons | contribute:bugs:start [2022/11/13 09:23] (current) – Improve phrasing kevinbowen | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bug Reporting | + | ~~NOTOC~~ |
+ | {{ : | ||
+ | ====== 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 | + | One of the most useful tasks that we rely on the community for is the testing and reporting of bugs. Since Xfce runs on various |
- | ===== 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. | + | ===== Crashes ===== |
- | Afterwards | + | We always try to make the Xfce Desktop Environment as stable as possible; but, there is always |
- | Obviously its also nice if you can write a patch that implements | + | There are a couple of things |
- | ===== Crashes ===== | + | ---- |
- | We always try to make the software as stable as possible, but there is always a possibility a crash or segfault can occur. To problem with crashes is that they are not always reproducible by the developers, this makes it quite often hard to track-down | + | ==== Search First ==== |
+ | Search the [[https:// | ||
- | Nonetheless there are a couple of things you can do to help resolving them: | ||
- | ==== Search First ==== | + | * For a list of currently open bugs, see the [[:contribute: |
- | Search the [[https:// | + | |
+ | ---- | ||
==== Report ==== | ==== Report ==== | ||
+ | |||
+ | |||
+ | When writing your bug report, try to be as descriptive as possible, but avoid verbosity; Mozilla has a nice guide on [[https:// | ||
If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | ||
Line 29: | Line 35: | ||
If the developer cannot reproduce it, he might ask for a // | If the developer cannot reproduce it, he might ask for a // | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
==== Backtraces ==== | ==== Backtraces ==== | ||
Line 47: | Line 56: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
===== Fixing Bugs ===== | ===== Fixing Bugs ===== | ||
Line 52: | Line 64: | ||
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 attaching a patch file to the reported bug. ( "git format-patch" | 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 attaching a patch file to the reported bug. ( "git format-patch" | ||
- | Not familiar with git? [[contribute/ | + | Not familiar with git? [[contribute/ |
+ | |||
+ | To get started, best read our [[contribute/ | ||
- | After you managed to download the source code, check [[:xfce:building|this manual]] to see how to build a package from it. | + | [[|Back To Top]] |
+ | ---- | ||
+ | [[ :start:|Return to Main Xfce documentation page]] |