#kubuntu-council 2018-01-30
<acheronuk> https://plus.google.com/u/0/+J%C3%B6rgvonFrantzius/posts/HxMMA9aAvPx
<valorie> \o/
#kubuntu-council 2018-01-31
<clivejo> acheronuk: ping
<acheronuk> clivejo: pong
<clivejo> I used to keep in contact with JR regarding the Paypal donation button on the website
<clivejo> would you take this on?
<clivejo> and make sure this is up to date - https://docs.google.com/spreadsheets/d/1Y0g-lWr8QSom6ZbfjgFt0pYRb-930FtO_egC_UhP9WQ/edit#gid=0
<clivejo> The last Paypal withdrawal was 17/2/2016 and there is quite a sizable sum in there
<clivejo> He will send you a screen shot of Paypal account
<acheronuk> clivejo: maybe. can't try to make sense of it today.
<acheronuk> maybe deal with this when he is back from canoeing the nile, or whatever
<clivejo> yeah for some reason submitting my self assessment made me think about it
<clivejo> anyways I'll leave you with it, cheerio
<IrcsomeBot1> <ahoneybun> Quite a bit in there for Kubuntu.
<IrcsomeBot1> <acheronuk> @ahoneybun, I would like to understand how that figure was arrived at. Not that I don't trust it, but you know what I mean.
<IrcsomeBot1> <ahoneybun> Yea I get you. We should find some use for some funds.
<IrcsomeBot1> <ahoneybun> Maybe the devs need a machine to run local builds?
<IrcsomeBot1> <acheronuk> As Launchpad is still ****ed waiting for spectre microcode fixes? LOL
<IrcsomeBot1> <ahoneybun> I know we need to handle the server costs somehow once Linode is over
<IrcsomeBot1> <tsimonq2> @ahoneybun, I could see it being used in the case where Ubuntu doesn't approve funding requests to go to conferences
<IrcsomeBot1> <ahoneybun> well we can't do what we do without servers
<IrcsomeBot1> <ahoneybun> I think that should be top usecase for the funds.
<IrcsomeBot1> <tsimonq2> Right
<IrcsomeBot1> <tsimonq2> But we already have those...
<IrcsomeBot1> <acheronuk> @ahoneybun, define local builds?
<IrcsomeBot1> <ahoneybun> @tsimonq2, but Linode is not renewing next year.
<IrcsomeBot1> <ahoneybun> @acheronuk, image a machine that you can build all of the packages on
<IrcsomeBot1> <acheronuk> I can build them all here. Just would take for *ever*
<IrcsomeBot1> <acheronuk> so you mean a mini build farm or do builder setup?
<yofel> would be something worth thinking about - we just need to decide how it should look like: CI exclusive like neon, or using a dediated scheduler (which would need some kind of API to jenkins) that allowes manual uploads
<IrcsomeBot1> <acheronuk> at the moment with launchpad, I am about ready to just give up on 18.04. it's just useless, and canonical don't seem to be able to find their backsides with their hands to fix the capacity problems
<yofel> As for server costs, I would delete linode once it runs out, there are more cost efficient options - either dedicated servers or cheaper cloud providers like scaleway
<IrcsomeBot1> <acheronuk> only way I got stuff done lately is to build in the ninja ppa to get buiold priority, then copy to a normal ppa to QA
<IrcsomeBot1> <acheronuk> yeah. linode is nice, but seems paying over the odds if we have to pay the bill. like paying for a premium brand, when actually the value one is 95% as good
<yofel> to be honest, if anything the build farm has regressed to ~2010 levels. Back then - when the PPA builders were seperate from the archive ones - build queues of 2 days were not really uncommon
<yofel> the private PPA was the only reason we got anything done
<yofel> as for linode: this is how much we're actually using it: https://kyofel.de/owncloud/index.php/s/r90ABiDbFJgJ9Wp
<yofel> i.e. 99.15% idle
<yofel> when the CI is running properly it's better, but still around 95%
<IrcsomeBot1> <acheronuk> we could use it more, but I either dont know how, or am reluctant to spend time setting things up on a service we know we are going to lose
<IrcsomeBot1> <ahoneybun> I'm up for going to a different hosting
<IrcsomeBot1> <ahoneybun> but it's something we should look at before the Linode runs out not when it does.
<IrcsomeBot1> <tsimonq2> So I have an interesting offer
<IrcsomeBot1> <tsimonq2> Altispeed, my employer, hosts some Lubuntu infrastructure at the moment
<IrcsomeBot1> <tsimonq2> He's asked me to let him know if I need any more servers for anything else because apparently it's been hugely successful for marketing
<IrcsomeBot1> <tsimonq2> He's willing to offer a server of any size for the Kubuntu team with no expiration date on how long we can have it given that we put Altispeed's name somewhere on the site (maybe the footer)
<IrcsomeBot1> <tsimonq2> ("he" being @Kernellinux)
<IrcsomeBot1> <tsimonq2> @ahoneybun @acheronuk Interested?
<IrcsomeBot1> <ahoneybun> I don't see a problem we do it for Linode now.
<IrcsomeBot1> <tsimonq2> Alright.
<acheronuk> [16:57] <acheronuk> any eta on getting capacity back on the build farm. I am guessing not, but ask on the off chance
<acheronuk> [17:00] * mpt (~mpt@canonical/mpt) has joined
<acheronuk> [17:14] <cjwatson> The ball remains in the CPU vendors' courts.
<acheronuk> at this point I am serious tempted to just go over the road and just do Neon fixes until May
<valorie> yikes
<valorie> is it very difficult to get our linode to do what we now rely on the builders to do?
<valorie> or just skip directly to scaleway, or take Altispeed up on their offer?
<valorie> I guess that question is both for yofel and acheronuk
<valorie> and maybe tsimonq2
<valorie> tsimonq2: could you get a firm offer from your boss and send it to the list?
<tsimonq2> valorie: It's the other way around I think; Altispeed will provide whatever Kubuntu needs/
<valorie> ok, but getting that offer to the list would be good
<valorie> because I assume a short discussion would get us to a "we need this, this and this, as soon as possible"
<tsimonq2> Alright.
<valorie> so we can start setting stuff up
<valorie> I know that neon does a lot of stuff with droplets
<tsimonq2> valorie: For what it's worth, Launchpad's builders can't be replaced by our own infra. Maybe for KCI we could make it work, but ultimately we need it for archive stuff.
<valorie> but the tooling to do all that seems very involved
<valorie> they can't?
<tsimonq2> No.
<valorie> splain why
<valorie> I mean I understand they they need to build things on their own servers
<tsimonq2> Right
<tsimonq2> That's it, for the archive.
<valorie> but we could certainly build ourselves first and resolve problems, right?
<valorie> which is the CI
<valorie> build problems and autotest issues
<tsimonq2> We could set up our own infra solely for KCI but I'm unsure the time spent is worth the gain.
<valorie> where do we run KCI now?
<tsimonq2> On Blue Systems' infra iirc.
<valorie> ah
<valorie> what do we do on linode now?
<tsimonq2> iirc just workspaces for developers
<valorie> I see
<valorie> so, what Santa_ is doing on his uni server is more what I was thinking of, I guess?
<valorie> building and doing the auto-tests
<tsimonq2> Yeah, we could do that.
<acheronuk> santa doesn't seem to be doing anything now
<valorie> it just seems to me that if we could feed our stuff *somewhere* and move it along
<valorie> instead of waitingwaitingwaiting
<valorie> this wouldn't be so frustrating
<acheronuk> night all
<tsimonq2> Honestly Valorie, I see that as the only option at the moment.
<tsimonq2> acheronuk: o/
<tsimonq2> We have to wait for this thing to be patched.
<tsimonq2> The build farm is only crippled, but it's superslow.
<valorie> if our stuff was already fixed before hitting their builders, perhaps we would have a better reputation with the release team
<tsimonq2> Which is why I am starting to spark discussions regarding giving everyone in ~ubuntu-dev Bileto access.
<valorie> what does that access allow?
<acheronuk> autotests
<valorie> niters acheronuk
<tsimonq2> It allows access to CI Train PPAs which have a full suite of automated tests and everything that would be ran if uploaded directly to the archive.
<acheronuk> I will go in a sec, lol
<valorie> ah
<tsimonq2> Once everything is tested, you press one button and sources + binaries are copied to the archive.
<valorie> that would be awesome
<valorie> why don't we have access to that NOW?
<acheronuk> and then all the tests that did pass, fail
<acheronuk> :P
<tsimonq2> I've convinced them to give me access to do Qt transitions but other than that, only Core Developers have access to it otherwise.
<valorie> acheronuk: lol
<tsimonq2> acheronuk: hah
<valorie> hm
<acheronuk> because someone uploaded broken stuff in the meantime
<valorie> so I guess riddell always had access to that
<valorie> and since he was an AA, everything was painless
<tsimonq2> Right.
 * valorie shakes her fist at the universe
