View Issue Details

IDProjectCategoryView StatusLast Update
0008512Talerdeployment and operationspublic2024-03-07 20:51
ReporterChristian Grothoff Assigned Toavalos  
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.9.4Fixed in Version0.9.4 
Summary0008512: enable easy Terms-of-Service deployment in regional currency installer
DescriptionRight now, the "Netzbon" installer deploys an exchange without terms of service or privacy policy configured. We should modify the script to ask for the ToS to deploy and configure the ToS/PP automatically. The exchange contrib/ directory includes various ".rst" files that would make suitable starting points, which are installed under /usr/share/taler/terms/*.rst by the installer. So we could just list those files and ask the admin to select which of them they want to use (or if they want to skip the step). Afterwards, we should use the taler-terms-generator to generate the ToS/PP in the various formats served by the exchange.
TagsNo tags attached.



2024-02-28 20:50

developer   ~0021565

This is implemented in dev/ivan-avalos/exchangetos.

However, there was some feedback from Antoine regarding the listing of ToS/PP files. In my commit, the user is asked for the file path of both the ToS and the privacy policy, and in both questions it is shown a list of ALL files under /usr/share/taler/terms with *.rst extension, like this one:

9. Do you wish to configure terms of service (ToS) for the exchange? (Y/n): y
9.1. Enter the filename of the ToS. Some available options are:
- /usr/share/terms/taler/exchange-pp-v0.rst
- /usr/share/terms/taler/exchange-tos-bfh-v0.rst
- /usr/share/terms/taler/exchange-tos-v0.rst

10. Do you wish to configure a privacy policy for the exchange? (Y/n): y
10.1. Enter the filename of the privacy policy. Some available options are:
- /usr/share/terms/taler/exchange-pp-v0.rst
- /usr/share/terms/taler/exchange-tos-bfh-v0.rst
- /usr/share/terms/taler/exchange-tos-v0.rst

However, Antoine argues that this is counterintuitive because it always shows all files regardless of whether it is the ToS or the privacy policy what is being asked for. We suggested a bunch of tricky solutions, and Florian suggested adding those files to the documentation instead of listing them in the deployment script. How do you think we should proceed? I personally don't think we should over-complicate something as simple as this.

Christian Grothoff

2024-02-28 23:11

manager   ~0021568

Why don't you |grep -- -pp- when going for the privacy policy, and for -tos- when going for the terms of service? We have pretty obvious naming conventions here...

Antoine A

2024-02-29 17:46

developer   ~0021580

Fixed in 6f0b35ef80d92daa15f6feb40cadbd6769c711fa

Issue History

Date Modified Username Field Change
2024-02-25 00:33 Christian Grothoff New Issue
2024-02-25 00:33 Christian Grothoff Status new => assigned
2024-02-25 00:33 Christian Grothoff Assigned To => avalos
2024-02-28 20:50 avalos Assigned To avalos => Christian Grothoff
2024-02-28 20:50 avalos Status assigned => feedback
2024-02-28 20:50 avalos Note Added: 0021565
2024-02-28 23:11 Christian Grothoff Note Added: 0021568
2024-02-28 23:11 Christian Grothoff Assigned To Christian Grothoff => avalos
2024-02-28 23:12 Christian Grothoff Status feedback => assigned
2024-02-29 17:46 Antoine A Status assigned => resolved
2024-02-29 17:46 Antoine A Resolution open => fixed
2024-02-29 17:46 Antoine A Note Added: 0021580
2024-03-07 20:50 Christian Grothoff Fixed in Version => 0.9.4
2024-03-07 20:51 Christian Grothoff Status resolved => closed