[00:02] <Eickmeyer> Bashing-om: I mean, maybe? We're 2 months out from 24.04 which is going to blow that out of the water in terms of usability and technology upgrades. We're talking zero-configuration out of the box and no more having to mess with JACK (Jack Audio Connection Kit, I'm not shouting).
[00:02] <Eickmeyer> I'm just wondering why someone is looking at 22.04 now. Doesn't make sense.
[00:03] <Bashing-om> Eickmeyer: I be open to pulling this one -- as yeah 22.04 is old old news.
[00:06] <guiverc> Eickmeyer, I've not watched it (started now), but if it's positive, I'd expect its benefecial overall (even if dated)
[00:10] <Eickmeyer> Right. I'm just thinking like this vs 23.10: To even use some of those applications in 22.04, you have to start JACK as it doesn't run by default. To do that, you have to first run Studio Controls, map it to your audio card, Click "Start JACK", and hope for the best.
[00:10] <Eickmeyer> In 23.10, everything works out of the box because PipeWire, with how it's configured in Ubuntu Studio, handles the JACK protocol natively along with the PulseAudio protocol. In terms of audio, I'd say it's on-par or better than macOS at this point.
[00:11] <Eickmeyer> So, my question is do we want to represent Ubuntu Studio how it *was* vs how it *is*?
[00:12] <guiverc> Eickmeyer, you have the best clue (by far!!!!) as to whether or not it's valuable; we'll do whatever you believe is best for you & your Ubuntu Studio team.
[00:12] <Bashing-om> Eickmeyer: Might prove real great to add a "disclaimer" with that above to move people to latest release.
[00:14] <Eickmeyer> Right. The thing is, despite 22.04 being the current LTS, 23.10 has by far the best UX because of the reason above. At this point, because 23.10 is a shorter skip to 24.04's UX, I steer people toward 23.10 despite the shorter cycle if they understand they need to upgrade to 24.04 shortly after it comes out.'
[00:15] <Eickmeyer> Bashing-om: I like the disclaimer idea.
[00:15] <guiverc> I'm happy wtih disclaimer Bashing-om if you wish or find it helpful.. 
[00:15] <Bashing-om> Eickmeyer: I make it so :D
[00:26] <guiverc> Eickmeyer, i just made a comment on that video, if you want correction/change; please just let me know
[00:27] <Bashing-om> guiverc: See that the discaimer rubs in a right way :D Longer than the summary itself.
[00:27] <guiverc> ack will do (I've not reviewed current uwn yet today)
[00:29] <Bashing-om> guiverc: ^ :D - as you can tell from the length of time to get this issue together - was a frustrating process - proof reading indeed required.
[00:29] -ubottu:#ubuntu-news- ::omg!ubuntu:: Ubuntu 24.04 Will Use Linux 6.8 Kernel (If All Goes to Plan) @ https://www.omgubuntu.co.uk/2024/02/ubuntu-24-04-linux-kernel-6-8-likely
[00:30] <guiverc> ack & thank you for your work & diligence Bashing-om 
[00:32] <Bashing-om> guiverc: Takes all of us to do this - what we present to the puplic at large is worth our diligence.
[00:32] <guiverc> yep.
[01:04] <Eickmeyer> Bashing-om, guiverc: making some small edits to where you quoted me, just to clarify.
[01:05] <guiverc> i didn't mention you by name... (wanted to, wasn't sure if helpful & decided it may carry more weight if I didn't thus didn't)
[01:06] <guiverc> sorry; i was thinking youtube thingy... 
[01:07] <guiverc> (& my comment on youtube itself..)
[01:07] <Bashing-om> Eickmeyer: Pleased that you take up our slack :P
[01:08]  * guiverc hasn't got that far... still in 'the hub' in review
[01:08] <Eickmeyer> I do what I can, when I can. Helps that I'm a discourse mod so I can jump-in as needed. :)
[01:09] <Bashing-om> Friends in high places :P
[01:14] <Eickmeyer> hehe
[01:14] <Eickmeyer> Ok, done editing/formatting. I *think* it looks good.
[01:25] <Bashing-om> Eickmeyer: ^ proof reading :P
[01:25] <Eickmeyer> That too.
[01:27] <Bashing-om> Eickmeyer: Well done as you have it :D
[01:27] <Eickmeyer> \o/
[01:33] <guiverc> Bashing-om, I don't use `telling` in my normal speech; but maybe s/In the telling some of these features we are told/In the telling of these features we are told/  ... ie drop 'some'  ??
[01:35] <guiverc> ubuntu touch article i think needs 'touching'..  ..
[01:36] <guiverc> s/since it rebasing on Ubuntu 20.04 LTS/ to either 'its rebasing on' or 'since rebased on'
[01:38] <guiverc> we could get rid of space in "improvements ; and" before ";"  but optional
[01:40] <guiverc> :)  @ disclaimer; thanks Bashing-om Eickmeyer 
[01:41] <guiverc> is 'disclaimer' the right word??  seems a little harsh.. should it be Addendum, or Notice: ??
[01:42] <Bashing-om> guiverc: Doing those edits soonest.
[01:42] <guiverc> (even "Please note:" but I use that all the time... I prefer something less harsh than disclaimer though)
[01:43]  * guiverc is just listing what I see as I read thru... you may disagree; or I can edit to reflect ^ too
[01:47]  * guiverc notices a security notice dated 26-jan, but I don't see it on uwn824 so no issue with it
[01:48] <guiverc> looks good Bashing-om , my read thru done
[02:00] <Bashing-om> guiverc: "Disclaimer" Me thinks still correct > "Statement ritually appended to many Usenet postings (sometimes automatically, by the posting software) reiterating the fact (which should be obvious, but is easily forgotten) that the article reflects its author's opinions and not necessarily those expressed."
[02:01] <guiverc> fair enough... 
[02:02]  * guiverc expresses (commnonly) my reaction/thoughts; alas doesn't mean I'm right...
[02:03] <Bashing-om> UWN: saved and out - edit count stands now at 23.
[02:04] <Bashing-om> guiverc: Was for a fact a valid point -- and if I could come up with a better term than disclaimer // my poor communications skills :( 
[02:07] <guiverc> Would just using "Note:" work??
[02:11] <Bashing-om> guiverc: Yep -- should work for our use case here :D making it so.
[02:14] <Bashing-om> UWN: 24 edit count :D
[02:17] <guiverc> no free set of steak knives earnt yet though....
[02:19] <Bashing-om> Ham N cheese sammich helps though :P
[02:31] <Bashing-om> Break - going to visit the rain locker.
[21:21] <Bashing-om> UWN: Pulling WIP/WIKI - noted the newlines in the header// Will start the push soonest.
[21:52] <guiverc> https://fridge.ubuntu.com/2024/02/05/ubuntu-weekly-newsletter-issue-825/   (I manually adjusted Welcome at start)
[21:55] <Bashing-om> UWN: M/L is away too - doing the Forums posting next.
[21:56] <guiverc> posted 825 to telegram , twitter
[22:12] <guiverc> posted 825 to (mewe) & fb
[22:13] <Bashing-om> Posted the Forums - making up a Mastodon blog next.
[22:42] <Bashing-om> UWN: Bloged Mastodon.
[22:44] <Bashing-om> guiverc: Next up is to see what I can finger out about importing the skeleton for 826 :D
[22:45] <guiverc> it sounded easy... (doesn't mean it is, but fingers crossed)
[22:46] -ubottu:#ubuntu-news- ::omg!ubuntu:: Microsoft’s VS Code Drama Gets a (Temporary) Happy Ending @ https://www.omgubuntu.co.uk/2024/02/vscode-recovery-update-for-ubuntu-18-04
[23:16] <Bashing-om> guiverc: Were not too difficult to finger out - it is not - as advertised - completely automatic. Will take note of the omittrd step that worked in this issue template import. It do workie !
[23:18] <guiverc> :)     alterantive ways (to accomplish a task) are almost always of benefit
[23:18] <Bashing-om> UWN: Issue826 Screeching hot off the line start :)
[23:19] <Bashing-om> guiverc: Import the template is much easier and faster :P Once we know how :P
[23:20] <guiverc> :)