[00:02] <Bashing-om> krytarik: Will make it as advised for (Mir) .. I should have remembered to look for the EOL notice in the security updates - just slipped my mind amongst all the things I do look for,
[00:03] -SwissBot:#ubuntu-news- ::uwn-commits:: Security Updates: Try and limit output to packages. @ http://git.launchpad.net/uwn/commit/?id=f166209f0078137f19a952d63620a42c4cfcd02f (by Krytarik Raido)
[00:11] <krytarik> I mean my rationale for not doing this earlier was that the few messages on the list that depart from the usual package-related pattern should be easy enough to spot and filter out manually, and therefor it shouldn't be worth it risking a regression in listing all relevant messages - but looking through the hole year back, it seems to be really just between those bracketed package-related ...
[00:11] <krytarik> ... messages and release support-related notices, so..
[00:17] <Bashing-om> krytarik: Looked at the patch - above my skill level to know what you did - I will not fret about my lack here. To update our working UWN directory just execute " git pull " ? 
[00:28] <krytarik> Yeah.  And well, it now filters out any messages whose subject line doesn't start with an opening '[' bracket - this leaves the matching open to more variations in what those brackets contain and therefor should limit the risk of regression sufficiently..
[00:31] <Bashing-om> Will update .. and keep an eye on the ListSecurity.py outputs for a few issues.
[00:33] <Bashing-om> Git: \o/ >> security-and-updates/ListSecurity.py | 2 +- :D
[00:34] <Bashing-om> guiverc: See ^^ the updated script ?
[00:35] <guiverc> ack & thanks !
[01:13] <krytarik> Bashing-om: Well, unless you compare it with the source list page, you wouldn't notice any missing messages in it though of course.
[01:14] <Bashing-om> krytarik: I did run a test of the patched script - Performed as you expected :D
[01:16] <krytarik> Yeah, of course I did too before committing, but..  anyway, like I outlined, I think we should be reasonably fine..
[01:17] <Bashing-om> krytarik: Hey I trust you - in all these years you have never led astray :D
[01:18] <guiverc> the heading on 'New 20.04.4 release date' isn't the same as ML post; is there a reason; if edited we could add "Ubuntu" to it too :)
[01:19] <Bashing-om> guiverc: Lemme look - I do recall something of that nature.
[01:19] <guiverc> it's missing the "Developers! " @ start
[01:27] <Bashing-om> guiverc: I see - But do we want to draw/limit attention to "Developers" here ?
[01:28] <guiverc> I don't mind dropping the Developers!, but if we do, I'd also recommend we add a Ubuntu in heading  (other non-Ubuntu teams have 20.04.4 releases...)
[01:29] <guiverc> my 2c
[01:31] <Bashing-om> guiverc: OH ! Great thought ! so we edit to be "Ubuntu - New 20.04.4 release date: February 24th" ??
[01:31] <guiverc> or I was thinking "New Ubuntu 20.04.3 release date.."  ie. just addition of word Ubuntu in front of 20.04.4
[01:34] <Bashing-om> guiverc: While I do like inserting "Ubuntu" into the title - is that a liberty that is also legal usage ?
[01:35] <guiverc> I'd normally prefer [Ubuntu] but that's a minefield we don't want either... just my 2c/thought. We've edited it already by dropping "Developers!" thus the extra "Ubuntu" doesn't worry me..
[01:36]  * guiverc thinks in for a penny, in for a pound....    
[01:37] <Bashing-om> krytarik: ^ I would apprciate the input from a word smith :)
[01:46] <guiverc> my read thru complete; looks good.  :) @ seeing ivy yang there.. 
[01:46] <guiverc> as reddit is listed & no official posting is done there, we could maybe add https://t.me/ubuntunewsletter too   (it'd need others to have access for that to be official in my opinion)
[01:48] <Bashing-om> guiverc: Thanks - I do my best to encourage ivy yang's participation. Our burden could use some lightening :D
[01:49] <Bashing-om> guiverc: reddit for a whike we had one "slidinghorn" that posted - but has since disappeared - such that I did remove reddit from the list. Now if we can find another I be more than glad to re-list !
[01:52] <guiverc> I've been posting to reddit when I remember; but I can forget the ones I post as 'me'  (I concentrate on official ones with more care there).   I forgot 711 but u/prisoninmate got it; I forgot 707 & 708 I note.. 
[01:52] <Bashing-om> guiverc: Wow ! that ^ will soon be two years ago ! https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Ideas .
[02:03] <Bashing-om> guiverc: Hummm -- thought that I had removed the https://www.reddit.com/r/Ubuntu/ item from the 'Further News' list.
[02:04] <guiverc> reading reddit ref.  (& I didn't expect it, but saw it on a prior issue & looked back on) is what caused my comment..
[02:08] <Bashing-om> guiverc: Well as we do not have a dedicated posting to reddit - should we remove it from the "Ubuntu news and announcements" lists ?
[02:09] <guiverc> My vote would be yes (for removal of reddit ref)... I try & post there, but as outlined ^ I forget ones that aren't official (mewe, reddit, mastodon etc) somewhat regularly..
[02:11] <Bashing-om> gui Removing https://www.reddit.com/r/Ubuntu/ - we can always put it back when the need arises.
[02:18] <Bashing-om> guiverc: How about "New [Ubuntu] 20.04.4 release date: February 24th" where '[]' is accepted as editorial edits.
[02:19] <guiverc> I like that ; was fearful the [] may cause scripting issue thus my hesitation earlier.. 
[02:20] <Bashing-om> guiverc: The use of brackets will ally my concerns :D
[02:21] <Bashing-om> allay*
[02:23] <Bashing-om> UWN: All caught up now to where I may log off ?
[02:41] <guiverc> sorry; all looks good to me Bashing-om 
[02:41] <Bashing-om> guiverc: \o/ 
[08:40] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: MAAS 3.1: Bare metal provisioning of hot metal @ https://ubuntu.com//blog/bare-metal-provisioning-of-hot-metal
[12:08] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Internet of Things and Ubuntu: 2021 highlights @ https://ubuntu.com//blog/iot-and-ubuntu-2021
[17:08] <krytarik> Bashing-om, guiverc (via logs): I'd be fine with leaving the 20.04.4 header without a reference to Ubuntu, since the article is featured in the General News section where only stuff pertaining to Ubuntu go anyway..  If you insist on adding "Ubuntu" somewhere in the header though, then I'd vote for not using the bracketed form, because that generally looks odd in a header (and yes, I also ...
[17:08] <krytarik> ... think it may cause issues with the script)..  Either way, since we've already done editorial addition on the Mir release article, I think both should follow the same style, in which case I'd prefer putting the missing terms where they really belong in the header.. rather than what I've been told ended up as "(Mir)" behind the original header text so far, because I think that looks also odd..
[20:03] <Bashing-om> UWN: I am getting "Internal Server Error" for our WIKI: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue713 . Someone try and confirm it is not my system with an error.
[20:13] <Bashing-om> UWN: Vlearing my cache resolved the connection issue :D
[20:24] <Bashing-om> krytarik: I read the log - and in accordance have edited the 2 items in "In this Issue", I have left the summary headers intact.
[20:35] <Bashing-om> guiverc: Edited once more --- see the log from last night. See if you agree with what now I have done for the Mir release and the Ununtu point release titles in "In this Issue".
[20:36] <krytarik> Bashing-om: Uhm, if you are editing the title, I assumed you are editing it in both places, the header of the article as well as in the issue summary.. O_o  Also, it still reads "Ubuntu New 20.04.4 release date", which as guiverc pointed out should be "New Ubuntu 20.04.4 release date" instead.
[20:36] <Bashing-om> UWN: Edits done and "WIP" pulled. Expect to push at 21:00 UTC .
[20:39] <Bashing-om> krytarik: Ack on Ubuntu . will make it as such . change aslo the summary tittle so that the table of "contents" gets updated ?
[20:42] <Bashing-om> krytarik: How about the added Mir "Mir Release 2.6.0" ? Should I also update the summary header ?
[20:43] <krytarik> Yes, I've been assuming you did it in both places, rather than only in the issue summary - because yes, that would also produce invalid links in the Frdige post.
[20:44] <Bashing-om> Great ! saving :D
[20:48] <krytarik> Now it's "New ubuntu 20.04.4 release date" in the issue summary, but uppercase "Ubuntu" in the header. >_<
[20:48] <guiverc> it'll be great Bashing-om ; i've not a lot of time next ~2 hours so assume I'm fine with what you need to do
[20:50] <krytarik> Also, could we move the Kylin article to the bottom of the General News section?  It being a flavor vs general Ubuntu news etc..
[20:51] <Bashing-om> krytarik: ack - doing ^ :D
[20:57] <Bashing-om> UWN: ^ Done - preparing to push - 21:00 UTC .
[21:00] <Bashing-om> UWN: ubuntu-news@lists is away - doing the Forum post next .
[21:15] <guiverc> okay to push UWN 713 to fridge Bashing-om ?  (when I'm ready)
[21:15] <Bashing-om> UWN: Forum Post done - abridgements; doing the re-directs next.
[21:30] <Bashing-om> UWN: Re-directs also completed - Pending is release to the Social Medias :D
[21:48] <guiverc> https://fridge.ubuntu.com/2021/12/13/ubuntu-weekly-newsletter-issue-713/
[21:49] <guiverc> tweeted 713 & sent via telegram
[21:56] <Bashing-om> Fridge: Spot check - checks good :D
[22:05] <guiverc> uwn 713 posted to fb too
[22:11] <Bashing-om> guiverc: 
[22:12] <Bashing-om> \o/ --- clear now to wipe Gdoc and put issue713 in the history file ?
[22:12] <guiverc> yep scrub away :)
[22:12] <Bashing-om> doing !
[22:13] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 713 @ https://fridge.ubuntu.com/2021/12/13/ubuntu-weekly-newsletter-issue-713/
[22:24] <Bashing-om> guiverc: Nother ooops on 713 :( please change in the Fridge's date " Welcome to the Ubuntu Weekly Newsletter, Issue 713 for the week of December 5 - 11, 2021." :( 
[22:26] <guiverc> give us a sec & not a problem; I should have detected that, as remember double-stepping on date but dismissed it
[22:28] <guiverc> ouch - it's in microblog.txt so will be everywhere too
[22:29] <guiverc> hold on 5-10 isn't an entire week (6 days without any saturday)
[22:32] <krytarik> guiverc: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue713?action=diff&rev1=33&rev2=34 - for posterity.. but yeah, a bit sad that tag line is wrong to begin with..
[22:35] <guiverc> okay I missed the 11 change...  my mistake & I understand now
[22:36] <guiverc> it's happened before ; dates aren't much fun when they don't match with your own [local] clocks
[22:37] <krytarik> Yeah, and for my part I never look over those in the first place.. >_>
[22:38] <guiverc> deleted old tweet, re-tweeted 713
[22:39] <guiverc> didn't say so ^ but fridge was changed
[22:40] <Bashing-om> I just caught my opps on the date when the dates did not add up for issue714.
[22:40] <krytarik> Personally I'd have been fine with leaving the social media stuff alone once it's out though.. >_<
[22:41] <guiverc> if it's not easily done, that's what I was going to do anyway  (telegram isn't easy .. a follow-up correction post would be messy..)
[22:44] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Kdenlive Video Editor Gets a Blockbuster Update (Yes, New Pro Features) @ https://www.omgubuntu.co.uk/2021/12/kdenlive-21-12-video-editor-release-new-features (by Joey Sneddon)
[23:12] <guiverc> thanks krytarik & Bashing-om 
[23:12] -SwissBot:#ubuntu-news- ::Fridge:: Ubuntu Weekly Newsletter Issue 713 @ https://fridge.ubuntu.com/2021/12/13/ubuntu-weekly-newsletter-issue-713/ (by guiverc)
[23:14] <Bashing-om> guiverc: My error and sorry I caused all this grieve :(
[23:16] <guiverc> not an issue... i think i had 2 date mixups & you've collected/posted many times whatever I did (years ago)