- User Since
- Sep 7 2015, 3:43 PM (170 w, 5 h)
Thu, Dec 6
what kind of inventory we want to do with this? hardware? software? both?
Tue, Dec 4
Mon, Dec 3
Sat, Dec 1
Fri, Nov 30
This comes from a discussion between myself and @vlorentz . To summarize my position: I would like to be able to tell downstream users "the keys we use in our metadata are (a subset of) the codemeta ones". AFAICT that means that they should be able to look them up here: https://codemeta.github.io/terms/ . As such, we should not use keys like schema:author, but simply author; similarly we should not use codemeta:issueTracker but simply issueTracker.
Wed, Nov 28
Tue, Nov 27
I've attached here T917, which was just a specific instance of this.
Fri, Nov 23
Regarding the glossary, we also had https://wiki.softwareheritage.org/wiki/Glossary ; once this is pushed the wiki glossary should be deprecated/deleted in favor of the docs.s.o one. In the meanwhile there might be entries there that are missing here (I haven't checked, but wanted to mention potentially useful previous work :-))
Mon, Nov 19
Would removing your 3rd requirement (per-package indexes) simplify things? I don't see that as a goal at all, just what happens by default with the minimalistic sphinx setup we used back in the days. I'd be much happier if we could have a single index / navigation bar, where the doc of all modules appear.
Fri, Nov 16
Thu, Nov 15
Wed, Nov 14
Thanks for filing this @moranegg !
The simplest solution would be to check if the computed timezone offset lies in the adequate bounds [UTC−14:00, UTC+14:00] and set it to 0 if not.
@ftigeot thanks for checking!
Please file tasks for changing the failing batteries (priority high) and automate the monitoring of failing batteries so that in the future we will be automatically notified of future similar failures (priority normal).
Tue, Nov 13
Mon, Nov 12
@anlambert: let's do this. Green light, go ahead!
Nov 9 2018
Nov 6 2018
Nov 5 2018
thanks! can you ping me when this fix (T1304) is deployed?
thanks! can you ping me when this fix (T1303) is deployed?
Oh, silly me, I commented without checking that first.
Fine by me then :) Thanks!
I've tried this before too, but we can't do that yet, because the version of msgpack we use in Debian stable doesn't yet have raw=False.
Nov 2 2018
Oct 31 2018
(I also note that the search results page treat both cases similarly: showing an X for both kind of origins. Good!)
To elaborate, the user-visible result should be the same of origins that haven't been visited yet, e.g.: