[09:27] i went into uwn doc, didn't find any needing summaries - looks done :) (or I need stronger glasses) [12:38] yay, FFMPEY "Wu" 4.0 http://ffmpeg.org/index.html#pr4.0 [12:38] FFMPEG* [14:42] ...Wait, with the current highest role of editor for any of us on the Fridge's WP, we can't even change the widgets on the site!? [15:04] (I merely wanted to see if we could add button linked to the general @ubuntu_news Twitter account alongside the RSS one to the Subscribe widget.) [15:30] no, we just submit tickets when we want something changed, in reality it's pretty rare [15:31] That really makes me want to cry now. :D [15:32] now that you're the boss you're welcome to talk to them about opening access, but I chose my battles with Canonical IS and this one wasn't worth it to me ;) [15:33] Yeah, I hear you. [21:06] memory leaks fixes in 18.04 LTS: The probable fix is in . https://feaneron.com/2018/04/20/the-infamous-gnome-shell-memory-leak/ . Do we re-write the original summary or replace it ? [21:49] krytarik, Bashing-om this is pretty important, it just came out today https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Shell-Memory-Leak-Fix do we want to add it? [21:50] Wild_Man: Awaiting response drom above " memory leaks fixes in 18.04 LTS: The probable fix is in . https://feaneron.com/2018/04/20/the-infamous-gnome-shell-memory-leak/ . Do we re-write the original summary or replace it ?" . [21:51] You two figure it out! :P [21:53] Bashing-om, I would replace it [21:54] The new link is a much more concise article and easier to read imo [21:54] Wild_Man: I am all for adding an editorial note to what we have, to see an additional summary . [21:56] woNot doing the backgraound research .. but feaneron seems to be the project leader . [21:59] Oh btw, I'd still like someone other than myself (conflict of interest) to work over the Studio reboot summary 1.) so the currently only sentence makes more sense, and 2.) hopefully get together an additional one. :) [22:00] Bashing-om, I do not find the link you posted, I thought the gnome leak was published in the 523? [22:04] Wild_Man: 524: https://community.ubuntu.com/t/help-test-memory-leaks-fixes-in-18-04-lts/5251 // my new source: https://feaneron.com/2018/04/20/the-infamous-gnome-shell-memory-leak/ . [22:04] Bashing-om, I guess you can use the link that you want to use, it hurts my eyes trying to read the small print [22:05] Okay, I found that one by Will Cooke but I was looking for one with the link you posted above. [22:06] Wild_Man: I will also look at your new link - the fix does need to be made public . Just. do we add an editorial note to what we have ? [22:07] Wild_Man: My thought is not to take away from the effort that our community provided . [22:07] I think that will be fine, we do not want to diminish the work that will has done [22:09] Wild_Man: A bit out of the norm to editorialize, but is such a thing acceptable practice ? [22:09] From what I have seen everything else is looking good, I am still dealing with a problem user on the forum that is causing trouble on FB also since last night so I am going to be busy with that for some time [22:10] As to what source to use, I think if you first heard of it from phoronix, which I think is the case, it's fair to reference it and mention that it links to the original post. [22:10] I am not sure how sure exactly what you plan to write I would just add the leak is not fixed and include the link and see what others have to say [22:11] scratched not [22:11] I need to put out fires [22:12] Wild_Man: While here ... xfcw has released their updates . Are there constraints on how many aricles are presented .. and are there constraints on the length of the newsletter . [22:13] xfce* [22:13] What would that be btw..? [22:14] krytarik: still looking at new material // so far xfce with 2 releases . [22:15] Bashing-om, no constraints, just it depends on how much help we have [22:16] Wild_Man: Well, I can make the time to add these 3 to UWN . [22:18] If you want to write about updates to individual parts of Xfce, I'd group them under one header at least though. [22:37] krytarik, wrote a summary for Ubuntu Studio and put it as a suggested, I will leave it up to you if you want to use it [22:39] krytarik: Hey. We do like xfce .. will make up a common heading and include in this edition :) [22:40] Yes, we do! [22:42] Bashing-om: On the Gnome memory leak post, please not so much quoting. [22:44] Wild_Man: I have read the OMG article earlier, and I'm not particularly convinced yet the summary captures its content sufficiently. :) [22:45] But it's closer already indeed. [22:46] krytarik: That long quote - IMHO - carries all of the relevant info ... yes ? [22:47] Well, we aren't to quote everything but to summarize. [22:48] The only place we can quote is apparently for pod casts [22:51] Well tbh, that's arguable too - but since it's always been done this way so far.. [22:53] At least I've changed the always same intro who is on the show the week to just a simple list already now. [23:45] https://lists.ubuntu.com/archives/ubuntu-release/2018-April/004438.html [23:45] /!\ /!\ Help test! /!\ /!\ [23:51] tsimonq2, is it worth putting it on fridge? (from memory testing qualifies) [23:51] tsimonq2: Looking ^ . [23:51] guiverc: Yes. [23:52] Interesting: https://insights.ubuntu.com/2018/04/20/design-and-web-team-summary-20-april-2018 . Does it suit for inclusion ? [23:54] i'll put on fridge (hyper-text-free though!) [23:55] (i meant https://lists.ubuntu.com/archives/ubuntu-release/2018-April/004438.html on fridge) [23:55] I think it does that is why I included it [23:56] tsimonq2, adam con.. of ?? it only has his name - Ubuntu Release Team??? [23:57] guiverc: Adam Conrad is on the Ubuntu Release Team, yes. [23:57] use that, or just Ubuntu team (start - Adam Conrad of ...) [23:57] Nah, Ubuntu Release Team is better, imho. :) [23:58] thanks. will use urt [23:58] Cool. :)