[19:11] <lynorian> did we ever fix k3b not being in disco before the huge infrastructure hiccup?
[19:20] <wxl> lynorian: looks like it according to the manifest
[19:48] <lynorian> Ok I need to work on k3b on the manual a ton 
[19:48] <lynorian> got 2 commits done on it
[19:55] <wxl> @tsimonq2: meeting?
 ERR:@tsimonq2IsNotHere
 :P
[20:13] <wxl> well i have no way of knowing XD
[20:13] <wxl> ah the problems with the telegram bridge
 > Last Seen 3 Hours Ago
[20:14] <wxl> at least ya'll know when matrix people are here ;þ
[20:14] <teward> Err: Simon Is Missing
[20:14] <teward> Result: PARTY HARD!
[20:14] <teward> *shot*
 Isn't our meeting normally in 35 minutes or so?
[20:24] <wxl> normally
 Ok. I was thinking it was early.
[20:26] <wxl> i feel like we missed last week's meeting or am i wrong? maybe i missed it
 We probably did.
[20:26] <wxl> i started keeping a worklog and it's a week old
 It was a little hectic (more so than normal).
 Yeah, we missed it
[20:26] <wxl> of course i haven't done much this last week bah :/
 See y'all in a bit when I get home.
[20:28] <wxl> o/
 I forgot you change time, so it is in 20 more minutes?
 Yup
 lies, it's in 15 minutes 😛
 *shot*
 I might not be around in time
 I will be in the subway I think
[21:11] <kc2bez> Sorry I'm late.
 It's all good
 Wanna go first, Dan?
[21:12] <kc2bez> Sure.
[21:12] <kc2bez> I tried to pull as much as I could from the google cache pages to reconstruct the phab tasks and wiki.
[21:13] <kc2bez> I still have the tar files if we need
[21:14] <kc2bez> That is pretty much it from me I think.
[21:14] <wxl> hey a thought about that..... maybe we should make a coordinated effort to get everything back up?
[21:14] <wxl> or work on a more programmatic solution?
[21:15] <kc2bez> What ever you suggest, I am all ears. I was just trying to save it before we lost it.
[21:16] <wxl> and dan, seriously, that is the most awesome thing anyone could have done
[21:16] <kc2bez> I wasn't able to get every task but I think all the wiki was there.
[21:16] <wxl> so my thoughts: either go the cheap route and we just split it up, or we actually take the time to maybe look at what posting apis may or may not exist for phabricator and try to figure out a programmatic solution. might be a lot of parsing
 I don't think the programatic solution would be easy, however, we do need a backup system
 Google cache is in HTML?
[21:18] <kc2bez> yes
[21:19] <wxl> why do you think the programmatic solution would be difficult, @tsimonq2 ?
 Sorry, the programmatic is to load the backup or backups in the future?
[21:19] <wxl> no
[21:20] <wxl> the situation is that we have caches that we can use to restore some of our lost content
[21:20] <wxl> of course to do it we have to take the cache and process it in some way or another to get it posted back on phabricator
 @wxl [<wxl> why do you think the programmatic solution would be difficult, @tsimonq2 ?], Parsing the HTML and turning it into rst
 I don't know if that's exactly easy
[21:21] <kc2bez> old T154 would be a bear for example.
 Mmm, I know nothing from rst, but parsing HTML is easy
[21:22] <kc2bez> I also don't know how important it is to have the task numbers match is.
 In php simplehtmldom is very easy to use
[21:23] <kc2bez> too many is's there.
[21:23] <wxl> right, there's probably libraries we could use, even to convert back into rst
[21:23] <lynorian> pandoc does lots of converting I would check there
 Every webscrapping tool handles html
[21:24] <wxl> do you want to see if you can't come up with a solution @HMollerCl? i suggest looking into it generally/casually. don't spend a lot of time on it. if we can't get an easy answer, let's just split up the content and do it manually
[21:24] <kc2bez> I agree with wxl
 Ok
[21:26] <wxl> thank you
[21:26] <wxl> and since dan is done... and i've got your attention, you've got anything @HMollerCl?
 Has anyone look into the DOM of those html?
