User1: abu Ahmad was added by: abu Ahmad
User1: <tsimonq2> Welcome!
-queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Disco Beta] has been marked as ready
User1: <tsimonq2> Chris Guiver is the man!
User1: <kc2bez> Yes he is!
User1: <tsimonq2> I really appreciate the testing :)
User2: He takes testing to another level, it is awesome indeed.
User1: <tsimonq2> For sure
User3: User5 any timetable on when you will be able to get multiple versions of the manual built I have almost finished some of what I think the last things are not documented in 18.10 yet
User1: <tsimonq2> @lynorian [<lynorian> User5 any timetable on when you will be able to get multiple vers â¦], I'll take a look tonight
User1: <tsimonq2> It shouldn't be difficult at all
User3: yeah I know I just don't think I have parts for say how it works on the server
User3: I need to get the software sources upgraded for 19.04 along with other stuff
User1: <tsimonq2> Yeah, just some nginx fun I think
User1: <tsimonq2> @teward001 A single nginx site can have multiple root locations depending on which URL you're visiting, right?
User1: <tsimonq2> So e.g. example.com serves /srv/example.com/foo while example.com/bar serves /srv/example.com/bar
User4: that seems like a good idea.. but how do navigate to the right page? manual.l.m will just have links to the different versions?
User4: this is why i liked the python-based solution that the sphinx folks implemented
User1: <lynorian> wxl I am not quite sure how to do that?
User4: this might be a thing https://robpol86.github.io/sphinxcontrib-versioning/v2.2.1/index.html
User4: OR
User4: it seems read the docs does this automatically. we could publish to there and just have manual.l.m point there
User4: actually that might be the easiest possible solution
User4: you can just connect to a github account or manually import docs from a git repository
User3: wxl that extension doesn't have the bootstrap theme we use
User1: <teward001> @tsimonq2 [@teward001 A single nginx site can have multiple root locations depending on whi â¦], Correct, but whatever is there needs to be aliased to it in order for the URIs to be properly handled
User1: <teward001> so depending on what you're trying to do... things could break ð
User1: <tsimonq2> @wxl [<wxl> it seems read the docs does this automatically. we could publish to there â¦], Does it support Sphinx?
User3: yes just not the bootstrap theme
User1: <tsimonq2> Are we willing to give up the theme?
User1: <lynorian> I can change it easily and you choose that one way back when
User1: <tsimonq2> True
User4: oh @lynorian you'll like the fact they build all the formats by default
User3: wxl building the format actually isn't quite the problem it is the chapter numbering on pdfs
User4: we can install a local instance of rtd hmmmm https://docs.readthedocs.io/en/stable/install.html
User1: <teward001> oh great another thing to deploy >.>
User4: well that's one way we could ensure our theme
User4: redis and elasticsearch are depends
User1: <teward001> redis i understand
User1: <teward001> ES.... eh
User1: <teward001> that's not a tiny thing to deploy that gets huge fast
User4: it's for the search functionality
User4: (and next on obvious statements..)
User5: HEEEEEEEEEEEEEEYA, it's meeting time!
User3: hello tsimonq2
User1: <teward001> do we include getting the infra back up and running a dev task ð
User5: yes @teward001
User5: k
User5: so
User5: I guess lynorian goes first
User5: :)
User6: so I should stick around then :P
User3: ok for the manual I got a lot of work on transmission and K3B on the manual
User5: User6 yes
User3: I did some work on firefox really
User3: I did a tiny bit of working on discover and muon
User4: that's good
User3: I also got some work done on vlc playlists
User4: (an aside: there's a ncurses vlc front end; just run `nvlc`)
User3: yes that is not in the manual yet
User4: i'm not sure it needs to be, per se, but..
User3: yes
User3: I think that is it from me
User5: ok
User5: teward goes next because he needs to catch a commute.
User6: assuming we include getting the core infrastructure back up after the fiasco...
User5: yes
User6: * SSL: Looking into whether it'd be more sane to get a *.lubuntu.me wildcard, but will have to coordinate with Canonical IS as they hold the domain.
User6: * Phabricator:
User6: - Phabricator daemons SystemD-ified for autostartup
User6: - Phab git/SSH daemon SystemD-ified for autostartup
User6: * CI: SSL issues reaching into CI/Lugito/etc., working on investigating syncing the SSL certs around to the containers from the host (with a semi-hackish approach...)
User6: * Security / Updates management: Investigating centralized monitoring/management via Landscape for reasons.
User6: * TODO:
User6: - Discourse
User6: - Automate Lugito startup
User6: Been a bit stretched this week because of my FT jobs :P
User6: </done>
User6: questions before I dart off, ask now.
User5: Thanks teward!
User5: User4 Go, unless someone has questions :)
User3: only thing I notice not being up is irc notifications in lugito
User4: i don't think i have much actually
User5: User3 Yeah.
User4: or perhaps anything except a little conversation :/
User5: No problem wxl :)
User4: done then
User5: Alright, who else is here?
User2: I'm here too, nothing to add.
User5: ok :)
User5: Thanks!
User5: * The Beta is TODAY! Adam is doing it this time, so we have a little bit of breathing room, but it's marked as ready.
User5: * RELEASE BLOCKERS AS OF RIGHT NOW:
User5: - FDE with Calamares on Secure Boot systems. I have a workaround that I need to confirm and test.
User5: - Completion of tests I have in the wiki page below.
User5: * Work on infra recovery as usual. I set up Jenkins again, I'm just waiting on teward to do some work with the SSL certs and we'll be golden. Here's the critical things I see that are left:
User5: - Completely recovering translations.
User5: - Getting our pal Lugito back in here.
User5: - CI, and related bits.
User5: - Lubot in the Council and Members channels.
User5: * I just thought I'd mention that my inspiration for these meetings originally was the Foundations team meetings, and they usually have stuff prepared beforehand and just copy/paste to the channel (like I do). It'd be cool if everyone could do that. It's optional, of course, but it makes this go a lot quicker. :)
User5: * I'm all set for LFNW, and I just need to hear back from Canonical about getting the actual money for my SELF tickets. Still in talks with Altispeed to fund a DebConf trip.
User5: * Canonical has given Lubuntu preliminary clearance to establish an LLC with the Lubuntu name. I'll be seeing a corporate accountant and a business lawyer after tax season to discuss bootstrapping it. Details to come, I'll talk with the council once Lubot is back so wxl doesn't miss anything.
User5: * Closed a few tasks today following uploads I have already done.
User5: * I've written a few bits of documentation, eyes welcome: https://phab.lubuntu.me/w/release-team/schedule/ https://phab.lubuntu.me/w/release-team/testing-checklist/
User5: * Really week overall, but I'm getting back into the swing of it. Weather has been getting much nicer, thankfully.
User5: Done.
User5: Any questions?
User4: what's the secure boot deal?
User3: nice calendar how did you do that?
User5: User4 My (untested!) theory is that we can do a little bit of Calamares hacking to allow for contextual partition layouts. From there, we just set it in the config.
User4: i think it's just a simple table
User5: ^
User5: :)
User3: cool
User4: @User5 did you check with upstream? i could have sworn i saw some rumbling about it in the support channel a while back
User5: User4 Yeah.
User5: crazy_ thinks I'm an idiot, oh well.
User5: What else is new? :P
User4: uh
User4: well perhaps instead of shouting into the channel, maybe ask the folks that will actually listen to you :/
User5: I'll prioritize writing some code myself.
User4: also i note #kubuntu-devel was reporting something similar
User4: perhaps getting them and/or neon to comment on a bug report might help
User4: s/bug report/github issue/
User5: Yep.
User5: I
User5: ugh
User5: I'm >< this close to getting a working staging area for next release.
User5: So if we know Lubuntu 19.04 looks good to go, we can start working on 19.10 via a PPA.
User4: ooooooooooooooooooooooooooooooooooooo
User5: It'll very likely involve bringing back Lubuntu Next.
User4: oh hell no
User5: There's support right in ubuntu-cdimage for PPAs.
User5: User4 How else do you want to build images? XD
User4: i just don't ever want to use that name
User5: Unless teward wants to set something else up... >_>
User5: hahahahaha
User5: ok
User5: User4 Name suggestion then?
User4: lubuntu bleeding edge?
User5: Lubuntu Edge it is
User4: oh great
User4: nwo we're a disabled browser
User5: HAHAHAHA
User5: ok
User5: so
User4: anyways
User5: It has to be Lubuntu ONEWORD I think
User3: not a demon
User5: Lubuntu Canary?
User4: hmmmmmm
User5: I like that
User5: Objections?
User4: 1s
User4: fine
User4: but it's a blue canary or nothing
User5: ok XD
User4: also: any reason why we don't turn that testing checklist into testcases?
User5: No ucarney@example.org.
User4: k.. probably make them more visible
User5: I'm suggesting you do that btw XD
User4: i suspected as such :)
User4: the base testcases need to be rewritten for calamares anyways
User5: Right.
User4: ok so we're done right? XD
User5: I guess XD
User4: k love you bye
User5: <3
User1: <kc2bez> XD
User1: <HMollerCl> Hi!
User1: <tsimonq2> Hey!
User1: <tsimonq2> What's up? :)
User1: <HMollerCl> Sorry I'm late
User7: o/
User1: <HMollerCl> I haven't been able to figure out how to upload the tasks
User1: <HMollerCl> I'm not sure I will have enough time to figure it out
User1: <HMollerCl> I can give the parsed "backup" to someone that can figure that out
User5: ok
User5: I'll do it
User5: User7 heya :)
User5: User7 Thanks for the testing work!
User1: <HMollerCl> @tsimonq2 [<tsimonq2> I'll do it], OK, I will send them to you
User5: Thanks!
User7: tsimonq2, if you have other [easy-ish] monkey-stuff i can do, let me know.. (this applies to others too)
User4: User7 that testing checklist
User4: https://phab.lubuntu.me/w/release-team/testing-checklist/
User5: ^
User7: okay wxl - will work on it (if it was given to me before, sorry I forgot)
User4: User7 not a problem. you're doing amazing work. we are so thankful.
User5: For sure :)
User6: *throws salt at wxl*
 * wxl throws slugs at teward
lubuntu-devel
Ubuntu IRC