Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
contribute:bugs:start [2018/11/17 23:04]
alexxcons Fixed grammar
contribute:bugs:start [2019/02/26 23:24] (current)
alexxcons [Fixing Bugs]
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://​bugzilla.xfce.org|bug tracker]]. 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://​bugzilla.xfce.org|bug tracker]].
- 
-===== Feature Requests ===== 
- 
-Although the philosophy of Xfce is to find the correct balance between features and lightweight,​ it is still possible to request new features. 
- 
-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. 
- 
-Afterwards a bug can be opened in the bug tracker. Make sure the //​Importance//​ is set to //normal// and //​enhancement//​. 
- 
-Obviously it would benice if you could write a patch that implements the new feature. 
  
 ===== 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"​ is the preferred way to create a patch file )  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"​ is the preferred way to create a patch file ) 
  
-Not familiar with git? [[contribute/​dev/​git/​start|This manual]] will help you to get started.+Not familiar with git? [[contribute/​dev/​git/​start|This manual]] will help you to get started. ​
  
-After you managed to download the source codecheck [[:​xfce:​building|this manual]] to see how to build package from it.+To get startedbest read our [[contribute/​dev/​coding/​example|beginners example on how to fix a simple xfce bug]]
 +===== Feature Requests ===== 
 + 
 +Although the philosophy of Xfce is to find the correct balance between features and lightweight,​ it is still possible ​to request new features. 
 + 
 +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 high possibility that there are major downsides. 
 + 
 +Afterwards a bug can be opened in the bug tracker. Make sure the //​Importance//​ is set to //normal// and //​enhancement//​. 
 + 
 +Obviously ​it would benice if you could write a patch that implements the new feature.