[01:50] <Eickmeyer> Bashing-om: There's no way that was an intentional redirect. You might have to skip the loco event section or just populate from last week as much as possible.
[01:51] <Eickmeyer> I don't even know who to contact except maybe the Canonical Community Team in #ubuntu-community-team, perhaps fallen would know what's up.
[01:55] <Bashing-om> Eickmeyer: Recently all the LoCo pages have seen updates - I reckon loco.ubuntu.com/events/ is collateral damage.
[01:56] <Bashing-om> Eickmeyer: Lemme see if Fallon is awake :D
[01:59] <Eickmeyer> Agreed, probably just slipped through. Probably all of the wiki pages getting moved to discourse, similar issues.
[02:29] -ubottu:#ubuntu-news- ::planet:: Alan Pope: i386 in Ubuntu won't die @ https://popey.com/blog/2023/08/i386-in-ubuntu-wont-die/
[03:38] <guiverc> Bashing-om,  I'll suggest dropping "The following LoCo team events are currently scheduled in the next two weeks: "   (makes no sense give none follow; except for reason... just have the reason I say)
[03:40] <guiverc> suggest dropping "that is, " from first Guadec 2023 event report.
[03:40] <guiverc> (gdoc not marked; yet anyway ... )
[03:42] <Bashing-om> guiverc: Yeah - will do a re-do of LoCo Events // pending if we have a resolution by the time of publishing ( still to delete the "#s" also).
[03:42] <Bashing-om> guiverc: Logging onto our WIKI - editing mode engaging :D
[03:43]  * guiverc reading wiki  (full screen... thus my chromium/oogle-editor is out of reach..why not touched)
[03:56] <guiverc> Bashing-om,  should "writes about the the new budgie 10.8 release" have Budgie in capials (other community) ??
[03:56]  * guiverc suspects it should have
[03:57] <guiverc> we're inconsistent if not change anyway; suggest capitilizing (real word?) the first 'budgie' use
[03:58] <guiverc> first "in the press" article has a `".,`  where the `.` needs removal I believe
[03:58] <Bashing-om> guiverc: Sounds reasonable to me - ooking --- and I made addition edits to the Guadec 2023 event report. See that it re4ads well now.
[04:02]  * guiverc will check shortly... still scrolling down (when not called away from terminal..)
[04:14] <guiverc> Bashing-om, ubuntu pro article; are you happy with "Pros & Cons" as written?   I'm wondering if out-of-place, and "'pros' & 'cons'" would be better... though 99% of readers won't likely notice
[04:15] <Bashing-om> guiverc: Agreed - lower case apprpriate.
[04:15] <guiverc> suggest adding a "and" after comma to  ' ", "clean-up to the AMD Zen '   (if that makes sense)..
[04:16] <guiverc> ^ me just wants an "and" between the two super-long quoted bits
[04:18] <Bashing-om> guiverc: Yup - "and" added.
[04:18] <guiverc> Bashing-om, maybe s/these, sitting/what is sitting/  for the HID Driver improvements one  (sentence reads awkardly to me)
[04:19]  * guiverc didn't get to re-visit gdoc yesterday sorry
[04:23] <guiverc> my read thu is (finally) finished, looks good Bashing-om 
[04:27] <Bashing-om> guiverc: Only so much we can do with the time on Earth we are given - got to sleep sometimes :D // Additional edits made to the "HID Driver" summary, see too that you like - as well as the rewrite of Guadec 2023 event report.
[04:31] <guiverc> looks good Bashing-om (I didn't note change to Guadec one, but nothing 'screamed' as needing attention to me, and line formatting had changed I noted thus changed)
[04:32] <guiverc> thank you good Sir.
[04:33] <Bashing-om> guiverc: And thank you - I often fall so short of the glory - addle brained sometimes too :D
[04:35] <guiverc> :)   going away from keyboard (got tops of weeds to trim & other stuff in the yard that needs attention)
[04:40] <Bashing-om> guiverc: ^ these kinds of things best done while the sun shines :P
[14:42] -ubottu:#ubuntu-news- ::omg!ubuntu:: Linux Kernel 6.5 Released, This is What’s New @ https://www.omgubuntu.co.uk/2023/08/linux-kernel-6-5-features
[15:42] -ubottu:#ubuntu-news- ::omg!ubuntu:: Ubuntu 23.10 Fixes Blindingly Bright Wallpaper Faux-Pas @ https://www.omgubuntu.co.uk/2023/08/ubuntu-23-10-fixes-its-blindingly-bright-wallpaper-faux-pas
[19:06] <Bashing-om> UWN: Log checked - no futher edits are known -- pulled "WIP" / LoCo Events section edited to reflect non availability. Will start the push soonest.
[19:29] <Bashing-om> UWN: M/L is away - doing the Forums posting next.
[19:45] <Bashing-om> UWN: Forums post completed - doing Discourse posting next.
[20:24] <Bashing-om> uwn: Discourse posting done - doing the Re-directs next.
[20:55] <Bashing-om> UWN: Re-directs done - doing a Mastodon blurb next.
[21:22] <Bashing-om> UWN: Blog on Mastodon done - pending now is release to the other Social Media.
[22:48] <guiverc> i'm remocing Loco (not available) line from fridge (802)
[22:49] <guiverc> https://fridge.ubuntu.com/2023/08/28/ubuntu-weekly-newsletter-issue-802/
[22:57] <guiverc> posted uwn 802 to twitter, telegram (mewe),  (skipped reddit; marked for support only posts)
[22:58] <Bashing-om> Fridge: Spot check and all looks good.
[23:00] <Bashing-om> guiverc: ^ "remocing Loco (not available) " Something that I should have done up different ?
[23:01] <guiverc> nah... I just felt the link (not available) being 'clickable' where it opened to top of page wasn't helpful - thus removed it.  (not highlighted with clickable link on fridge)
[23:04] <guiverc> I could have worked on to try and point to LocoEvents..   opted to remove; but I like what you did.
[23:05] <guiverc> I could have changed it to "https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue802#LoCo_Events" for exampl
[23:08] <Bashing-om> guiverc: The only reason I opted to keep the entry was for consistency in releases - that our readers might miss the LoCo notices.
[23:08] <guiverc> I can add the link to fridge; do you think it's better there (with link I posted ^) ? Bashing-om 
[23:12] <Bashing-om> guiverc: As we have no metrics - hard to judge if the ommision is meaningful at all :( Fridge is your domain - I will acquise to your choices :)
[23:16] <guiverc> I've added the line back (with altered link) Bashing-om (look again, though may need to incognito/private etc to notice updated page)
[23:18] <guiverc> it DOES draw attention to the revitalizing effort text you wrote.  a plus with it there.
[23:20] <Bashing-om> guiverc: Looks and links good // should we now wipe away our evidence ?
[23:20] <guiverc> yep scrub away...
[23:21] <Bashing-om> guiverc: Ho-Kay - wipe/clean/rinse/repeat in process :D
[23:39] <Bashing-om> UWN: Issue803 is off and running :P