• sent

Adriaan de Groot
groot@kde.org

Thanks for looking at this, Harald. For various downstream packaging reasons, we're going to be stuck with patching, so I'm going to give up on this particular patch.

ar_longnamesIndex is used as an array-index into ar_longnames, which is new[]ed, so a negative index is UB. This patch voids that case.

I pretty much burned out of promo after QtWS. I have Opinions, but not necessarily the desire or energy to share them. I have a thing june 4/5th, and wasn't planning on going to onboarding,; outside of that I'm generally available, but don't let anything depend on me. (editedchanged date on my existing event)

I'd start to think about three separate files , unix_impl.cpp, windows_impl.cpp, stub_impl.cpp (although then you get API-syncing issues, probably, when only one of them is updated).

So there's subtask extract version information from CMakeLists.txt, which implies a few things:

• going over the applications to check that they actually do set their version in the top-level CMakeLists, as part of the project() command,
• check that tooling uses that version consistently,
• check that the tooling can provide the version information everywhere it's needed.

On FreeBSD, /proc is not necessarily mounted (it might be a Linuxism). So while I do have /proc, it's empty because procfs isn't mounted there. If I do mount it, then there's the expected list of processes and a curproc symlink. But /proc/<pid> doesn't contain a stat file .. there's a status, though. Let me mess around a bit with that... yes, changing to status makes all 6 tests pass. So I'd suggest something like

Config: Using QtTest library 5.12.1, Qt 5.12.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by Clang 6.0.1 (tags/RELEASE_601/final 335540))
PASS : KProcessListTest::initTestCase()

With my Calamares maintainer hat on: the decision to live outside of the KDE umbrella was taken before my time, but is basically this: make sure that the installer is seen as a desktop- and sitro-neutral approach, even when it uses KDE technologies. It's an installer for a whole bunch of distro flavors, although it's also enthusiastically used by a bunch of KDE-showcase distro's. I don't want it tied to only the KDE-showcases though.

This has been filed upstream, continues to be unresolved (needs a bunch of kauth work, presumably). It is also an issue with: the webviewmodule, which doesn't run as root because the browser component crashes.

Please file this upstream as appropriate. Probably you can get this done via the packages module, but anything more specific should be discussed elsewhere and have a design attached.

Please file everything upstream as needed.

Similar list as @broulik

Put export in conventional spot.

See if arc diff HEAD^ does what I wanted.

This one accidentally also contains the changes from D17735

Public blog posts about the event:

• https://euroquis.nl/bobulate/?p=1989 (before)
• https://euroquis.nl/bobulate/?p=1991 (after)

With UFS, stat(1) tells me

With UFS, stat(1) tells me

I think you're over-interpreting my comment about the video: it could use an update (can we agree on that? it doesn't show the current state of the phone).

@davidedmundson : can you bring a monitor? since you're driving down that ought to fit. Although a different task says "giant monitor a must" I don't think we should do that last-minute here. Besides, the number of expected attendees is much lower than ELCE, so cost is a thing.

Lessons learned: watch the promo-video playing in the background beforehand, so you can talk about it. Check the video, too .. the PlaMo video has a bunch of art photos (naked!) and punk rock songs (naughty words in the title!) on the demo phone, as well as some personal information that is visible (someone's phone number!); not to mention using a cheesy pre-paid phone operator. So it might be updated.

I sent my generally-positive review of the event to the -promo list. Materials have been sent to Dave for the next event.

• Jon has a box of T-shirts, which we can sell at a pinch and also just wear for consistency (but let's not get stuck on that, and there's something to be said for KDE-in-diversity shirts, e.g. wear what you want)
• I'll leave my SBCs at home, and just bring the pinebook and slimbook

• Do we have a dress code in mind for this? Like, KDE India T-shirts or similar? Polo shirts? I can just throw a bunch of KDE-branded clothes (for me) in the suitcase and see what happens, too.
• None of my SBC's have (touch)screens unless you count the pinebook as one.

Business cards:

• I'm going to use my (very) old ones, since neither my email nor my phone # has changed in all that time. I'll just scratch off "vice-president, KDE e.V.".
• If we actually *have* a business card template (PDF? Scribus? Krita?) that can be adapted by others, it should go on community.k.o, right?

Do we need a couple of these: https://www.staples.nl/reclamehouder-a4-schuin/cbs/2411073.html?promoCode=&Effort_Code=WW&Find_Number=2411073&m=0&isSubscription=False to clamp them in? Something to pick up on saturday at a random office-supplies store?

So those table signs, those would be clamped in those perspex-standy things so you can, for instance, set the "Pinebook" sign next to a Pinebook, pre-answering the "what's that?" question.