View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006696 | Taler | documentation | public | 2021-01-13 23:50 | 2021-08-11 04:55 |
| Reporter | Florian Dold | Assigned To | ttn | ||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0006696: discuss better structure for LibEuFin docs | ||||
| Description | The LibEuFin docs are currently pretty chaotic. We should come up with a better structure. I guess there are three different target audiences for the docs: * Operators of LibEuFin (who want to use it with Taler) * Developers who want to use the LibEuFin API * Core Developers of LibEuFin ("internal stuff, documented in public") | ||||
| Tags | No tags attached. | ||||
|
|
Well, the HOWTO (tutorial) is clearly targeted at the Operator audience. I don't know what the distinction is between the other two audience groups are, however. |
|
|
Applicable not just to Libeufin, but all Taler documentation: https://documentation.divio.com/ |
|
|
Please see recent commits in docs.git/libeufin/*.rst -- the "target audience" can be "operator", "developer", "core developer". (Feel free to add/correct my guesses.) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-01-13 23:50 | Florian Dold | New Issue | |
| 2021-01-13 23:50 | Florian Dold | Status | new => assigned |
| 2021-01-13 23:50 | Florian Dold | Assigned To | => ttn |
| 2021-01-29 19:42 | ttn | Note Added: 0017449 | |
| 2021-01-30 23:55 | Christian Grothoff | Severity | minor => text |
| 2021-02-02 21:34 | ttn | Note Added: 0017490 | |
| 2021-06-02 09:58 | Christian Grothoff | Assigned To | ttn => Christian Grothoff |
| 2021-07-13 06:48 | Christian Grothoff | Assigned To | Christian Grothoff => ttn |
| 2021-08-11 04:55 | ttn | Note Added: 0018093 |
