Address #5700.

1 files changed, 57 insertions, 2 deletions

diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index 000b86a..e933f3a 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -51,8 +51,13 @@ Texts.  A copy of the license is included in the section entitled
 
 @menu
 * Standalone deployment::               Deploy Taler in your homepage
-* Testing components::                  How to make and run tests.
+* Testing components::                  How to make and run tests
 * Releases::                            Releases patterns
+* Code::                                Where to find Taler code
+* Bugtracking::                         How to track Taler bugs
+* Continuous integration::              How CI is currently performed
+* Code coverage::                       Where to find coverage reports
+* Demo and Test::                       Live Taler services
 @end menu
 
 @node Standalone deployment
@@ -131,7 +136,7 @@ $ taler-deployment-arm -i taler-postgres-standalone
 $ taler-deployment-build
 @end example
 
-Now make the configuration file @code{${HOME}/.config/taler.conf}:
+Now make the configuration file @code{$@{HOME@}/.config/taler.conf}:
 @example
 $ taler-deployment-config-generate
 @end example
@@ -341,4 +346,54 @@ filename: taler-exchange-0.1.0.tar.gz
 
 Upload the files in @b{binary mode} to the ftp servers.
 
+@node Code
+@chapter Code
+Taler code is versioned via Git.  For those users without write access,
+all the codebases are found at the following URL:
+
+@example
+git://git.taler.net/<repository>
+@end example
+
+A complete list of all the existing repositories is currently found at
+@code{https://git.taler.net/}.  Note: @code{<repository>} must NOT have
+the @code{.git} extension.
+
+@node Bugtracking
+@chapter Bugtracking
+Bug tracking is done with Mantis (https://www.mantisbt.org/).  All the
+bugs are then showed and managed at @code{https://bugs.gnunet.org/}, under
+the "Taler" project.  A registration on the Web site is needed in order to
+use the bug tracker.
+
+@node Continuous integration
+@chapter Continuous integration
+CI is done with Buildbot (https://buildbot.net/), and builds are triggered
+by the means of Git hooks.  The results are published at @code{https://buildbot.wild.gv.taler.net/}.
+
+In order to avoid downtimes, CI uses a "blue/green" deployment technique.
+In detail, there are two users building code on the system, the "green" and
+the "blue" user; and at any given time, one is running Taler services and
+the other one is either building the code or waiting for that.
+
+There is also the possibility to trigger builds manually, but this is only
+reserved to "admin" users.
+
+@node Code coverage
+@chapter Code coverage
+Code coverage is done with the Gcov / Lcov (http://ltp.sourceforge.net/coverage/lcov.php)
+combo, and it is run *nightly* (once a day) by a Buildbot worker.  The
+coverage results are then published at @code{https://lcov.wild.gv.taler.net/}.
+
+@node Demo and Test
+@chapter Demo and Test
+Taler code is normally kept under two Git branches: @code{master} and @code{stable}.
+The first branch keeps the latest code, therefore more experimental and
+unstable.  The latter branch is usually pointing at the latest release and
+is expected to be more stable.
+
+Finally, there exist two live systems that run Taler from those two
+branches, and where any user can try the Taler experience.  The 'master'
+branch is run at @code{https://test.wild.gv.taler.net/} and 'stable' at
+@code{https://demo.wild.gv.taler.net/}.
 @bye