[GNUnet-SVN] [taler-deployment] branch master updated: Onboarding.

[gnunet]

This is an automated email from the git hooks/post-receive script.

marcello pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new e468ab0  Onboarding.
e468ab0 is described below

commit e468ab04efe900ab906e0673e43f5eed988956b5
Author: Marcello Stanisci <address@hidden>
AuthorDate: Mon May 20 14:04:19 2019 +0200

    Onboarding.
    
    Invite the reader to read each component's installing instructions.
---
 doc/onboarding.texi | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index e933f3a..040eba5 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -50,7 +50,7 @@ Texts.  A copy of the license is included in the section 
entitled
 @end ifnottex
 
 @menu
-* Standalone deployment::               Deploy Taler in your homepage
+* Standalone deployment::               Deploy Taler in your homepage @ 
taler.net
 * Testing components::                  How to make and run tests
 * Releases::                            Releases patterns
 * Code::                                Where to find Taler code
@@ -66,6 +66,12 @@ Texts.  A copy of the license is included in the section 
entitled
 This installation assumes that all the steps are run with @code{$HOME}
 as @code{$CWD}.
 
+NOTE: this documents does not explain how to get all the dependencies
+installed, but just how to use the helper scripts hosted in this repository.
+Any component comes with a "doc" directory, or a README file where building
+instructions are reported.  As a last resort, those instructions are also
+available at https://docs.taler.net.
+
 The first step is to fetch the @cite{deployment} repository, which hosts all
 the needed scripts.
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden