| 8 Aug 2022 |
 Robert Hensing (roberth) | some other single-word combinations I came up with for 1/2: interface/implementation, reading/writing, query/answer, possibility/determination | 17:29:03 |
 nbp | Yeah, the statements are biased toward the solution I had, but this is the general idea of summarizing in a few statements what each is. | 17:29:13 |
| Robert Hensing (roberth) | decision/choice | 17:30:41 |
| Robert Hensing (roberth) | parameter/argument | 17:31:52 |
| Robert Hensing (roberth) | well, you've got me thinking very laterally, brainstorming mode | 17:34:21 |
| nbp | These are interesting suggestions! I bet others have ideas too. Coming back tomorrow, I expect this channel to be flooded with others' suggestions ;) | 17:35:10 |
| Robert Hensing (roberth) | so my end goal is mostly to replace the terms "declaration" and "definition" by something that's a little less ambiguous in normal English. A second goal is to find a term for a "whole" configuration, or the sum of all modules, such as what's returned by evalModules and nixosSystem | 17:49:28 |
| nbp | The FIX POINT result ! | 17:50:11 |
| Robert Hensing (roberth) | that's how it's implemented | 17:51:07 |
| nbp | the implemnted configuration. Using a passive, as-if it was already there. | 17:52:48 |
| nbp | * the implemented configuration. Using a passive, as-if it was already there. | 17:52:54 |
| nbp | Causality and laziness are not playing well in Human languages. | 17:53:29 |
| Robert Hensing (roberth) | oh that's necessarily what I meant when I said implemented, but I guess it kind of works | 17:53:31 |
| Robert Hensing (roberth) | a problem with the term "whole configuration" is that it suggests that it isn't used as a submodule anywhere, which it may well be | 18:07:09 |
| Robert Hensing (roberth) | fix point doesn't tell me that there aren't any metavariables in the function that's looped back on itself | 18:07:53 |
| Robert Hensing (roberth) | I wish instantiation wasn't taken. How about instance? | 18:08:57 |
| 10 Aug 2022 |
 infinisil | @room The next meeting will take place in a couple minutes at https://meet.jit.si/nixpkgs-architecture, meeting notes here, and live stream here | 14:54:20 |
 mkaito | I'm going to skip today. Been dealing with a stomach bug since yesterday. Much vomiting. I'll read the notes. 🥺 | 14:55:05 |
| infinisil | I wish you a good recovery! | 14:55:38 |
 Alyssa Ross | I'm on a train :( | 14:56:01 |
 j-k | I think we have a member that joins from the car since I swear I've heard the click of an indicator & the grumble of a moving vehicle 😅
if you've got a seat & wifi you could always join even just to listen & type in the chat but completely up to you | 14:58:20 |
| Alyssa Ross | well the main thing is I doubt the internet is up to that | 14:59:00 |
| Alyssa Ross | I guess I can try! | 14:59:01 |
| infinisil | In reply to @profpatsch:augsburg.one
I’d start by asking what the main use-cases for nixpkgs are. And then building some Personas, UX design style profpatsch: Will you be there? | 14:59:12 |
| nbp | infinisil: Could this be the back channel for meeting communication? Such that others who are not following live can catch up? | 15:35:52 |
| * nbp (6 minutes away from live) | 15:36:20 |
| Alyssa Ross | wfm as long as infinisil is reading it (I'm most of the chat this meeting) | 15:36:49 |
| nbp | That works too | 15:37:08 |
| j-k | <jitsi call chat continues here> | 15:40:28 |
 nbathum (he or they) | lots of meta talk for now | 15:41:01 |
