@mattdm@adamw@as400 We already kind of do this with the annual survey. If they click yes, we can generate a link (client side) that they can optionally click that doesn't interact with the data collection endpoint at all. The badge would also be opt-in in this way and no data sent if they never click on it. Might be a way to get people to sign up for a FAS as well to get the badge.
@vwbusguy I was thinking more along the lines of writing or using a dummy/minimal one which doesn't really implement the whole protocol properly, just always says user admin is logged in (or whatever). there are some existing ones like this - e.g. https://github.com/Soluto/oidc-server-mock - but still, working one into the current bodhi dev env isn't trivial.
caught up with shutdown email backlog (not too bad)
committed some updated #fedora#openqa needles I created over the shutdown but just left lying uncommitted on the prod server, did another small test fix
cleaned up the discussion thread on my big Bodhi PR a bit so it's easier to review (I hope)
updated openQA and os-autoinst packages to latest git
generated a big needle cleanup commit for openQA, put it on stg for testing
@adamw Yeah, he tends to go straight through like he's speed running it where for me, the side quests are often more important than the main story. I'm not a die hard completionist, but I'll often try to as long as it stays interesting.
lots more trying to get #fedora#openqa update tests working post-F39 branching; I think I have it in a good state now, and gating is enabled for #rawhide again. All tests should pass for Rawhide updates, for F39 updates the desktop_background tests will fail as we don't have F39 backgrounds yet, I have dropped these from the gating policy for now
got sysadmin-main powers. somebody has made a terrible mistake somewhere
@funnelfiasco@adamw I need to watch it. It's "based in" the city I now live in, even though it wasn't actually filmed here. The 1966 Batman movie, however, was filmed here and I think of it every time I go by Stearn's Wharf.
Adam West voice: "Some days you just can't get rid of a bomb!"
today: did my talk at #flocktofedora , I think it wasn't quite as good as at devconf.cz because I was pretty tired, but went well enough! I'll post a link to a recording when one is up somewhere. lots of attending talks (some good ones on CPE team status and rpminspect), hallway track, pub quiz...now to try and get some sleep
hey #fedora#server#fedoraserver folks! I'm floating the idea of possibly dropping #activedirectory client support from the Fedora release criteria (so it'd still be there, but we wouldn't be required to test it every cycle and block the release if it fails). I'm looking for input.
is it a feature of Fedora you value? is it important enough to spend significant time automating (or continuing to test manually)?
@adamw is this feature also needed for the enterprise login in GDM in Workstation? Because I've talked to several sysadmins who use it and they complained it does not always work.
@sesivany it's required if the domain controller is AD. if the domain controller is FreeIPA, of course the AD support isn't needed.
But yeah, that's a good point: we don't actually test that flow either. If there's a bug which isn't in the FreeIPA support or the AD support but is in the GDM code itself, neither of them will work. We don't cover that flow in the automated testing - every time someone mentions it I think "oh yeah we should", but keep forgetting to do it. I'll file a ticket...
spent the entire day down a vast rabbit hole of ancient Fedora/EL release perl packaging stuff, trying to help a project which really didn't care to be helped. I should've taken a hint and quit sooner, but I am bad at stopping in the middle of things. Oh, well
(yes, I did manage to get a CentOS 6 system installed, on a network, and configured with working yum repos for the base system and EPEL. I was surprised too!)
note the quote: "Cisco also said that the hacker’s ability to install malicious firmware exists only for older company products. Newer ones are equipped with secure boot capabilities that prevent them from running unauthorized firmware, the company said."
the #podman thing looks small, but it's quite a cool collaboration with upstream: what it (should) mean is that we catch when a change in something else, e.g. systemd, breaks something important in podman (more than we did already, by doing some functional testing of podman). upstream is excited about it, let's hope it works out well.
more work on the #openqa alternate approach for update and workaround repos, hit a roadblock but got around it, the mechanism now seems to fully work, did a bit of optimization and polish, more to go
#psa : if you're having trouble reaching #fedora stuff - it's because we're being DDoSed. fun times. @nirik is on it, as always, as far as it's possible to be on it anyway...
today's embarrassing workflow confession: I just now switched to using git remote add instead of manually editing .git/config, which I've been doing for I think about a decade at this point
today: more epic battling with the bodhi container development environment. fought ipsilon (fedora's identity...thingy) in a no-holds barred battle and eventually emerged victorious: now the dev env has a kinda 'real' identity layer, you can log in as different users with different capabilities, and be logged out.
this required me to write, uh, four patches (so far) for ipsilon. but it was the last big thing!
now i just need to tidy it all up, add some wrapper commands, and finally submit it.