David Arnold

@yvaucher :notes: :wink: I'll have to wrap my head around, but I feel it's probably a good idea to do a second attempt. :)

These things here: https://www.nushell.sh/book/overlays.html#basics Meaning semantics like the following: ```console > overlay list ──┬────── 0 │ stdenv 1 │ python 2 │ conda ──┴────── > build unpack ... patch ......

Also mentioned on telegram: While not directly related, https://github.com/frappe/frappe/pull/23931 was designed and intended to **not** make Email as special as it currently is in the entire framework and thus marginally...

Dumping a related idea that came up during discussing kanban for CRM in telegram:  It is designed to unambiguously hint at which part of the funnel needs rebalancing, and...

I'll dump reference material from the telegram chat, here: - https://sattelite.me -- Smart call centric, mobile first CRM-ish - FluffyChat's implementation of native calling on mobile: https://github.com/krille-chan/fluffychat/blob/main/lib%2Futils%2Fvoip%2Fcallkeep_manager.dart using https://pub.dev/packages/callkeep -...

The Nix Community is [currently working](https://github.com/opencontainers/image-spec/compare/main...nix-community:image-spec:shards-for-nix) with the OCI specification body to prototype a `non-conflicting-on-prefix: "/prefix"` layer type that can be a nix store path. Constructing an overlayfs is unduely...

https://github.com/actions/toolkit/pull/1253 (If it doensn't get organic attention)

Would it be too much of a plug to paraphrase the 4 layers of packaging (by someone who _can_ explain)? And even recommend in the practices section the use of...

Sounds pretty good! I agree with the cautionary voice of not overclocking on the recommendation (which might backfire, anyways). But I also think we shouldn't overclock on scepticism of what...

Yep, that sounds pretty good! Maybe not too much detail (if we can avoid it) and stick to the high level aspects. I think such a policy is a good...