<valorie> so unfair
<valorie> ah well
 * acheronuk shakes fist at main and multiverse
<tsimonq2> I totally blame Intel for this (excuse my french) bullshit.
<tsimonq2> acheronuk: hahahahahaha
<acheronuk> but mostly universe
<tsimonq2> valorie: Had this not been disclosed early, things would be fine.
<valorie> yes
<valorie> whoever let that out.....
<valorie> grrrrr
<valorie> well, Intel scientists were monumentally arrogant
<tsimonq2> I agree.
<acheronuk> tsimonq2: doubt that would have got the microcode updates out by now, unless those spectre vulns would have still been under wraps
<tsimonq2> acheronuk: They released it a week early.
<tsimonq2> They expected to have that long.
<valorie> sort of a double-edged sword though
<tsimonq2> Right.
<valorie> the builders wouldn't have been shut down
<valorie> and perhaps those vulns would have been baked in for even longer
<acheronuk> tsimonq2: yes, and nearly a moth later, things are still borked, and would have been on that basis, even it not leaked
<acheronuk> s/moth/month
<tsimonq2> Right.
<tsimonq2> All of this is frustrating.
<tsimonq2> I'm Frustrated.
<valorie> monunmentally
<acheronuk> initial crap was the early release, but now there is not that excuse
<tsimonq2> Right.
<valorie> amen
<tsimonq2> This release cycle...
<tsimonq2> like holy shite
<tsimonq2> :/
<valorie> I have no clue why they don't replace the crippled machines
<tsimonq2> It doesn't work like that.
<acheronuk> I though it was bad last year waiting for gpgme to get fixed!
<valorie> jesus, canonical is in the BUSINESS of providing that stuff
<tsimonq2> valorie: Canonical has said multiple times, the machines that are open for building already have patches. Blame Intel and AMD for taking so long.
<tsimonq2> They've done what they can.
<valorie> no
<tsimonq2> We should stop giving them a hard time about it.
<tsimonq2> They've done what they can.
<valorie> they could provide more patched machines
<valorie> that's what they DO
<tsimonq2> It doesn't work like that; they already have a set of machines, and they have a limited budget to that department.
<tsimonq2> I've had these conversations.
<tsimonq2> I've asked the exact same things.
<valorie> understood
<acheronuk> I've not heard of any other distro being so crippled
<tsimonq2> There's nothing they can do at the moment.
<tsimonq2> acheronuk: They have a different build infrastructure.
<acheronuk> OBS seems to being going as normal
<valorie> there's nothing they WILL do at the moment
<valorie> I get that
<valorie> that's why it's so frustrating
<acheronuk> seems a case of sit on their hands and wait for someone else to fix it
<valorie> yes
<acheronuk> I am probbaly being mean, but I'm starting to not care
<valorie> suse and redhat are not suffering that I've heard
<valorie> or for that matter, microsoft or apple
<valorie> or google, or amazon
 * acheronuk wonders if we could submit our stuff to OBS. lol
