diff options
| author | Christian Grothoff <christian@grothoff.org> | 2019-12-10 17:01:37 +0100 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2019-12-10 17:01:37 +0100 |
| commit | 518c496278982b67d6f220fd5b9c15036c410bfe (patch) | |
| tree | 898475b1fbd4f37651a1aca92d5b865a0b814949 /developers-manual.rst | |
| parent | 69a282f6997d2dc230a28543b707e3ceecfa6a05 (diff) | |
| download | docs-518c496278982b67d6f220fd5b9c15036c410bfe.tar.gz docs-518c496278982b67d6f220fd5b9c15036c410bfe.tar.bz2 docs-518c496278982b67d6f220fd5b9c15036c410bfe.zip | |
clarify instructions
Diffstat (limited to 'developers-manual.rst')
| -rw-r--r-- | developers-manual.rst | 22 |
1 files changed, 16 insertions, 6 deletions
diff --git a/developers-manual.rst b/developers-manual.rst index 536f5c7b..c188f5aa 100644 --- a/developers-manual.rst +++ b/developers-manual.rst @@ -43,8 +43,11 @@ A complete list of all the existing repositories is currently found at Committing code --------------- -To obtain Git access, you need to send us your SSH public key. You can -find instructions on how to do so in the `Git book <https://git-scm.com/book/en/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key>`_. +To obtain Git access, you need to send us your SSH public key. Most core +team members have administrative Git access, so simply contact whoever +is your primary point of contact so far. You can +find instructions on how to generate an SSH key +in the `Git book <https://git-scm.com/book/en/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key>`_. If you have been granted write access, you first of all must change the URL of the respective repository to: @@ -90,11 +93,11 @@ merge commits and instead always rebase your changes before pushing to the master branch. If you commit and later find out that new commits were pushed, the following command will pull the new commits and rebase yours on top of them. - + :: # -S instructs Git to (re)sign your commits - $ git pull --rebase -S + $ git pull --rebase -S @@ -466,7 +469,7 @@ 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 -``https://buildbot.wild.gv.taler.net/``. +``https://buildbot.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, @@ -491,7 +494,7 @@ then published at ``https://lcov.taler.net/``. Coding Conventions ================== -GNU Taler is developed primarily in C, Python and TypeScript. +GNU Taler is developed primarily in C, Kotlin, Python and TypeScript. Components written in C ----------------------- @@ -589,6 +592,13 @@ When shell scripts are used, they ``MUST`` begin with the following ``set`` comm # commands with non-zero exit status. set -eu +Kotlin +------ + +We so far have no specific guidelines, please follow best practices +for the language. + + Python ------ |