[21:28] <wxl> i think the only thing that's been done is that @tsimonq2 has been putting some of them back up manually
 Not much, there are still things I don't understand why icons that where white now are dark (about lxqt, nm-tray, among others)
 @wxl [<wxl> i think the only thing that's been done is that @tsimonq2 has been putting …], Yeah
 And I don't understand why the software - properties - qt - drivers. Desktop doesn't appear
[21:29] <lynorian> well pandoc supports html input
 Need to check those
 Pandoc?
[21:29] <wxl> python
[21:29] <wxl> https://pandoc.org/
 I have to look at the backup
[21:30] <wxl> oh whoa i'm wrong
 And see how is the dom
[21:30] <wxl> i always thought pandoc was python. it's haskell
 Haskell?
[21:30] <wxl> there is a library though https://pypi.org/project/pypandoc/
[21:31] <lynorian> even better is in repos
[21:31] <wxl> haskell is a super rad purely functional programming language
 @HMollerCl [And I don't understand why the software - properties - qt - drivers. Desktop doe …], In the menu?
 @kc2bez [In the menu?], Yes
 Preferences —> Software sources
[21:33] <lynorian> I think it was not is cosmic but is in disco
 @kc2bez [Preferences —> Software sources], Yes, but it should be another. Desktop that goes directly to tab 4
 Oh, I gotcha now.
[21:34] <wxl> i'm confused about what ya'll are talking about
[21:34] <wxl> i guess a bug/task would be a good place to start :)
 Wxl: Software-properties-qt
 I added 2. Desktop to the menu, only 1 appear
 T144
[21:35] <wxl> oh
 Anyway @kc2bez where can I see those html?
 Sure, I sent the link to the tar in the members chat but I can PM you.
 And I would need the rst info to know in what I need to transform the html
 Where can I get the rst info?
[21:38] <wxl> the desktop for software sources seems to just lxqt-sudo software-properties-qt.. is that right?
[21:38] <wxl> reStructured Text
 @wxl [<wxl> the desktop for software sources seems to just lxqt-sudo software-properti …], That's one, but should. Be another
[21:39] <wxl> http://docutils.sourceforge.net/rst.html
 @wxl [<wxl> reStructured Text], Yes, but how it should be loaded into phab
 Task, details, comments, etc...
[21:40] <wxl> THAT i don't know
[21:40] <wxl> looking at whether or not phabricator has a posting api will be the key
 @wxl [<wxl> looking at whether or not phabricator has a posting api will be the key], That's the main issue
[21:41] <wxl> yes
 OK, will look at it
 That will be on my side
 (I have to take a bike now)
 Thanks Hans.
 Thanks!
[21:43] <wxl> bai
[21:43] <wxl> ok who's next?
 Nothing for me except recovering from data loss
[21:44] <lynorian> I have not gone yet 
[21:44] <wxl> that's big stuff. thanks for that.
[21:44] <lynorian> Yes thanks for getting stuff backup tsimonq2
[21:44] <wxl> one quick thing, though.... what IS our backup plan?
 No problem, it's been a draining week and I'm about to go AFK for a few hours to get some fresh air and unwind
[21:47] <wxl> @tsimonq2: you see my question?
 Which?
[21:47] <wxl> one quick thing, though.... what IS our backup plan?
[21:49] <wxl> maybe i have to hlight you to get an answer? XD
[21:49] <wxl> @tsimonq2 one quick thing, though.... what IS our backup plan?
 Sorry
 I'll let @teward001 elaborate on that
 He has a plan, for sure
[21:51] <wxl> ok
[21:52] <wxl> in that case, carry on, my wayward son. there'll be peace when you are done.
[21:53] <wxl> @lynorian: you want next?
[21:53] <lynorian> yes
[21:53] <lynorian> I have set up 2fa now
[21:54] <lynorian> I also did lots of manual stuff major improvements of kde partition manager and qps
[21:54] <wxl> ooh qps
[21:55] <lynorian> I also have kept on polishing many other applicatoins like featherpad and qterminal
 Yeah, cool!
[21:55] <wxl> qool you mean
 Right!
[21:56] <lynorian> I also added build dependencies to the README for stuff needed to make a pdf
[21:57] <wxl> great!!!!
[21:57] <lynorian> which I still have not figured out the chapter numbering
[21:57] <lynorian> I polished a ton of lxqt-panel 
[21:58] <lynorian> polished up muon package manager
[21:58] <lynorian> I did a ton of polishing last week
[21:59] <wxl> you are amazing, lynorian 
 Indeed.
[21:59] <lynorian> lots of the prefrences for lxqt
[21:59] <lynorian> I may need to get mulitple version built as I have not started on new stuff for 19.04 though
[22:00] <lynorian> while not confusing 18.10 users
[22:00] <lynorian> then the whole data loss happened
[22:00] <lynorian> and today I am working on k3b more
[22:02] <lynorian> that is it for me
[22:02] <wxl> ok thanks again!
[22:02] <wxl> anyone else left or should i go?
[22:03] <lynorian> I don't think anyone else is here
 I think it is you wxl.
[22:04] <wxl> ok i only really have stuff from the week before the infrastructure loss
[22:04] <wxl>  * Could not reproduce bug 1819009 on real hardware or VM (thanks Chris, Dan, Thomas)
[22:04] <wxl>  * Triaged bug 1804554 - was expired (can't reproduce on VM) but reproducible on real hardware. Still, it's for pure Openbox, so low (thanks Chris, Dan, Hans)
[22:04] <wxl>  * Triaged bug 1819322 - fixed.
[22:04] <wxl>  * Tried to figure out why ISOs weren't uploading due to a Trusty ISO missing from the manifest. Turns out someone archived .5 but didn't remove it, so it only affected some flavors.
[22:04] <wxl>  * Worked to further confirm bug 1797665 (thanks Dan, Thomas)
[22:04] <wxl> jeez what's up with the bot?
[22:05] <wxl> there it goes
[22:05] <kc2bez> The bridge was slow too.
[22:06] <wxl> there's also someone else who has popped up on bug 1782984 and i need to get them to further confirm, but i'm still convinced it's a gtk2 bug.. which makes me want to not even bother because LXDE is probably never going to get gtk3 compliant.. at least not before the next api breaking gtk update comes uot XD
 @wxl [<wxl> in that case, carry on, my wayward son. there'll be peace when you are don …], Thanks dude
[22:07] <wxl> incidentially the bug has kind of become a great way to promote LXQt X'''D
[22:07] <wxl> and that's about it for me
[22:08] <kc2bez> Thanks for everything wxl
[22:08] <wxl> i don't want to say anything due to fear of jinxing but i should have some free time soon so should see a little more from me
 @wxl [<wxl> incidentially the bug has kind of become a great way to promote LXQt X'''D], Actually that's one of the things why I was interested in 18.10 at the beginning
[22:09] <wxl> @HMollerCl as i said on the bug, trying to make it GTK3 compliant is essentially what compelled PCMan to do a Qt port because he found that compared to GTK3, Qt was actually better at resource usage.. so this is an important thing to remember when people complain about Qt versus GTK2. 
 There was a question in the Spanish group about Wayland in lubuntu. Are there answers?
[23:10] <guiverc> apologies to everyone, I just realized it's friday.. i didn't have anything to say anyway, but sorry for my belated..
[23:20] <wxl> @HMollerCl https://github.com/lxqt/lxqt/issues/10
 wxl: long thread
[23:22] <wxl> guiverc: no prob. i know you've been doing bug stuff and it's been appreciated.
[23:22] <wxl> @HMollerCl indeed
 https://secure.phabricator.com/book/phabricator/article/conduit_edit/
 there is an api
[23:23] <wxl> DrewRWx: do you have any insight on lxqt/wayland?
[23:25] <wxl> @HMollerCl that's a good sign then! 
 tasks seems more doable
 in the wiki I haven't found a concrete structure that would be easy to parse all of them
[23:38] <wxl> well 50% is better than 0
 https://github.com/enckse/phabricator-tools  this might be usefull for backups
[23:47] <wxl> ^^^ @teward001