summaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2016-02-20 15:03:08 +0200
committerLars Wirzenius <liw@liw.fi>2016-02-20 15:03:08 +0200
commit18d2e571cede45c48e50d69fd25d69df36becbf5 (patch)
tree891dd0deb32f3620e25685b797c1fda747583fde /manual
parentddba78a0a656686bfa608da3af1f2332fd6f7362 (diff)
downloadobnam-18d2e571cede45c48e50d69fd25d69df36becbf5.tar.gz
Write section on develping the code
Diffstat (limited to 'manual')
-rw-r--r--manual/en/700-contrib.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/manual/en/700-contrib.mdwn b/manual/en/700-contrib.mdwn
index 5a6d4d60..7654edd0 100644
--- a/manual/en/700-contrib.mdwn
+++ b/manual/en/700-contrib.mdwn
@@ -156,5 +156,18 @@ nice.
Developing the code
-------------------
+Assuming you already know how to program, it's fairly straightforward
+to work on the Obnam code base. At least it's meant to be so: if you
+have trouble, please ask and point out what's unclear or wrong.
+
+Check out the source from the git server, and read the `README` file
+for details on how to get started, and how to run the automated test
+suite, and how to send patches. See the website for some development
+documentation, including explanations of the on-disk data structures.
+
+Code changes that are not very trivial should be sent in a form that
+can be handled by git. This can be actual patches sent to the mailing
+list, or a URL from which changes can be merged.
+
Project governance
------------------