[01:12] <guiverc> looked thru uwn 810 & looks good to me (thus far).  Bashing-om, I ~suggested opening uwn in collection/summary phrases as wiki (after you were gone yesterday) as it will make it easier for others to join in on work; we can thus remove wiki for final edits maybe & prior to publish  (I didn't test that; looks to me like we can do it anyway)
[01:19] <Bashing-om> guiverc: Regrets but I do not recognize the term " collection/summary phrases" :(
[01:20] <guiverc> sorry; collection phase when you're collecting, summary the weekend - my mistype (extra R) was error sorry (I didn't notice)
[01:25] <Bashing-om> guiverc: Formerly there was a number of steps to complete wiki.ubuntu.com/UbuntuWeeklyNewsletter/ // now directed to Discourse completion. Do you suggest that I pause in Discourse at each step of the way ?
[01:30] <guiverc> no.  I don't recall what is on wiki; but when we publish current issue we can adjust some to point to discouse for newer work; maybe https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter/359  which can be edited further (as required) etc.. You do what you normally do, as that is the normal way.. wiki will be older way I bet
[01:33] <Bashing-om> guiverc: After I puplish I will point to: https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-issue-810/39XXXX / And while doing the normal re-directs I will fix old Gdoc links to point to https://discourse.ubuntu.com/c/uwn/124 .
[01:34] <guiverc> :) & thanks
[01:39] <Bashing-om> guiverc: I anticipate that tomorrow as soon as the Discouse issue is completed that I also make up the WIKI for issue810. - Monday long about 19:00 UTC will pull "WIP". IF there are no other edits to be made, soonest after will put out the release notice M/L.
[01:41] <guiverc> I wondered if we'd be required to make up the wiki due to script issue.. but I wasn't planning to create it (unless required so we can run scripts against it)
[01:42] <guiverc> I've not recently run testing on our scripts from discourse.. thus the wiki creation was my planned fallback should script issues occur
[01:43] <Bashing-om> guiverc: For now the WIKI is needed for those subscribing to the newsletter.
[01:45] <guiverc> ack.  as you do most of the publishing you'll know (remember) more than I do
[01:48] <Bashing-om> guiverc: I be the grunt in this operation. Mine is not to reason why :P // However, if we were to to longer push out the full WIKI via  M/L would sure lighten the load on the WEB.
[01:52] <Bashing-om> guiverc: Mailing List could just a a notice that hte issue is completed .. " Dear reader: issue8XX now available -https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-issue-8XX/XXXXX" LD 
[01:54] <guiverc> the ML post was just the wiki page sent as far I as can see (looking at 809 in my inbox; reads like I was looking at wiki source); so we could do the same from discourse if we wanted it long (not <!--comments--> though) or just link to page alone
[01:56] <Bashing-om> guiverc: A big change in tradition - will take a lot of thought before action on this.
[02:00] <Bashing-om> guiverc: My vote remains though to send a link and watch the Discourse view count increase 20 fold. Making up the WIKI is duplicate effort from making up the Discourse page.
[02:04] <guiverc> yep.
[12:01] <krytarik> Bashing-om, guiverc: So a few things to clear up..  Yes, the content sent out via email was always just the wiki source minus a few wiki-specific formatting, and so the same is now done by the publish script adjusted to Discourse.  I doesn't currently take care of any comments in the source, so it'd be nice to continue with the habit of removing the comments as you complete the issue.  And ...
[12:01] <krytarik> ... wrt the wiki, 1.) I'd stop publishing the final issue to the wiki right away, as it's not needed for technical reasons and the single source of truth is on Discourse now; and 2.) I don't feel like we'd particularly gain anything by even using the wiki temporarily for completing the issue, if we need a platform that allows for broader access to editing because Discourse isn't as flexible  ...
[12:01] <krytarik> ... here, then I think there might still be an Ubuntu Etherpad instance around we could use for this, but generally I think copying parts of the issue forth and back just complicates things further - plus the history of pages on the wiki is still retained even after deleting the page, so we'd be blowing up the database by using the wiki as a temporary editing platform.
[12:05] <guiverc> thanks krytarik 
[12:23] <krytarik> Uhm, as I'm just looking at the source of the current issue on Discourse, could you please continue formatting the headers like "## Foo ##" as we were used to on the wiki?  I think this makes the headers stand out more in the source (which will be used in the email as said), it shouldn't make any difference on Discourse, and in assuming we do so the Fridge script fails at parsing out the ...
[12:23] <krytarik> ... issue summary currently.
[12:24] <guiverc> okay will do; it was me that didn't use trailing ## (or ###) I believe
[12:30] <krytarik> And the license reference at the bottom should still be converted into "Commons Attribution ShareAlike 3.0 License" being a link to the license text as I mentioned the other day.  Another thing is the publish script currently doesn't strip out images either, but even if it's forgotten to pull from the text before sending out as email then it's only two of them as usual..
[12:32] <krytarik> guiverc: And as I also said that day, could you try on Discourse if putting the image in front of the license text works the same as on the Fridge?
[12:34] <guiverc> what link krytarik (cc by-sa 3.0) - is this okay ?  https://creativecommons.org/licenses/by-sa/3.0/deed.en   or did you provide another?
[12:35] <krytarik> Just the one we've been using on the wiki and on the Fridge so far.
[12:35]  * guiverc grunts ; didn't think of looking on wiki for link :(
[12:35] <krytarik> Unless of course it needs updated.
[12:36] <guiverc> https://creativecommons.org/licenses/by-sa/3.0/   (from fridge; on my posts there too it seems!)
[12:37] <guiverc> that link added to 810; adding to skeleton (before I forget)
[12:38]  * guiverc adding a request to remove comments prior to publish whilst in skeleton
[12:51]  * guiverc added trailing ##, ### on 810 & skeleton (hopefully none missed), some comments removed from 810
[12:56] <guiverc> krytarik, the fridge text currently exists (along with ^older version) on skeleton... it looks weird in preview (spacing is wrong) but when saved it looks better ... not identical to fridge though
[12:58] <krytarik> Uhm, first I just noticed you included "licensed under a" in the link text on Discourse, please only put the actual license name as the text as we are used to.
[13:00] <krytarik> I'm currently working to make the scripts drop all comments, images, and excess empty lines from the source.
[13:01] <krytarik> And seems like you went over my question regarding the license image placement.
[13:02] <guiverc> i only modified https://discourse.ubuntu.com/t/uwn-skeleton-template/39501  (which has untouched first, then the fridge version currently in comparison; it showed differently whilst in preview on my screen)
[13:04] <krytarik> Yeah, I'll have to log in to the Fridge to see this one still.
[13:09] <krytarik> Ah, you referred to only the image thing by that! XD
[13:12] <krytarik> Hmm ok, I'd say let's just make the colon there into a period and be good instead.
[13:14] <guiverc> so the upper one (unchanged from yesterday) with ":" becoming a fullstop.  will do
[13:15] <krytarik> Yeah, the upper one with just the link added.
[13:16] <guiverc> i added link to 810... didn't bother with skeleton as I had to edit it to remove one of ends anyway... 
[13:17] <guiverc> done.
[13:18] <guiverc> Thank You krytarik  !
[13:18] <krytarik> Well, I didn't look at the template until just now, and when I pulled the 810 post before mentioning this it certainly still had no link.
[13:19] <guiverc> 810 didn't before I added it; it had issues saving (may have if you'd edited, discourse doesn't cope with two editors) .. but it's saved on both now, at least that I can see
[13:20] <krytarik> Now to the current issue, while I see it please add an empty line after the very first link in the General News section, and drop the excess second space in front of the trailing '##'s you just added.
[13:21] <krytarik> Nah, wouldn't have been me, since I'm not even a user there yet. >_<
[13:22]  * guiverc wonders if discourse was just being annoying...  
[13:29] <guiverc> done (3 double spaces I think removed)
[15:00] <krytarik> Bashing-om, guiverc: I just pushed a few updates to the script repo, so "git checkout discourse; git fetch origin discourse; git reset --hard origin/discourse" iirc to update your local copy.
[18:49] -ubottu:#ubuntu-news- ::omg!ubuntu:: 7 Spooky Desktop Wallpapers for Ubuntu @ https://www.omgubuntu.co.uk/2023/10/eerie-desktop-wallpapers-for-halloween-linux
[22:37] <Bashing-om> UWN: Issue810 up for review and final edits: https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-issue-810/39540 - https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue810 :D
[22:40] <krytarik> Bashing-om: Did you check the channel logs from earlier today?
[22:41] <Bashing-om> krytarik: Ouch no I failed tp check - had my mind on what it would take to do Discourse :(
[22:49] <krytarik> Bashing-om: Same as last week, there should be an empty line added after "Please see" in the LoCo Events section (on Discourse, on the totally unneeded wiki post there is also a missing empty line above of the "Looking beyond" line there)
[22:51] <Bashing-om> krytarik: fixing - will also need to re-read the channel log of yesterday for penetration.
[22:52] <krytarik> On Discourse there is also an excess empty line above of the LoCo Events header - although this won't matter so much since I've earlier today made the publish script strip out excess lines.
[22:58] -ubottu:#ubuntu-news- ::omg!ubuntu:: Errands is a Top To-Do List App for Linux Users @ https://www.omgubuntu.co.uk/2023/10/errands-todo-list-app-for-linux
[23:02] <krytarik> Bashing-om: 1.) There is also an empty line too many above of the Planet header, 2.) you missed dropping the "Good Luck from the UWN Team.  -->" of the comments at the top, which does show in the rendered page, 3.) "## Ubuntu Stats  ##" has a space too many before the closing '##'s, and 4.) some of the headers in the Audio & Video section need closing '##'s added yet - all of the latter ...
[23:02] <krytarik> ... being on Discourse.
[23:16] <krytarik> Bashing-om: Also, I just read that in order to disable previews of links that are on their own on a line, as it's the case with the links under our summaries, one can just put a space in front of the link (so at the beginning of the line) - could you try doing this with the links in the Discourse post that currently are rendered as previews?  In fact, I wonder if we shouldn't just format ...
[23:16] <krytarik> ... all these links the same, regardless of whether they get previews or not - this way the publish script won't have to strip out the extra space in front..
[23:19] <krytarik> Uhm, just noticed the quote(s) under the Security podcast seem to partially repeat themselves?
[23:24] <krytarik> Looking at the podcast page, turns out the first quote is correct and the second one is erroneous.
[23:42] <Bashing-om> UWN: Edits ^ done - think I got them all and a couple of others I saw in passing again.