 The issue is making a vm on the server and the set up the domain unless we just host the file and link to it.
[02:20] <valorie> @ahoneybun -- I don't know much about that stuff but it should be possible
 @RikMills, KCI is a critical component, and we need a plan to update, maintain, and document it. I too am a little scared, not of the system or Jenkins, but the packaging scripts and tooling. I'd like to pitch in to a team to help get it sorted 😁
[11:27] <yofel> you are rightfully scared of the tooling FWIW. Though I'm more annoyed about docker there than the actual ruby code. That is decent - we just have 0 active developers that know ruby, which is the biggest issue.
[11:27] <yofel> The jenkins base tooling is fairly trivial. The only things you need to set up on the hosts by hand are those lock services for git and docker, and jenkins master has some additional setup for hosting the images and stuff like that
[11:30] <yofel> I'm must worried because I pay little attention to it lately, and we have passwordless PGP keys lying on those machines. So while incredibly unlikely, one hijacked system would technically mean reviewing all git histories for malicious commits
[11:30] <yofel> *just worried
 Council, I think in view of comments from Yofel we need to try to organise a   time when we can group up and figure out a plan, thoughts ?
[15:16] <yofel> it would be good to have a plan for jenkins maintenance at least. The tooling itself is an issue, but it works fine without touching unless something changes in the packaging, which doesn't seem to have been the case so far. Or is there something?
[15:24] <RikMills> yofel: should be ok AFAIK. to be honest, I have just put off doing updating. then it got to being a big big update!
[15:25] <RikMills> not really that scared of it, but if an update did break something, I may get stuck fixing it is all
[15:33] <yofel> well, true that. I did updates on swy-01 today and promptly had to fix docker which refused to start up afterwards.
[15:33] <yofel> I don't really remember why I postponed the release upgrade on master. Maybe because I had bad experiences with upgrades on RAID setups.
[15:34] <yofel> Or maybe I just ran out of time after setting up the docker storage layer again from scratch
[15:37] <RikMills> on a slightly side topic, I think now release is over, we should really do a blog post thanking linode for another year. explaining how and why their server helped us get 19.10 done. @ahoneybun valorie @Sick_Rimmit et al?
 Agreed. Don't we have Bytemark too?
 Yeah, Not sure whether to lump both in to one that is all
 Yes we do have Bytemark too.
 I'll write a draft 😃
 Anyone know what we use cms2cms for ?
 Nope
[17:48] <yofel> was that for the old cms migration? (drupal > wp)
 Ah ha OK That's good enough info thanks
[17:49] <RikMills> before my time
 OK, There is an article in drafts, that probably needs a little @Valoriez love to make sure its on point on grammatically sensible. Perhaps a little @ahoneybun magic, with a Kubuntu / Konqi graphic 😉
 I think we can (a) add the logos and links to that? (b) explain a bit more what the servers give us? not big technical details, but widen it bit as it is more than just build servers.
 I'll try to come back and have a look where people have got to with it before I go to sleep UK time :)
 Ah well I was planning to make Sponsors a link to the Sponsors page. 😉
 Yeah, but it is impact on the 1st page people hit I was thinking of. People may not click through. So sponsors logos and links on the article would be best?
 For example, if we tweet the link thanking them
 In that case, people who see a logo and a link may investigate. A check the sponsors page link may just not get looked at by most.
 Yes I agree, lets do it. I'll make the amends
 Great
 I would like yto propose that we remove cms2cms as we do not use any services from them ongoing, would that be ok ?
 I propose that, if it is as historical as it seems.....
 Updated draft done with Logo's and links.. Just need a review from the US side and we're good to go 😃
 https://kubuntu.org/wp-admin/post.php?post=4248&action=edit
 kool
[18:43] <valorie> I'll look in a sec
[18:46] <valorie> I'm a bit confused -- we use both bytemark and linode for the same thing?
[18:46] <valorie> ah, ok, I think I understand
 Yes we have Master and Slaves build machines and they're distributed across both hosting providers
[18:49] <valorie> k.
[18:49] <valorie> shall I publish, then we can tweet?
 where did the images and links go?
[18:50] <valorie> wtf, a link just disappeared
[18:50] <valorie> jeeeeez
[18:51] <valorie> I still see the images
[18:51] <valorie> @RikMills if you want to check, I'll log out
[18:51] <valorie> done
[18:51] <valorie> bytemark link disappeared
[18:51] <valorie> good god
 no idea. damn wordpress. back in a min
[18:55] <valorie> I'll start the tweet
 no even going too look until published now :P
 too many cooks!
[18:58] <valorie> not seeing it yet
[18:58] <valorie> gosh I love our new wallpaper on the website
[18:59] <valorie> thank you again @rikmills
 I have logged out as well. please publish if you think it is ok
