Mon, Oct 19
More details for this task is here T2537
Agreed. In terms of where this doc go, I think it should just be a new section under https://archive.softwareheritage.org/api/ , where we already have other stuff very similar in nature. And we will be able to link to the relevant section of it via # anchors, as we already do for, e.g., rate limit.
Sun, Oct 18
Fri, Oct 16
Wed, Oct 14
I improved a bit over your work.
Mon, Oct 12
An interesting diagram that can fit the mirror documentation: https://www.programmevitam.fr/pages/VaS/
Fri, Oct 9
Thu, Oct 8
Tue, Oct 6
(FYI, I'm a little busy with other things, so if someone has time on their hand, they can take over this task)
Wed, Sep 30
Sep 24 2020
For whoever who want to work on this (and on doc restructuring in general), I recommend to watch this talk: https://www.youtube.com/watch?v=t4vKPhjcMZg , which provides a good taxonomy of the kind of docs that exist. Our GSoD 2019 application page also contains a lot of useful related work.
I'd like to close this task, but unfortunately:
I guess we can say that, let's close this.
Sep 23 2020
Sep 22 2020
Examples for a community driven documentation: