(if we want / need a topical meeting before, about this topic for example, we can always schedule it)
2025-12-17 35154, 2025
bitmap[m]
I'm fine to meet on tuesdays, even if it's only a short meeting
2025-12-17 35157, 2025
reosarevok[m]
I'm mostly planning to have a holiday during the holidays, but I'm sure I'll be around to some degree (emails, spam, etc) and I can talk code if forewarned
2025-12-17 35104, 2025
yvanzo[m]
I won’t be able to achieve a lot more in the two next weeks either.
2025-12-17 35132, 2025
op3kay[m]
<op3kay[m]> "reosarevok: regarding the..." <- reosarevok bitmap : no rush, please take a look at this when youre free :)
2025-12-17 35152, 2025
v6lur joined the channel
2025-12-17 35154, 2025
reosarevok[m]
Yeah, sorry, I saw but was busy earlier. bitmap: if you have time to take a quick look? :)
2025-12-17 35117, 2025
op3kay[m]
reosarevok[m]: no worries :)
2025-12-17 35133, 2025
bitmap[m]
I don't have a good recollection of the codebase, so it won't be quick, but I can have a look
2025-12-17 35140, 2025
reosarevok[m]
op3kay: keep in mind we generally slow down around the Christmas period so communication might get worse - but playing with stuff is always encouraged
2025-12-17 35120, 2025
reosarevok[m]
bitmap: I think it's at a level where "what are the priorities we want to concentrate on" might be more important than the state of the codebase itself
2025-12-17 35150, 2025
reosarevok[m]
(I took a quick look to remind myself, and it's generally very half done, so)
2025-12-17 35104, 2025
op3kay[m]
reosarevok[m]: No worries at all! ill explore around and experiment a bit
2025-12-17 35107, 2025
reosarevok[m]
(the one positive is that it's half done enough that pivoting it is doable)