From c4bd8200b517fb9d41750397ef5269c7124481a2 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Mon, 13 Mar 2017 17:44:06 +0100 Subject: revising gov page based on feedback from Sva and Marcello --- developers.html.j2 | 161 ++++++++++++++++++++++++++++++++--------------------- 1 file changed, 99 insertions(+), 62 deletions(-) (limited to 'developers.html.j2') diff --git a/developers.html.j2 b/developers.html.j2 index e3725df4..d235c53a 100644 --- a/developers.html.j2 +++ b/developers.html.j2 @@ -13,20 +13,18 @@

{% trans %} - Taler is free software implementing an open - protocol. Anybody is welcome to inspect our code - and integrate our reference implementation into - their applications. Different components of Taler - are being made available under different - licenses. The Affero GPLv3+ is used for the + GNU Taler is free software implementing an open + protocol. Anybody is welcome to integrate our reference + implementation into their applications. Different + components of Taler are being made available under + different licenses. The Affero GPLv3+ is used for the exchange, the LGPLv3+ is used for reference code - demonstrating integration with merchant platforms, - and licenses like Apache/Mozilla/GPLv3+ are used - for wallets and related customer-facing software. - We are open for constructive suggestions for - maximizing the adoption of this libre payment - platform. - {% endtrans %} + demonstrating integration with merchant platforms, and + licenses like Apache/Mozilla/GPLv3+ are used for + wallets and related customer-facing software. We are + open for constructive suggestions for maximizing the + adoption of this payment platform. + {% endtrans %}

@@ -46,7 +44,7 @@ structure data, making it easy to integrate Taler with existing Web applications. Taler's protocol is documented in - detail here. + detail at api.taler.net. {% endtrans %}

@@ -62,13 +60,14 @@

{% trans %} Taler is currently primarily developed by a - research team at Inria and GNUnet e.V. However, + research team at Inria and + GNUnet. However, contributions from anyone are welcome. Our Git repositories can be cloned using the Git and HTTP access methods against git.taler.net with the name of the respective repository. A list of - public repositories can be found in - our GitWeb. + repositories can be found in + our GitWeb. {% endtrans %}

@@ -77,54 +76,64 @@

{% trans %} - In addition to this website, - the documented - code and + In addition to this website, the documented code and the API - documentation, we are in the process of - preparing a comprehensive design document which - will be published here soon. + documentation. Technical papers can be found in + our bibliography. {% endtrans %}

{{ _("Discussion") }}

-

{{ _("We have a mailing list for developer discussions. - You can subscribe to it or read the list archive at - http://lists.gnu.org/mailman/listinfo/taler.") }}

+

+ {% trans %} + We have a mailing list for developer discussions. + You can subscribe to or read the list archive at + http://lists.gnu.org/mailman/listinfo/taler. + {% endtrans %} +

{{ _("Regression Testing") }}

-

{{ _("We have - Buildbot - automation tests to detect regressions and check - for portability at - buildbot.taler.net. - ") }}

+

+ {% trans %} + We have Buildbot + automation tests to detect regressions and check for + portability at buildbot.taler.net. + {% endtrans %} +

{{ _("Code Coverage Analysis") }}

-

{{ _("We use - LCOV +

+ {% trans %} + We use + LCOV to analyze the code coverage of our tests, the results are available - at lcov.taler.net. - ") }}

+ at lcov.taler.net. + {% endtrans %} +

{{ _("Performance Analysis") }}

-

{{ _("We - use Gauger +

+ {% trans %} + We + use Gauger for performance regression analysis of the exchange backend - at gauger.taler.net. - ") }}

+ at gauger.taler.net. + {% endtrans %} +

@@ -135,24 +144,31 @@

{{ _("Taler system overview") }}

-

{{ _("The Taler system consists of protocols executed among - a number of actors with the help - of Free Software - as illustrated in the illustration on the right. - Typical transactions involve the following steps: ") - }}

+

+ {% trans %} + The Taler system consists of protocols executed among + a number of actors as illustrated in the illustration on the right. + Typical transactions involve the following steps: + {% endtrans %} +

system overview
    -
  1. {{ _("A customer instructs his bank to +
  2. + {% trans %} + A customer instructs his bank to transfer funds from his account to the Taler exchange (top left). In the subject of the transaction, he includes an authentication token from his electronic wallet. In Taler terminology, the customer creates a - reserve at the exchange. ") }}
  3. + reserve at the exchange. + {% endtrans %} + -
  4. {{ _("Once the exchange has received the wire +
  5. + {% trans %} + Once the exchange has received the wire transfer, it allows the customer's electronic wallet to withdraw electronic coins. The electronic coins are digital @@ -164,10 +180,13 @@ purchased what at which merchant. The use of Taler does not change the currency or the total value of the funds (except for fees which the - exchange may charge for the service). ") - }}
  6. + exchange may charge for the service). + {% endtrans %} + -
  7. {{ _("Once the customer has the digital coins in his +
  8. + {% trans %} + Once the customer has the digital coins in his wallet, the wallet can be used to spend the coins with merchant portals that support the Taler payment system and accept the @@ -183,10 +202,14 @@ merchant to learn the identity of the customer. Naturally, the customer can spend any fraction of his digital coins (the system takes - care of customers getting change). ") }}
  9. + care of customers getting change). + {% endtrans %} + -
  10. {{ _("Merchants receiving digital - coins deposit the respective receipts +
  11. + {% trans %} + Merchants receiving digital + coins deposit the respective claims that resulted from the contract signing with the customer at the exchange to redeem the coins. The deposit step does not reveal the @@ -202,9 +225,13 @@ the customer. Thus, the exchange's database allows the state to enforce that merchants pay applicable taxes (and do not engage in illegal - contracts). ") }}
  12. + contracts). + {% endtrans %} + -
  13. {{ _("Finally, the exchange transfers funds +
  14. + {% trans %} + Finally, the exchange transfers funds corresponding to the digital coins redeemed by the merchants to the merchant's bank account. The exchange may combine multiple @@ -212,9 +239,13 @@ transfer. The merchant can query the exchange about the relationship between the bank transfers and the individual claims that were - deposited. ") }}
  15. + deposited. + {% endtrans %} + -
  16. {{ _("Most importantly, the exchange keeps +
  17. + {% trans %} + Most importantly, the exchange keeps cryptographic proofs that allow it to demonstrate that it is operating correctly to third parties. The system requires an @@ -223,9 +254,13 @@ to frequently verify the exchange's databases and check that its bank balance matches the total value of the remaining coins in - circulation. ") }}
  18. + circulation. + {% endtrans %} + -
  19. {{ _("Without the auditor, the exchange operators +
  20. + {% trans %} + Without the auditor, the exchange operators could embezzle funds they are holding in reserve. Customers and merchants cannot cheat each other or the exchange. If any party's @@ -233,7 +268,9 @@ is limited to the respective party and proportional to the funds they have in circulation during the period of the - compromise. ") }}
  21. + compromise. + {% endtrans %} +

-- cgit v1.2.3