[00:59] <Bashing-om> Michael Larabel is some kind of prolifferant . Getting boreing " Michael Larabel writes " .
[01:01] <krytarik> Could always variate at the verb at least though! :P
[01:52] <Bashing-om> https://www.phoronix.com/scan.php?page=news_item&px=Rise-Tomb-Raider-Linux-Tomorrow is outdated by the former article . remove it ?
[01:56] <Bashing-om> http://news.softpedia.com/news/kde-applications-open-source-software-suite-gets-first-major-release-in-2018-520768.shtml though more detailed is a repeat of the ups Michael Larabel article .
[01:58] <Wild_Man> Bashing-om, by what former article?
[02:04] <Wild_Man> Bashing-om, I realize that link that Tomb Raider has already been released today but I see it as just a way to let people know that it has been released, just my opinion we will see what krytarik thinks and the second link to me in no way just restates that gnome has been released it talks about many apps so, I looked that that before I posted it, I think it is good to keep it again just my opinion I am not an expert at this
[02:17] <Wild_Man> Bashing-om, I have been thinking about the Tomb Raider link since it will be next week before we publish I think you are correct we should remove it, we can probably find an updated one to replace it with
[02:23] <Bashing-om> Wild_Man: Does not this suffuce for Tomb raider "https://www.phoronix.com/scan.php?page=article&item=tomb-raider-20 ' in our summary ?
[02:25] <krytarik> Someone please reword the KDE Applications summary. :P
[02:27] <Wild_Man> Bashing-om, that will do, I looked at the the kde application link again and the writer of that article changed his article from just talking about Dolphin to include all the things in the link you posted so it is a duplicate now but the second link is better I think we should leave that one and remove the first one
[02:28] <krytarik> Or in fact, pick the Softpedia one in favor of that.
[02:28] <Wild_Man> krytarik, that is what I am saying as well, it is better in my opinion
[02:29] <krytarik> Yeah, I've just read your last message. :)
[02:31] <Wild_Man> krytarik, I am curious do it show me logged into gdoc? I see you and Bashing-om but not myself, I assume that is the way gdoc is supposed to be
[02:31] <Wild_Man> do/does
[02:31] <krytarik> Yeah, one always just sees the other ones.
[02:31] <Wild_Man> ok
[02:33] <Wild_Man> I hope Bashing-om looks in here to see what we said about removing that link because I think he is trying to rewrite the summary, I wonder if I should remove it?
[02:34] <Bashing-om> Wild_Man: Agreed .. to scrap Michael Larabel's article and write up the release article .
[02:34] <krytarik> Yeep! :D
[02:35] <krytarik> Also, the robot summary is both too short and the sentence doesn't really make sense to me at the end.
[02:35] <Wild_Man> krytarik, I am not good at grammar these days, why does not summary need rewritten?
[02:36] <Wild_Man> not/that, I really need to triple check my typing before posting in here
[02:36] <krytarik> Also, keep in mind that this time we'll also try and sling in the other editors - so there will hopefully a bit more review be going on than just us three.
[02:38] <Wild_Man> I hope more summary writers as well but I would hate to leave the summaries until the weekend and be disappointed, so I do not know.
[02:38] <Wild_Man> I only received four replies out of about 30
[02:46] <guiverc> Wild_Man: as someone who wrote to writers regularly after summaries, 4 replies of 30 is actually very good!  Lyz would probably say its an outstanding response!  likewise Simon..
[02:47] <Wild_Man> guiverc, It sure is better then none
[02:48] <guiverc> also I only have 'view mode' to doc, writers will need write access to gdoc too
[02:50] <krytarik> guiverc: If you would like write access to it, PM me your email address and I can add you.
[02:55] <Wild_Man> krytarik, did you look the gdoc down so people can not easily edit it?
[02:56] <guiverc> PM - you're stretching an old guy like me...  (let me know you got it)
[02:57] <krytarik> Wild_Man: We did last we after a lengthy discussion - don't you remember?
[02:57] <krytarik> ..Week.
[02:57] <Wild_Man> lets not talk about getting older guiverc
[02:57] <Wild_Man> I was not sure that it was actually done
[02:58] <Wild_Man> Yes I remember the discussion
[02:59] <Wild_Man> I hope if the summary writers show up to write that they pop in here.
[03:00] <guiverc> Would be nice, but I never saw it  (I didn't do email summaries that long anyway  -- i did ~50 contribs before I actually entered this room anyway
[03:01] <Wild_Man> I am afraid if the come and see they can not write to the gdoc that they will just leave
[03:01] <Wild_Man> the/they
[03:07] <krytarik> Well, I certainly don't want to check every day if anybody has planted an easter egg someplace in it.. :P  Unlike just deleting the whole thing like last week, which is pretty obvious.
[03:08] <krytarik> And e.g. my computer can't really handle the docs' history function at all, so..
[03:09] <Wild_Man> Do you want to add the emails of the people that replied and said they would help? or wait until they show up?
[03:09] <krytarik> If they are Gmail ones, I guess yes.
[03:09] <Wild_Man> they have to be gmail?
[03:10] <krytarik> Yep, or connected to it.
[03:11] <oerheks> oerheks@ubuntu.com was not valid :-(
[03:11] <guiverc> why not just mention in email that they'll need to request-write access (if they don't already have it)... ie. warning & be ready for responses...
[03:12] <guiverc> i noted a 'request write' access on gdoc (alas after I'd mentioned access here)
[03:16] <Wild_Man> guiverc, that is what I was thinking of doing, is editing the email that goes out to the summary writers
[03:17] <guiverc> :)
[04:09] <Bashing-om> We have enough material ? ( still need to populate general) Do we want to write up a success story on the Dell XPS on 18.04 ?
[04:10] <Bashing-om> https://daniel.holba.ch/blog/2018/04/a-month-with-dell-xps-13-9370/
[04:12] <krytarik> General is really only for official community news.
[04:15] <Wild_Man> Bashing-om, we can probably use it but as krytarik said not in General, I am having trouble finding articles to put in this section
[04:15] <Bashing-om> krytarik: Yup, and my official community news sources are skimppy this week :P
[04:16] <krytarik> Iirc it isn't always populated.
[04:17] <Bashing-om> krytarik: Well, yeah .. got nothing to say, best say nothing :)
[04:17] <krytarik> Yuup! :)
[04:22] <krytarik> Bashing-om: As to the above post, maybe replace the literally one-sentence gksu one with it..?
[04:23] <krytarik> Could write about the OMG post on it instead then if you'd like.
[04:24] <krytarik> ..Or that was someplace else.
[04:26] <Bashing-om> krytarik: Might be able to flesh out the gksu issue ,, seen some flack in the channels in that respect .
[04:26] <krytarik> I mean it's kind of important, so we should find some proper post about it.
[04:27] <Bashing-om> krytarik: See what i can find - uncle Google !
[04:27] <krytarik> Yep!  At it too! :P
[04:28] <krytarik> Or just wait two days.. :P
[04:30] <Bashing-om> Saturday will bring it's own problems . let us deal with what is now . gksu !
[04:33] <Wild_Man> the one I posted by Jeremy Bicha has a link to the bug report on how to do it now, he is the dev that removed it
[04:33] <krytarik> Yeah, but no details whatsoever..
[04:36] <krytarik> I mean that's like linking to the bug report directly - except with one more click.
[04:37] <krytarik> http://www.linux-magazin.de/news/ubuntu-18-04-lts-verzichtet-auf-gksu/ - the German one I had in mind there instead btw. :P
[04:38] <krytarik> So I'd say we wait a day at least and see what more pops up.
[04:38] <Bashing-om> krytarik: Yup seen that , points to : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892768 and we can reference the bug to flesh out the summary .
[04:38] <krytarik> That's like writing a post yourself..
[04:39] <Bashing-om> krytarik: Would for sure be stretching the definition of "summary" .
[04:40] <Wild_Man> this is from today https://ubuntuforums.org/showthread.php?t=2389656&highlight=gksusetting it up is a bother
[04:40] <krytarik> Yes...
[04:40] <Bashing-om> krytarik: As An aside, I have no used gksu in ages ... since I seen the man page for ' sudo -H ' .
[04:41] <krytarik> I'll go to bed now, good night folks! :)
[04:41] <krytarik> I have never used 'sudo -H' myself yet tbh.
[04:42] <Wild_Man> Bashing-om, sudo -H no longer works either
[04:43] <Bashing-om> Wild_Man: I still use it here on xubuntu 18.04 .
[04:43] <Wild_Man> I tried earlier on Ubuntu it is a no go
[04:43] <Bashing-om> Wild_Man: Ouch .. lemme test ! updates may have killed it .
[04:44] <krytarik> Who needs root anymore... :D
[04:44] <Wild_Man> I do!
[04:44] <krytarik> Such a stickler to the core..
[04:45] <Wild_Man> Yep!
[04:45] <krytarik> Fwiw, I always use 'sudo -i'.. :P
[04:46] <Bashing-om> Wild_Man: ' sudo -H ' upper case h .. still works for me .
[04:46] <Wild_Man> that is good
[04:47] <Wild_Man> krytarik, sudo -i does work
[04:47] <krytarik> See, I always use the most robust stuff! :P
[04:47] <Bashing-om> Wild_Man: However, I can believe that I must learn policyKit .
[04:48] <Wild_Man> Bashing-om, sudo -H works for me now, I guess 18.04 was acting up earlier
[04:48] <Wild_Man> I tried several times earlier and it did not work
[04:48] <krytarik> "Don't work"... :D
[04:49] <krytarik> Details, dude!
[04:49] <Wild_Man> I use the terminal for almost everything these days
[04:49] <Bashing-om> Wild_Man: Them there Grimlins .. never can tell what they are up to .
[04:49] <krytarik> I got Lynx there.. :P
[04:50] <Wild_Man> indeed
[04:54] <Bashing-om> Wild_Man: Should we stretch "summary" an in the gksu article also give the debian bug report link ?
[04:55] <Wild_Man> Yes I think so
[04:56] <Wild_Man> No, I just remembered that it says no links in the summary its self, you have to add it after the summary
[04:57] <Wild_Man> Bashing-om, ^^
[04:57] <Bashing-om> Wild_Man: Let's see if it flies by a sweep :) // that is waht I meant to ass it after the header's link .
[04:57] <Bashing-om> ass/*add
[04:57] <Wild_Man> ok
[05:06] <Bashing-om> Wild_Man: Like so - have a look - is what I suggest . And rest on it .
[05:11] <Wild_Man> Bashing-om, maybe I am getting to tired, you want me to look at the gksu article right? I do not see the link to the bug report
[05:12] <Wild_Man> Bashing-om, I did add a link under the General Section that I think can stay there
[05:12] <Wild_Man> I think it is time to call it a night
[05:13] <Bashing-om> Wild_Man: I placed it right below the https://jeremy.bicha link .
[05:13] <Wild_Man> maybe I need to refresh the page
[05:15] <Wild_Man> it showed up after refreshing the page, that works for me
[05:16] <Wild_Man> Bashing-om, tomorrow we probably should adjust the summary to say the bug report link is included?
[05:16] <Bashing-om> Wild_Man: So yes .. let's call it a night :)
[05:16] <Wild_Man> Indeed!
[05:16] <Wild_Man> see you tomorrow after I get done at the VA
[05:17] <Wild_Man> Thanks for all the great work!
[05:17] <Bashing-om> Nite nite - do not let the bed bugs bite :P
[05:17] <Wild_Man> Night
[18:40] <Bashing-om> Taking a break from mowing - catch up on where we are for publishing . I see we have added help :)
[18:45] <krytarik> Yes! :)
[19:22] <Bashing-om> At a stopping place, back to mowing . I return here soonest :)
[19:27] <krytarik> Now, wrt this channel's ACL: 1.) Who is Beuno..?  And 2.) I'd like to have op rights too (I'm no Ubuntu member yet still), just in case.. :)
[19:34] <krytarik> (To be clear, particularly for the case where spammers quite literally hit every channel in the Ubuntu namespace, regardless of topic or size - which I've also seen hit this one before.)
[20:21] <Bashing-om> Wild_Man: WB :) .. I am in the midst of mowing .. in and out as I take an opportunity of respite from the mower .
[20:22] <Wild_Man> Bashing-om, Okay did you see my message you in the gdoc?
[20:22] <Bashing-om> Wild_Man: No ..I did not see any in gdoc .. lemme recheck .
[20:24] <Bashing-om> Wild_Man: Uh Huh .. it workie // was of some wonder how to chat there :)
[20:55] <Bashing-om> Gonna go have that reel mower beat up in me a bit more .. back in jusst a few .
[20:57] <Wild_Man> Bashing-om, see you!
[22:13] <Bashing-om> Back .. My attention however is presently in the forum - will check here periodically .
[22:18] <Wild_Man> Bashing-om, okay