Fri, Oct 11
Thu, Oct 10
Tue, Oct 1
Indeed, I forgot the requests module does not set any default timeout value and will hang until the connection is closed.
Mon, Sep 30
Fri, Sep 27
We do need the submenus, this will be clear in a couple of weeks
Thu, Sep 26
Almost all points have been treated and deployed to production (see https://www.softwareheritage.org/).
Closing this as the revamped support page is now deployed to production for all languages: https://www.softwareheritage.org/support/
We only have counters history data for contents, revisions and origins (see history_counters.json).
Wed, Sep 25
I have deployed a new version of https://archive.softwareheritage.org including the archive evolution graphs on the homepage.
Very nice, that's a GO for me :-)
Yes we can. I have updated the page accordingly.
Cool, can we try to have the 4 columns of "you can help" on the same row, like the ones below?
First draft of the revamped support page can be found here: https://www-dev.softwareheritage.org/support/
Mon, Sep 23
To check the archive menu (and all of them) in other languages.
Thu, Sep 19
Wed, Sep 18
I fully support this last proposal, that makes total sense.
I would like to see an API entrypoint that provides the information that will go in archive.s.o/coverage.
Tue, Sep 17
Sep 9 2019
sorry for the ultra-late reply, this message has been on the stack for a
Sep 5 2019
Sep 3 2019
Aug 28 2019
Aug 27 2019
Aug 26 2019
Aug 21 2019
This is now particularly imporant, following the sunset announcement from Bitbucket, here: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket