aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKevin Chabowski <kevin@kch42.de>2012-05-20 14:07:34 +0200
committerKevin Chabowski <kevin@kch42.de>2012-05-20 14:07:34 +0200
commit40cafe0ca0699647781e8953b413622b8e341913 (patch)
tree94dc9c1f207cce61aa7d4d273a272e0b1895b9d8
parent3765c31f7cc8b86d4bda1a7fd5f00533b322b9c0 (diff)
downloadratatoeskr-cms-40cafe0ca0699647781e8953b413622b8e341913.tar.gz
ratatoeskr-cms-40cafe0ca0699647781e8953b413622b8e341913.tar.bz2
ratatoeskr-cms-40cafe0ca0699647781e8953b413622b8e341913.zip
HACKING file contains some rules for contributing.
-rw-r--r--HACKING13
1 files changed, 13 insertions, 0 deletions
diff --git a/HACKING b/HACKING
new file mode 100644
index 0000000..f21c491
--- /dev/null
+++ b/HACKING
@@ -0,0 +1,13 @@
+Some rules for hacking on Ratatöskr
+===================================
+
+All in all, there are not many rules, Cowboy Coding FTW!
+
+But here are some rules / advice, to make cooperation easier:
+
+* Use the "develop" branch in git, not the "master" branch. The master branch
+ should by now only contain releases (including beta versions). But for the
+ work between releases, please use the develop branch from now on.
+* More an advice than a rule: When implementing a particular feature, make a new
+ branch for that feature. This should make things more clear for other people
+ that merge your changes. \ No newline at end of file