<valorie> we can
<tsimonq2> :/
<valorie> probably more trouble than it's worth
<tsimonq2> Y'all are frustrating me.
<acheronuk> that would be funny. and very sad
<valorie> but anybody can
<acheronuk> tsimonq2: join the club
<valorie> tsimonq2: this is the universe we live in, and those are the rules
<valorie> but the next universe over doesn't seem to have quite the same limitations
<valorie> also I missed seeing the lunar eclipse because CLOUDS
<acheronuk> +++Divide By Cucumber Error. Please Reinstall Universe And Reboot +++
<acheronuk> ^^^ Pratchett
<valorie> rofl
<tsimonq2> There's nothing we can do. I'm moving on with my life, and I'll come back if there's any hope.
<valorie> RIP Pratchett!
<tsimonq2> I've accepted this,
<valorie> oh, me too
<valorie> I hope we can fix some papercuts while we're waiting
<tsimonq2> E: No time
<acheronuk> I've been tinkering with Neon the last few weeks, and honestly think maybe I can be more productive over there.
<acheronuk> canonical seems to be on a suicide mission with their attitute
<acheronuk> ubuntu itself may scrape by, but screw the rest
<acheronuk> ok. going now. lol
<valorie> bye acheronuk
<valorie> hope you are feeling more hopeful about kubuntu later
<acheronuk> I hope so too
#kubuntu-council 2018-02-01
<yofel> 'couple corrections
<yofel> The KCI master server is hosted on the bytemark server today which was arranged by Rick
<yofel> Linode is used for some dev builds, and hosts one of the KCI slaves - and really does most of the jobs for the CI
<yofel> I have pondered setting up our own builds, but as I'm not too happy with any existent replacement that currently exists
<yofel> - Neon does it's own builds, but has no dedicated build scheduler and just uses jenkins. Meaning nobody can do any manual uploads (which is both good and bad). Aptly is something I would use for repository management as well though
<yofel> - I don't know of any debian-esque build schedulers that have any kind of API that jenkins could talk to. At least I know that wanna-build and debile don't have any (i.e. we need to write that ourselves, which would be a doable amount of work)
<yofel> - OBS as hosted by OpenSuse allowes builds for Ubuntu, but not the development release when I checked last, so is kind of useless for our use case.
<yofel> you *can* host it yourself though, so someone might want to take a look at that
<yofel> and IIRC ximion was working on some kind of build system himself, though I haven't heard any news regarding that, so maybe he abandoned it
<yofel> as Rik said, there *are* solutions to our problems, but I'm not conviced that the amount of effort we have to put in is worth it in the end
<yofel> and any more infrastructure we create for ourselves increases the maintenance costs
<acheronuk> yeah, thanks for all that yofel. I agree. if LP gets back to normal, while not perfect, that is a no-brainer to use
<valorie> acheronuk: will the adjustments that wgrant offered help enough, do you think?
<valorie> thanks for the clarification, yofel
<ahoneybun> thanks yofel , also good to see you around again!
<valorie> yofel: I think we all agonized about some of these choices before, when it looked like we might get not be able to be Kubuntu any more
<valorie> we thought about new names, etc.
<valorie> I would not like to see us independent, annoying as Ubuntu/Canonical can be, because we simply are not big enough to do what needs doing by ourselves
<tsimonq2> We ARE Ubuntu too.
<valorie> we are
<tsimonq2> So we're calling ourselves annoying? :D
<valorie> well, I know I can be
<valorie> lol
<wxl> in your case it makes sense @tsimonq2
<tsimonq2> Same here, lol
<valorie> never YOU tsimonq2
<valorie> lol
<tsimonq2> wxl: XD
<valorie> neon sort of found a crack they could settle into and that's fine with me
<valorie> I think continuing to work with them helps everybody
<tsimonq2> "a crack they could settle into"
<tsimonq2> lol no :)
<valorie> between Ubuntu and KDE i mean
<tsimonq2> mmmmmmmmmmmmmmmmmmmmmmmmmmmmh
<tsimonq2> idk
<valorie> I would rather see us all still together, but neon is providing a service to plasma developers in particular
<valorie> and that ends up helping everybody
<valorie> all of desktop and mobile linux at least
<valorie> sec
<valorie> maybe not a crack -- a niche
#kubuntu-council 2018-02-02
<yofel> ravine? >.>
<clivejo> could someone with admin priv please do https://kci.pangea.pub//user/clivejo/delete
<clivejo> can't delete self for some reason :/
<IrcsomeBot1> <ahoneybun> should be fixed clivejo.
<clivejo> @ahoneybun thanks :)
<IrcsomeBot1> <ahoneybun> your welcome. ;)
<clivejo> @ahoneybun don't happen to know where I saved my private keys?!
<IrcsomeBot1> <ahoneybun> on the server?
<clivejo> nah
<clivejo> trying to revoke my Kubuntu.org certs, but can't find the key to one of them
<clivejo> amazing how quick I forget stuff when not using it
 * clivejo feels like Dory
