=== arraybolt3_ is now known as arraybolt3 [09:18] FWIW I have never witnessed a bridge between two chat protocols which wasn't actively harmful to one side of the chat. [09:19] In my experience it's Matrix which is the harmful actor in every single one of these situations. [09:19] ๐Ÿ‘ [09:36] โ€œDad why is my sisters name rose?โ€ Because your mother loves roses โ€œThanks Dadโ€ No problem Ubuntu 22.04.1 LTS !!! [09:48] is that a community riddle oerheks :p [09:49] yes, dad [09:49] lol [14:20] Eickmeyer: did you learn anything new regarding the bridge? Should I reach out to someone at libera? [14:20] It should be operational now. [14:21] Test [14:21] Looks good [14:21] All is well. [14:21] Perfect, thank you! [14:26] The long and short of it is Libera outsourced the running of the bridge to Element Web Services (they no longer run the bridge themselves), and a scheduled restart happened during a netsplit, which caused havoc on the bridge. [14:32] outsourcing the maintenance of one of your core components is indeed a clever move ... [14:33] just wait til canonical outsources kernel maintenance to microsoft ๐Ÿ˜› [14:47] my old company used to have a laugh-cry emoji I'd like to use here :) [14:55] its like outsourcing your default browser to... oh wait :P [14:58] well, i wouldnt mind if we could outsource maintaining our kernel to linus like we did with the browser ๐Ÿ˜‰ [15:00] how is he doing with code of conduct latetly? could be a liability :D [15:00] haha [15:01] https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1989359 [15:01] some cool walls amongst them [15:05] would be awesome to have a winner that can be releases with all the available color sytles gnome offers now [15:05] *released [15:06] yeah [15:06] i mean there are like 3 greens. so maybe one of them would be ok :) [15:07] but blue, orange, green, red would be awesome [15:16] Fallen: I've recently gotten caught up with a different project and haven't been paying a whole lot of attention to the documentation stuff. Is there anything in particular I should be doing for us to stay on schedule? [15:23] arraybolt3: I'm a bit behind myself, had some other responsibilities to take care of last week. I think what I am missing mainly is the call to action, e.g. where do we point folks so they can get started. The simplest option would be (simplified) "go to #ubuntu-doc and tell us you are interested", but requires a bit more manual conversations. The more involved option would be "Here is a page about the effort, a tracker, and how to get [15:23] started, and also hang out on IRC so we can chat with you", but that will take a bit longer to get out and might make it more difficult to align people. [15:24] How do you think we should be starting the conversation with folks? [15:25] While it will require more manual conversations if we go with "poke your head in #ubuntu-doc and ask", that's essentially what Lubuntu does (IIRC), and that's how I ended up onboarding with them. [15:26] This was all of the info I had about contributing to Lubuntu when I first came in: https://manual.lubuntu.me/stable/B/Contributing.html and https://lubuntu.me/links/ [15:26] Fallen: So since that seems to have worked well, that would be my first thought. Give a general idea of what to do, then come in and chat to get the details and become onboarded. [15:27] (Become onboarded... /me wonders if that's actually a term) [21:34] I've used it for sure, maybe "get onboarded" :D I think that is reasonable. I've let the CC know, I think if we don't get an answer until Thursday we can proceed. [21:39] Fallen: Nice! (Hey, if you sent any messages before this most recent one, I missed them - power company messing with stuff = power outage = IRC outage :( so if you sent anything I missed I'd appreciate it if you could re-send it.) [21:39] Nothing inbetween :) [21:40] Nice.