01:57 <voltagex[m]> It arrived! Now to become smarter.

02:01 <whitequark[cis]> congrats!

04:49 <esden[m]> voltagex (@_discord_123312205738278912:catircservices.org) congrats! I hope it serves you well. 🙂

14:07 <tem01[m]> The fun part is I've finished all the projects I was originally planning on using to learn this with. Which definitely, 100%, counts as an excuse to start new projects instead of finishing everything else.

17:14 <esden[m]> tem01 (@_discord_190648969318236160:catircservices.org) finished projects? What is that!? 😉

17:36 <esden[m]> A bunch of Glasgows ready to be packed for the next batch. 🙂

17:36 <galibert[m]> yay, another couple hundred?

17:37 <esden[m]> I want to ship at least 200 in the batch. But maybe we manage to do more. We will see. I do want to ship the boxes before the end of this week.

17:37 <galibert[m]> Impressive

17:38 <esden[m]> Thanks. Just keeping on cranking 😄

17:38 <galibert[m]> :-)

22:29 <adamgreig[m]> well mouser are very sorry that they posted it to the old address, but luckily I was able to pick it up from a slightly confused stranger's house 🚀

22:29 <adamgreig[m]> hopefully they managed to get the address change right for most people!

22:36 <esden[cis]> adamgreig: Congrats that you managed to get it though!

22:36 <esden[cis]> I am sorry it ended up in an ordeal. :/

22:36 <esden[cis]> So far you are the only one that had an issue like this... 🤞

22:37 <adamgreig[m]> "our system shows the order address change was successfully processed two years ago, so we don't yet see how this error could have occurred" 👻

22:38 <adamgreig[m]> anyway excited to get my hands on it at last :D

22:39 <omnitechnomancer> Clearly they can't see someone put the billing address on the shipping label

22:40 <esden[cis]> adamgreig: Ghost in the machine... clearly!

22:40 <gsuberland> whitequark[cis] - ohai :3 I'm thinking of putting together a documentation page that describes the Glasgow revC3 hardware in terms of electrical parameters and operation. would you be interested in this being part of the main docs, or would you prefer it go somewhere else (e.g. as a 3rd party reference manual)?

22:41 <gsuberland> well, I say "thinking of" but what I really mean is I started writing it already haha

22:43 <sys64738_2574[m]> yeah mine was also still addressed to my deadname 💀

22:44 <gsuberland> stuff like power rail derivation, protection, monitoring, tolerances, etc. for each of the rails, reset logic for the ICs, an I2C address table for quick reference, testpoint info, etc.

22:46 <q3k[cis]> i am not catherine but i see no reason for this to not be documented in the main docs?

22:48 <gsuberland> :)

22:51 <esden[cis]> I am not Catherine either. :D But I think the best way to make a judgment/discussion of how to integrate it, is if you can share it gsuberland. If you were still "thinking" about it we could have a planning discussion first. :D But as you have already done a bunch of the work the easiest thing would be to create a PR with it and then reorganize rephrase as needed.

22:52 <gsuberland> sure, that works. gimme 2 ticks and I'll throw what I have so far into a gist so you can see the rough idea

22:56 <gsuberland> https://gist.github.com/gsuberland/0affffae190386e0ae2c5c8c5974104c

23:00 <gsuberland> info in there is based on my reading of the schematic and datasheets, essentially whitebox hardware RE, so naturally I'm happy for any additional input and corrections from the folks who actually designed it :P

23:45 <whitequark[cis]> gsuberland: definitely main docs, but yeah i want to start reading it and giving feedback early

23:47 <gsuberland> whitequark[cis]: cool. what's your preferred method for providing preview and organising feedback?

23:47 <whitequark[cis]> depends on the volume

23:48 <whitequark[cis]> for big things I often just work directly with the contributor to avoid the github back-and-forth

23:48 <gsuberland> fair