View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006649 | Taler | documentation | public | 2020-11-17 17:29 | 2021-01-07 22:29 |
| Reporter | MS | Assigned To | MS | ||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | 0.8.1 | ||||
| Summary | 0006649: taler-util needs documentation | ||||
| Description | The various APIs exported by taler-util (Python module) need to be documented. It should also be agreed on *where* to write this documentation. | ||||
| Tags | No tags attached. | ||||
|
|
ttn: this may also be a task suitable for you, if you can read Python ;-) |
|
|
I'm open to learning about taler-util and documenting it along the way. I agree that *where* to put such docs is a good question. Hmmm... |
|
|
We're currently lacking a "real" chapter on the Python bank. https://docs.taler.net/taler-bank-manual.html is hardly a skeleton for that. It does not explain taler-bank-manage and its subcommands, or how to install, or what it does. If we have a good chapter on the Python bank (bank.git), then I think in a section for _developers_ of the bank can contain a subsection on taler-util (as it is primarily used by the bank.git). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-11-17 17:29 | MS | New Issue | |
| 2020-11-17 17:29 | MS | Status | new => assigned |
| 2020-11-17 17:29 | MS | Assigned To | => Stefan |
| 2020-11-17 17:30 | MS | Target Version | => 0.8.1 |
| 2020-11-17 17:30 | MS | Description Updated | View Revisions |
| 2020-11-17 17:37 | MS | Assigned To | Stefan => MS |
| 2021-01-01 16:40 | Christian Grothoff | Note Added: 0017291 | |
| 2021-01-07 04:10 | ttn | Note Added: 0017317 | |
| 2021-01-07 09:42 | Christian Grothoff | Note Added: 0017319 | |
| 2021-01-07 22:29 | Christian Grothoff | Severity | minor => text |
