diff options
Diffstat (limited to 'taler-developer-manual.rst')
| -rw-r--r-- | taler-developer-manual.rst | 40 |
1 files changed, 21 insertions, 19 deletions
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst index c348a1d5..49ffa250 100644 --- a/taler-developer-manual.rst +++ b/taler-developer-manual.rst @@ -174,11 +174,12 @@ development. Communication ------------- -We use the #taler channel on the Freenode IRC network and the taler@gnu.org -public mailinglist for discussions. Not all developers are active on IRC, but -all developers should probably subscribe to the low-volume Taler mailinglist. -There are separate low-volume mailinglists for gnunet-developers (@gnu.org) -and for libmicrohttpd (@gnu.org). +For public discussions we use the taler@gnu.org mailinglist. All developers +should subscribe to the low-volume Taler mailinglist. There are separate +low-volume mailinglists for gnunet-developers (@gnu.org) and for libmicrohttpd +(@gnu.org). For internal discussions we use https://mattermost.taler.net/ +(invitation only, but also achieved). + What to put in bootstrap ------------------------ @@ -254,22 +255,19 @@ Language-Specific Guidelines Taler Deployment on gv.taler.net ================================ -This section describes the GNU Taler deployment on ``gv.taler.net``. -``gv`` is our server at BFH. It hosts the Git repositories, Web sites, -CI and other services. Developers can receive an SSH account and -e-mail alias for the system. As with Git, ask your primary team -contact for shell access if you think you need it. +This section describes the GNU Taler deployment on ``gv.taler.net``. ``gv`` +is our server at BFH. It hosts the Git repositories, Web sites, CI and other +services. Developers can receive an SSH account and e-mail alias for the +system, you should contact Javier, Christian or Florian. As with Git, ask +your primary team contact for shell access if you think you need it. -Our old server, ``tripwire``, is currently offline and will likely -go back online to host ``production`` systems for operating real -Taler payments at BFH in the future. DNS --- -DNS records for taler.net are controlled by the GNU Taler -maintainers, specifically Christian and Florian. If you -need a sub-domain to be added, please contact one of them. +DNS records for taler.net are controlled by the GNU Taler maintainers, +specifically Christian and Florian, and our system administrator, Javier. If +you need a sub-domain to be added, please contact one of them. User Acccounts @@ -510,7 +508,7 @@ Database schema versioning -------------------------- The PostgreSQL databases of the exchange and the auditor are versioned. -See the 0000.sql file in the respective directory for documentation. +See the ``versioning.sql`` file in the respective directory for documentation. Every set of changes to the database schema must be stored in a new versioned SQL script. The scripts must have contiguous numbers. After @@ -518,7 +516,7 @@ any release (or version being deployed to a production or staging environment), existing scripts MUST be immutable. Developers and operators MUST NOT make changes to database schema -outside of this versioning. +outside of this versioning. All tables of a GNU Taler component should live in their own schema. @@ -663,6 +661,8 @@ debian/changelog, and then run: in the respective source directory (GNUnet, exchange, merchant) to create the ``.deb`` files. Note that they will be created in the parent directory. This can be done on gv.taler.net, or on another (secure) machine. +Actual release builds should be done via the Docker images +that can be found in ``deployment.git`` under packaging. On ``gv``, we use the ``aptbuilder`` user to manage the reprepro repository. @@ -1472,7 +1472,9 @@ use when talking to end users or even system administrators. key used by the exchange to sign online messages, other than coins order - FIXME: to be written! + offer made by the merchant to a wallet; pre-cursor to + a contract where the wallet is not yet fixed. Turns + into a :term:`contract` when a wallet claims the order. owner a coin is owned by the entity that knows the private key of the coin |