<ahoneybun> yea I'm not sure
<valorie> yofel: ha
#kubuntu-council 2018-02-03
<IrcsomeBot1> <acheronuk> Hope I'm not coming acrross too grumpy on that font size thing, but I REEEEEEEEEEEEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAAAALLLLLY hate that change!
<IrcsomeBot1> <acheronuk> If I said what I really think of it, I think that would break all the CoC. ð³
<IrcsomeBot1> <acheronuk> https://twitter.com/MariusNestor/status/958434063127326727
<IrcsomeBot1> <acheronuk> May have to download that and have a look!
<valorie> acheronuk: not kicking it up one?
<valorie> I'd better read before asking
<valorie> seriously damp outside, gosh
#kubuntu-council 2020-01-27
<IrcsomeBot2> <Sick_Rimmit> (Document) https://irc-attachments.kde.org/9wr9aJ59/file_22747.mp4
<IrcsomeBot2> <Sick_Rimmit> Let's do a Kubuntu Focus Birthday Party on Saturday 1st February 2020.
<IrcsomeBot2> <Sick_Rimmit> Kubuntu Focus Birthday Party Ã¢â¬Â¦ All times are UTC Ã¢â¬Â¦ 11:00 - 12:00 Introductions and Welcomes as people arrive ( Drive up activity on Social Media etc.. ) Ã¢â¬Â¦ 12:00 - 13:00 GoBot Croquet ( Round 1 of up to 3 heats ) Ã¢â¬Â¦ 13:00 - 14:00 Exploring Steam, on the Kubuntu Focus Ã¢â¬Â¦ 14:00 - 15:00 The Kubuntu Podcast ( The podcast team reunite to do a special show ) Ã¢â¬Â¦ 15:00 - 16:00 GoBot Croquet ( Round 2 of up to 3 heats ) Ã¢â¬
<IrcsomeBot2> 17:00 Guests, and Revellers community talk â¦ 17:00 - 18:00 Interview with the Kubuntu Focus Team ( including Q&A ) â¦ 18:00 - 19:00 Gobot Croquet ( Round 3 of up to 3 heats ) â¦ 19:00 - 20:00 Pizza Party Time ( Bring your own Pizza ) â¦ 20:00 - 21:00 News Review ( We discuss the news and reviews around the Kubuntu Focus ) â¦ 22:00 - 23:00 GoBot Croquet the Final & Prize giving â¦ 23:00 Party closes.
<IrcsomeBot2> <ahoneybun> @Sick_Rimmit So I'll be getting my first tattoo (or should be if everything goes right) on that date lol.
<IrcsomeBot2> <ahoneybun> So was I in the reunion or just as a normal person?
<IrcsomeBot2> <Sick_Rimmit> In the Reunion
<IrcsomeBot2> <Sick_Rimmit> Maybe if we time it right, you can show off your tattoo, depending on where you had it done ?
<IrcsomeBot2> <ahoneybun> @Sick_Rimmit my main question is am I in the reunion?
<IrcsomeBot2> <Sick_Rimmit> Well we would like you to be if you can
<IrcsomeBot2> <Sick_Rimmit> Hey @ahoneybun We've discussed the Party, and we now think that this should be pushed back to Saturday 25th April, and lined up with the Release of 20.04 at the same time
<valorie> @ahoneybun what tat are you gonna get?
<valorie> Saturday the 25th I'll be at LFNW
<valorie> hmmm, first time that that and release have coincided
<IrcsomeBot2> <Sick_Rimmit> Oooo how cool would it be if we could beam you into the party for an Interview ð
<valorie> at least in the years I've been going
<valorie> well, I'll have a browser
<valorie> not usually IRC
<IrcsomeBot2> <ahoneybun> @Sick_Rimmit, alrightly.
<IrcsomeBot2> <ahoneybun> @valorie, That'll be a surprise for LFNW.
<valorie> :-)
#kubuntu-council 2020-01-28
<IrcsomeBot2> <Sick_Rimmit> Hey @Valoriez would you be willing to jump an a call with us in BigBlueButton to provide us with a show report ? That would be so cool to have. If so what time UTC could you do it ?
<IrcsomeBot2> <Sick_Rimmit> From LFNW that is
<valorie> oh gosh
<valorie> it's after midnight here now
<valorie> can I tell you tomorrow?
<valorie> I can say yes that would be fun!
<IrcsomeBot2> <Sick_Rimmit> Oh so sorry I pinged you, night night xxx
<valorie> lol
<valorie> no problem
<IrcsomeBot2> <Sick_Rimmit> https://kubuntu.org/event/kubuntu-20-04-release-party/
<IrcsomeBot2> <ahoneybun> @Sick_Rimmit can't change the date now!
<IrcsomeBot2> <Sick_Rimmit> No, that's a commitment
<valorie> @Sck_Rimmit please add UTC after the time on the announcement
<IrcsomeBot2> <Sick_Rimmit> 10:4 will do that ð
<valorie> :-)
<IrcsomeBot2> <Sick_Rimmit> Hmmm the event Calendar on our website, offers UTC but the only selectable entry in the UTC category is a 'blank'
<IrcsomeBot2> <Sick_Rimmit> I have added a *bold* line that all times are UTC, hopefully that's better than nothing
<valorie> sounds like 16:00 would be best for me to hail in, but I think the hall doesn't open until 17:00
<valorie> so maybe during the pizza party would be better
<valorie> so 19-20:00 I'll log in, if not just listening before that
<valorie> ok, it's on my calendar
