*** willbarnard has joined #trustable | 05:58 | |
*** weyfonk has joined #trustable | 08:13 | |
*** traveltissues has joined #trustable | 08:47 | |
paulsherwood | flatmush: is there a cache server involved in your ci? if so, would a re-run be faster? | 09:02 |
---|---|---|
paulsherwood | also maybe we can adjust the timeout | 09:03 |
paulsherwood | or create a dedicated runner for this | 09:03 |
flatmush | should be the same as definitions, so probably | 09:04 |
flatmush | but still seems wrong for the CI to timeout in less than the time a full rebuild takes | 09:05 |
flatmush | not very automated | 09:05 |
flatmush | Ah, we're not using the cache, I guess I could nag ironfoot for the key | 09:22 |
*** willbarnard has quit IRC | 09:29 | |
*** willbarnard has joined #trustable | 09:30 | |
ironfoot | yes you could, but I believe it wasn't even working in baserock/definintions.git so I'm not sure it will speed things up | 09:32 |
ironfoot | let's give it a try though | 09:33 |
flatmush | STANDUP! Order: flatmush, noisecell, willbarnard | 10:09 |
flatmush | ## Ben Brewer (flatmush) | 10:09 |
flatmush | * Done | 10:09 |
flatmush | - Make minimal distro work public | 10:09 |
flatmush | - Try to get CI working | 10:09 |
flatmush | - Discussion about bootstrapping | 10:09 |
flatmush | - Work on minimal distro | 10:09 |
flatmush | * Doing | 10:09 |
flatmush | - Enable CI caching | 10:09 |
flatmush | - Discussion about bootstrapping compilers | 10:09 |
flatmush | - Attempt to replace glibc with musl | 10:09 |
flatmush | ## Francisco Redondo Marchena (noisecell) | 10:09 |
noisecell | * Done | 10:09 |
noisecell | - Update package dependencies to use build and runtime dependencies wisely | 10:09 |
noisecell | * Doing | 10:09 |
noisecell | - Trim the system and update packages to latest versions. | 10:09 |
noisecell | - Update packages to latests stable versions | 10:09 |
noisecell | ## Will Barnard (willbarnard) | 10:09 |
willbarnard | * Doing | 10:10 |
willbarnard | - Analyzing certification requirements for ISO 26262/IEC 61508 | 10:10 |
willbarnard | - Planning for functional safety workshop | 10:10 |
flatmush | - Improving level of detail on standup notes. | 10:10 |
flatmush | ## Discussion | 10:10 |
ironfoot | o/ | 10:10 |
noisecell | _o_ | 10:11 |
flatmush | ironfoot? | 10:11 |
ironfoot | regarding musl, there was a previous attempt done in baserock | 10:11 |
ironfoot | and i think a finished one | 10:11 |
flatmush | yes, by rdale | 10:11 |
ironfoot | _o_ | 10:11 |
flatmush | I'm looking at that, it doesn't directly work | 10:11 |
flatmush | probably did at the time | 10:11 |
flatmush | STANDUP ENDS! | 10:11 |
*** willbarnard has quit IRC | 11:27 | |
*** willbarnard has joined #trustable | 11:27 | |
paulsherwood | https://twitter.com/devcurmudgeon/status/1020270488398987264 | 11:37 |
ltu | I may send that to the C Safety and Security Study Group | 11:49 |
ltu | We had a debate back when it first started out over whether to make the (hopefully) resulting standard free or not | 11:50 |
ltu | David A Wheeler pointed out that the only way to make a standard relevant was to make it free. | 11:51 |
paulsherwood | ltu: it's about time i wrote to that group, in any case | 12:28 |
paulsherwood | but by all means send it :) | 12:29 |
*** noisecell has quit IRC | 14:22 | |
persia | ETSI has a requirement to charge for standards baked in to the structure of the organisation. One trick that is used by a number of ETSI working groups is to publish a) the source of the standard (for review), b) a set of requirements for implementation of the standard (different language to standard, but ideally same content), and c) an open source reference implementation. | 14:56 |
persia | Those groups don't end up seeing much revenue, but they do seem to be leading with adoption, despite the standard costing money. | 14:56 |
persia | (in that implementing organisations purchase one copy and nobody ever reads that copy: it's just for the audit trail) | 14:56 |
* paulsherwood likes the sound of that :) | 15:00 | |
persia | At least for (a), there are an increasing number of standards organisations that are increasing transparency and opportunity for public comment, often under an "open source" initiative. There were a few people from standards organsiations (or organisations providing services to standards organisations) at OSCON this year, although I don't want to speak in advance of anyone's announcement. | 15:11 |
persia | (b) and (c) require a lot more commitment by members of the relevant working group for the standard in question, rather than being something that can be required by policy. | 15:12 |
*** willbarnard has quit IRC | 15:39 | |
*** willbarnard has joined #trustable | 15:40 | |
*** willbarnard has quit IRC | 16:55 | |
*** toscalix has joined #trustable | 17:03 | |
*** toscalix has quit IRC | 17:08 | |
*** toscalix has joined #trustable | 17:13 | |
*** weyfonk has quit IRC | 17:32 | |
*** toscalix has quit IRC | 18:34 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!