summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorBenedikt Meurer <benny@xfce.org>2005-01-26 21:34:18 +0000
committerBenedikt Meurer <benny@xfce.org>2005-01-26 21:34:18 +0000
commit9ed3a6cabc28be37c3d08bb263b363593129e5cb (patch)
tree3ae8eeeac68b8f0d5bd9e61b537b5b87b0bb0edc /HACKING
parent9cc8112bc0b41e8dad311a2c3345b187cec8c0ba (diff)
downloadxfce4-dev-tools-9ed3a6cabc28be37c3d08bb263b363593129e5cb.tar.gz
Initial revisionBMEURER_20050126
(Old svn revision: 2260)
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING45
1 files changed, 45 insertions, 0 deletions
diff --git a/HACKING b/HACKING
new file mode 100644
index 0000000..d1b253b
--- /dev/null
+++ b/HACKING
@@ -0,0 +1,45 @@
+Bug tracking system
+===================
+
+Please use the Xfce bugtracking system at http://bugzilla.xfce.org/ to report
+bugs and post feature requests.
+
+
+Patches
+=======
+
+Please submit patches to the Xfce bugtracking system or the xfce4-dev@xfce.org
+mailinglist. Your patch should be in unified diff format (the -u option to
+GNU diff) 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.