View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005697 | Taler | documentation | public | 2019-04-19 15:40 | 2019-12-20 18:11 |
| Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0005697: Polishnig onboard.texi. | ||||
| Description | The file deployment/doc/onboard.texi has been partially obsoleted by readme.md from gv-maintenance.git. It should be seen whether this file should be simply polished, or entirely disposed. | ||||
| Tags | No tags attached. | ||||
| first cleaning: 42a3311..ddcfb1b | |
| I generally believe the onboarding.texi should be kept. It should have a much broader scope than just gv-maintenance.git, which is about system administration. Onboarding is about "everything" a new dev should know (from Git write access to Bugtracking to CI to coding conventions, etc. etc.). Naturally details about system administration might be better kept in the gv-maintenance.git readme. | |
| Okay for all, but 'CI' needs some clarification: this aspect has the sysadmin side (accounting for which users are running which workers, or where in the system some worker outputs some files, etc.) and the user side (like letting the user know where the BB Website is, or what happens after they push their changes, etc.). We should agree that the first part goes in gv-maintenance.git, and the second goes in onboarding.texi at deployment.git. | |
| In 875fdb95058e0..c42dbea3cda4a2ab, I reviewed and polished the per-user setup environments. Actually, we should also agree about keeping this feature around or not. | |
| Commit 99a3eee..5536720 finishes polishing the current content, and so this can be closed. New sections, like about Git / Bugtracking / Buidlbot for *users* needs to be added. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-04-19 15:40 | Marcello Stanisci | New Issue | |
| 2019-04-19 15:49 | Marcello Stanisci | Note Added: 0014304 | |
| 2019-04-20 10:08 | Christian Grothoff | Note Added: 0014310 | |
| 2019-04-22 13:58 | Marcello Stanisci | Note Added: 0014327 | |
| 2019-04-22 16:24 | Marcello Stanisci | Note Added: 0014329 | |
| 2019-04-22 16:30 | Marcello Stanisci | Note Added: 0014330 | |
| 2019-04-22 16:30 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2019-04-22 16:30 | Marcello Stanisci | Status | new => informing |
| 2019-04-22 16:30 | Marcello Stanisci | Resolution | open => fixed |
| 2019-09-16 07:24 | Christian Grothoff | Product Version | => git (master) |
| 2019-09-16 07:24 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2019-09-16 07:24 | Christian Grothoff | Target Version | => 0.6 |
| 2019-12-20 18:11 | Christian Grothoff | Status | informing => closed |