Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
contribute:bugs:start [2018/11/17 23:05] – moved feature requests to the bottom of the page alexxcons | contribute:bugs:start [2022/11/13 09:23] – Improve phrasing kevinbowen | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
+ | {{ : | ||
====== Bug Reporting and Fixing====== | ====== Bug Reporting and Fixing====== | ||
- | 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 |
+ | |||
+ | * **[[: | ||
+ | |||
+ | ---- | ||
===== Crashes ===== | ===== Crashes ===== | ||
- | We always try to make the software | + | We always try to make the Xfce Desktop Environment |
+ | |||
+ | There are a couple of things you can do to help us resolve these issues and help making the experience of using Xfce better for everyone. We appreciate your help. | ||
- | Nonetheless there are a couple of things you can do to help resolving them: | + | ---- |
==== Search First ==== | ==== Search First ==== | ||
- | Search the [[https://bugzilla.xfce.org|bug tracker]] and look if the issue is already known. Also look through the resolved bugs because the issue might be fixed already, but has not been released or applied downstream. Peeking the [[http://git.xfce.org/xfce|GIT repository]] might help for the latter. | + | Search the [[https://docs.xfce.org/ |
+ | |||
+ | |||
+ | * For a list of currently open bugs, see the [[: | ||
+ | |||
+ | ---- | ||
==== 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 19: | 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 37: | Line 56: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
===== Fixing Bugs ===== | ===== Fixing Bugs ===== | ||
Line 42: | 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/ |
- | + | ||
- | After you managed to download the source code, check [[: | + | |
- | + | ||
- | ===== 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 #xfve-dev first. You might think your idea is brilliant, but there is a high possibility that there are major downsides. | + | To get started, best read our [[contribute/ |
- | 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. | + | [[|Back To Top]] |
+ | ---- | ||
+ | [[ : |