summaryrefslogtreecommitdiff
path: root/HACKING
blob: e566c86c1832a72c4cd6ef3d6d2411fb5a2e673e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Bug tracking system
===================

Please use the Xfce bugtracking system at http://bugzilla.xfce.org/ to report
bugs and post feature requests.


Notes to developers
===================

If you are a Xfce developer with write access to the Xfce git repository,
and you feel like you want or need to change something in this module,
do not simply commit your changes, unless its really a trivial fix. If it's
a non-trivial change, discuss the change on xfce4-dev@xfce.org first. In
either case, don't forget to update the ChangeLog file before you commit!


Patches
=======

Please submit patches to the Xfce bugtracking system or the xfce4-dev@xfce.org
mailinglist. Your patch should be created with the git-format command (see man
git-format) and it should follow the coding style used by the maintainer.

Please send a patch against a recent version of this package. Patches against
the HEAD branch are most preferable.


Feature requests
================

Please send your feature requests to the Xfce bugtracking system
(http://bugzilla.xfce.org, product Xfce developer tools) with a Severity of
enhancement. Make sure that your feature request wasn't reported already
before; requesting a feature several times won't increase the chance that
it gets added.


Coding Style
============

 - Be sure to use the same indentation rules as the maintainer (esp. important:
   expand tabs).
 - Don't follow the philosophy "If it works, it's right" that most open source
   projects follow. Instead, follow the philosphy "It doesn't work unless it's
   right".
 - If you don't follow the rules above, your patches will be rejected or - in
   case you have write access to the Xfce repository - your changes will be
   reverted!


Release process
===============

 No procedure yet, we have to figure out how to handle this module best.