[19:01] <valorie> I don't see the story at ALL
[19:02] <valorie> there it is
[19:02] <valorie> bytemark link is still missing
[19:02] <valorie> sheesh
[19:03] <valorie> is this it? https://www.bytemark.co/
[19:04] <valorie> oh, this one: https://www.bytemark.co.uk/
[19:06] <valorie> https://kubuntu.org/news/thanks-to-our-sponsors/
[19:11] <valorie> https://kubuntu.org/news/thanks-to-our-sponsors/
 Yay! That looks great
[19:19] <valorie> took all hands on deck
[19:19] <valorie> I think we need to approach Canonical again about the WP
[19:19] <valorie> or just build a site elsewhere
 Oh why ?
[19:20] <valorie> it's extremely out of date
[19:20] <valorie> constant warnings about upgrading
[19:20] <valorie> and I don't believe that we can upgrade ourselves
[19:21] <valorie> up-to-date WP isn't quite so bad I think
 Yes here is why
 You cannot update because WordPress 5.2.4 requires PHP version 5.6.20 or higher. You are running version 5.5.9-1ubuntu4.29.
 The box it's running on needs PHP 5.6
[19:21] <valorie> right
 That's a job for canonicalsysadmins
[19:22]  * yofel tries to remember how many years PHP 5.5 is EOL now and fails
[19:23] <valorie> yes, so I think we need to ask again
[19:23] <valorie> I believe that this "ask" is years old
 It is the admins at Canonical as they only have access to the VM that it is running.
 valorie I can maybe get a WP site up though not sure how I could move it.
 We may end up with issues with the theme on an newer version though. It's kinda OK as we don't have user info or the ISO though the WP.
[20:33] <valorie> yeah
[20:34] <valorie> not move as much as backup the data we have and restore from that backup
[22:18] <keithzg[m]> Going to start my tenure attending to the Kubuntu fediverse account by linking to the 19.10 release announcement :) (Changed the banner accordingly too)
[22:19] <valorie> \o/
[22:22] <valorie> keithzg[m]: it looks a bit cut off
[22:23] <valorie> perhaps shrink a bit and then re-upload?
[22:23] <valorie> for others: discussing https://mastodon.technology/@Kubuntu
[22:25] <keithzg[m]> valorie: Hmm, interesting, for me it looks fine (if a bit small in terms of the text, which makes sense as I just grabbed the current website banner which is designed as a big page banner)
[22:25]  * keithzg[m] uploaded an image: Screenshot_20191018_162411.png (76KB) < https://matrix.org/_matrix/media/r0/download/riot.keithzg.ca/DSHTWaaRogzBtLNfbAzksAoN >
[22:26] <keithzg[m]> Ah, looks like a bit of a different layout when not logged in. That's unfortunate.
[22:28] <valorie> yeah, not logged in
[22:29] <valorie> welp, when @RikMills wakes he can give you access to a shrinkable image I think
[22:31] <keithzg[m]> Yeah, maybe there's a way to thread this needle better. For now I've cropped it in a way that should make it a bit better overall, splitting the difference a bit. A tricky proposition, overall; entirely different display again in the Pleroma frontend, for instance! (Where the text is a bit of an issue since Pleroma overlays the main account details overtop of the account's banner).
[22:32] <valorie> ah
[22:32] <valorie> I just cropped for the tweet, too
[22:32] <valorie> that's quick n dirty
[22:32] <valorie> and looks good
[22:33] <keithzg[m]> Yeah, best not to let the perfect be the enemy of the good!
[22:33] <valorie> indeed, and that is better
[22:33] <valorie> thank you
[22:33] <keithzg[m]> :)
[22:35] <valorie> https://twitter.com/kubuntu/status/1185271978866774016 is the tweet to which I refer
[22:35] <valorie> courtesy of spectacle
[22:36] <keithzg[m]> I also used a KDE app to do my quick crop, Gwenview in my case :)
[22:39] <valorie> :-)
 It looks great now.
 keithzg can you link to the new post as well?
 God I need to my butt in gear for the 20.04 release when it comes to the docs.
[23:03] <valorie> if we do zfs there will be some writing needed
[23:03] <valorie> not much but screenies for plasma 5.17
 So I released the 19.04 docs on the site yesterday lol.
[23:03] <valorie> but it would def. be good to have a better website and the docs online
[23:03] <valorie> ha
[23:04] <valorie> really not many changes 19,04 > 19.10
[23:04] <valorie> but plasma does look different
 I'll see what I can do for 19.10 and start the branch for 20.04.
 Not this weekend since my dad is in town but next weekend.,
[23:07] <valorie> oh nice
[23:07] <valorie> have a good weekend!
[23:07] <valorie> gotta get my flu shot this weekend
[23:07] <valorie> grocery store pharmacy was out of the senior shot yesterday
[23:13] <keithzg[m]> @ahoneybun: I don't see any Fediverse accounts for any of the three sponsors (which is fair enough!), so just went with a simple link post: https://mastodon.technology/@Kubuntu/102985914023817036
 That's good. Thank you.