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:01] – [Bug Reporting abd Fixing] alexxcons | contribute:bugs:start [2019/02/26 23:24] – [Fixing Bugs] alexxcons | ||
---|---|---|---|
Line 2: | Line 2: | ||
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:// | ||
- | |||
- | ===== 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 52: | Line 42: | ||
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/ |
+ | |||
+ | Read our [[contribute/ | ||
+ | ===== 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 // | ||
- | After you managed to download the source code, check [[: | + | Obviously it would benice if you could write a patch that implements the new feature. |