<@tstellar:fedora.im>
19:01:40
!startmeeting FESCO (2024-05-13)
<@meetbot:fedora.im>
19:01:43
Meeting started at 2024-05-13 19:01:40 UTC
<@meetbot:fedora.im>
19:01:44
The Meeting name is 'FESCO (2024-05-13)'
<@tstellar:fedora.im>
19:01:45
!meetingname fesco
<@tstellar:fedora.im>
19:01:52
!topic Init Process
<@mhayden:fedora.im>
19:01:59
!hi
<@zbyszek:fedora.im>
19:02:00
!hi
<@zodbot:fedora.im>
19:02:03
Major Hayden (mhayden) - he / him / his
<@jonathanspw:fedora.im>
19:02:04
!hi
<@zodbot:fedora.im>
19:02:05
Zbigniew Jędrzejewski-Szmek (zbyszek)
<@tstellar:fedora.im>
19:02:06
!hi
<@jistone:fedora.im>
19:02:06
!hi
<@zodbot:fedora.im>
19:02:08
Jonathan Wright (jonathanspw)
<@zodbot:fedora.im>
19:02:10
Tom Stellard (tstellar)
<@zodbot:fedora.im>
19:02:10
Josh Stone (jistone) - he / him / his
<@blackwell:fedora.im>
19:02:15
!hi
<@zodbot:fedora.im>
19:02:19
Jason Blackwell (blackwell)
<@mhayden:fedora.im>
19:02:19
_needs to depart around 20-30 mins after the hour_ 😢
<@humaton:fedora.im>
19:02:29
!hi
<@zodbot:fedora.im>
19:02:32
Tomáš Hrčka (humaton) - he / him / his
<@berrange:matrix.org>
19:02:39
!hi
<@zodbot:fedora.im>
19:02:42
No Fedora Accounts users have the @berrange:matrix.org Matrix Account defined
<@tstellar:fedora.im>
19:02:45
OK, looks like we have quorum.
<@nirik:matrix.scrye.com>
19:03:04
morning
<@zbyszek:fedora.im>
19:03:40
danpb: thanks for coming.
<@tstellar:fedora.im>
19:04:00
!topic
#3205 Request exception to permit shipping pre-built, signed SGX enclave binaries in Fedora
<@tstellar:fedora.im>
19:04:15
!fesco 3205
<@zodbot:fedora.im>
19:04:19
**fesco #3205** (https://pagure.io/fesco/issue/3205):**Request exception to permit shipping pre-built, signed SGX enclave binaries in Fedora**
● **Opened:** 5 days ago by berrange
● **Last Updated:** 4 minutes ago
● **Assignee:** Not Assigned
<@zbyszek:fedora.im>
19:05:11
In general, I'm happy with the proposal as it stands.
<@tstellar:fedora.im>
19:06:09
The proposed solution, seems the best out of all of them. My only concern is that it will be difficult to reproduce the buids bit for bit when there are updates.
<@jistone:fedora.im>
19:06:11
I'm not thrilled about entire custom toolchains
<@jistone:fedora.im>
19:07:30
the situation seems sort of similar to openh264 to me (though the reasons aren't the same)
<@nirik:matrix.scrye.com>
19:07:39
I'm not happy about the entire thing, but oh well. ;(
<@jistone:fedora.im>
19:07:44
what's so wrong with pointing to an external repo?
<@nirik:matrix.scrye.com>
19:08:17
Also, do we want to allow some community discussion of this? it just went to fesco via ticket... or is that unlikely to provide much additional input or ideas?
<@sgallagh:fedora.im>
19:08:30
.gi
<@sgallagh:fedora.im>
19:08:31
.hi
<@sgallagh:fedora.im>
19:08:40
(Sorry, got sidetracked and am late)
<@sgallagh:fedora.im>
19:08:43
!hi
<@zodbot:fedora.im>
19:08:46
Stephen Gallagher (sgallagh) - he / him / his
<@sgallagh:fedora.im>
19:09:21
So, I'm opposed to this as written. I agree with Josh; this looks like it should be solved similarly to H.264
<@tstellar:fedora.im>
19:10:21
Stephen Gallagher: What's the H.264 solution, third-party repository?
<@nirik:matrix.scrye.com>
19:11:13
we build it, but they distribute it. it's not exactly the same here tho.
<@zbyszek:fedora.im>
19:11:15
The reason we used an external repo for x264 was the were _not_ allowed to ship the code ourselves. The external repo was the only legal way it could be shipped, i.e. the only legal way we could make it easily available for our users.
<@sgallagh:fedora.im>
19:12:12
The thing that really bothers me about this is that it's an entire execution environment that we cannot validate or verify.
<@sgallagh:fedora.im>
19:12:44
Why would I trust that it's truly confidential if I can't validate that the binary matches the sources?
<@zbyszek:fedora.im>
19:12:46
But here the situation is different: first, we _can_ ship the code, and that means that we can make the packaging as good as we want it. Second, there is no external repo. Based on the description in the ticket, it seems Intel wants to do one build (in the way that they already have set up), and they have no desire to do packaging for us.
<@berrange:matrix.org>
19:12:49
what do you mean by that ? what would you want to validate in respect of the hardware features ?
<@sgallagh:fedora.im>
19:12:57
Or rebuild it myself and add my own signing key?
<@zbyszek:fedora.im>
19:13:18
No, that's a complete misunderstanding.
<@zbyszek:fedora.im>
19:14:04
The whole complicated setup is so that we actually _do_ verify that the binary matches the sources.
<@sgallagh:fedora.im>
19:14:06
Sorry, coming back up to speed as quickly as I can. I read the ticket last week while I was away at a conference.
<@jistone:fedora.im>
19:14:24
Does Fedora Legal need to weigh in on this too?
<@berrange:matrix.org>
19:14:41
the proposal is that the we do a build in fedora koji and validate this is byte-for-byte identical to the pre-built binary signed by Intel, (minus the signature of course)
<@zbyszek:fedora.im>
19:15:06
You can do that, but that'd be completely useless, because the CPU firmware is not going to trust your key. And, unlike in SecureBoot, there is no mechanism to allow custom keys.
<@zbyszek:fedora.im>
19:16:01
Why do you think so? The license situation is very clear.
<@sgallagh:fedora.im>
19:16:06
OK, sorry. I just finished rereading the ticket and I see where I got tripped up.
<@sgallagh:fedora.im>
19:16:34
Why is "Require anyone who wants to run TDX CVMs to acquire the pre-built enclaves from Intel's GitHub download site. Possibly add a script to Fedora to download this automatically on boot or first use. I include this for completeness, as it is the fallback if all the other options above are rejected. I think it would be an unfriendly solution for Fedora's users though, so I'd like to avoid it." not the best option?
<@jistone:fedora.im>
19:16:53
In case the binary aspect needs approval - maybe it doesn't, I don't know
<@tstellar:fedora.im>
19:17:15
What is the license?
<@sgallagh:fedora.im>
19:17:18
Why is "Require anyone who wants to run TDX CVMs to acquire the pre-built enclaves from Intel's GitHub download site. Possibly add a script to Fedora to download this automatically on boot or first use." not the best option?
<@berrange:matrix.org>
19:17:43
it doesn't give a seemless out of the box experiance, and doesn't co-ordinate fedora software updates with the vendor's own updates schedule
<@sgallagh:fedora.im>
19:17:49
Tom Stellard: As long as it's freely distributable, I think we could make a reasonable argument that this is a "firmware blob"
<@berrange:matrix.org>
19:18:02
the code is under quite a variety of licenses, but all are approved for Fedora
<@berrange:matrix.org>
19:18:38
last i audited, i got "BSD-3-Clause AND Apache-2.0 AND MIT AND OpenSSL AND ISC AND BSD-2-Clause AND GPL-2.0-only AND SMLNJ AND NCSA AND Apache-1.0 AND FSFAP AND BSD-4-Clause-UC AND FSFUL AND Zlib AND (Apache-2.0 OR GPL-2.0-or-later) AND EPL-1.0 AND MS-PL AND BSD-4-Clause AND MIT-0"
<@sgallagh:fedora.im>
19:19:19
danpb: I'm not sure I follow; if we just added a systemd unit file that checks for and updates the SGX blob as a `Before=libvirt.service`, how would the end-user notice or care?
<@zbyszek:fedora.im>
19:19:26
It's a binary that we have built in koji from sources that allow redistribution. It is true that we used a specific version of the compiler to build it, but we have many packages which use a specific version of the compiler to build (e.g. different llvm versions, or different java versions, etc, etc.). We don't make special provisions for code that is built with a non-default compiler or some compat versions of libraries. And at the technical level, this is exactly what is happening here.
<@sgallagh:fedora.im>
19:19:31
(I oversimplified that, but the gist is there)
<@sgallagh:fedora.im>
19:20:02
zbyszek: No, but we do require that those special versions of the compiler are, themselves, built in Fedora.
<@tstellar:fedora.im>
19:20:12
I agree with Josh Stone I think we we would need to have Fedora Legal review this if we end-up redistributing binaries. Re-distributing binaries and building from sources are different.
<@sgallagh:fedora.im>
19:20:21
We have a chain of trust from code to binary that passes through the compiler and build-system
<@berrange:matrix.org>
19:20:23
a slight difference from firmware, is that this runs at normal userspace privilege level, as opposed to a higher privilege beneath the OS - a SGX enclave is merely a way of isolating trusted code from untrusted code
<@zbyszek:fedora.im>
19:20:52
It also requires a working network connection to the outside.
<@sgallagh:fedora.im>
19:21:18
zbyszek: True, and that's definitely a valid concern, particularly for air-gapped setups
<@zbyszek:fedora.im>
19:21:54
But we are distributing a binary that we built ourselves.
<@blackwell:fedora.im>
19:22:06
It could be packaged into the image for an airgapped setup
<@zbyszek:fedora.im>
19:22:23
It happens to be the same as some other binary, but that's OK.
<@jistone:fedora.im>
19:22:27
This is kind of splitting hairs, but AIUI the koji build is building the source to ensure equivalence with the signed binaries. That's valuable, but not exactly the same as distributing what we build.
<@berrange:matrix.org>
19:23:15
this is kind of like the 'shim' model, except that we're using a fixed toolchain with byte-for-byte reproducibility, so when we send the binary off for signing, they can just give us back a binary they already had signed
<@tstellar:fedora.im>
19:23:31
zbyszek: Are we, I though in the end we were distributing the upstream binaires?
<@berrange:matrix.org>
19:23:56
the main difference from shim, is that while users can do custom builds, they can't practically use them
<@sgallagh:fedora.im>
19:24:14
That's another point: have we been able to ensure that we *can* get a byte-for-byte replica?
<@berrange:matrix.org>
19:24:36
i've got about 90% of the way there
<@sgallagh:fedora.im>
19:24:55
So only 90% to go? :)
<@mhayden:fedora.im>
19:25:26
_will be back in a half hour_
<@zbyszek:fedora.im>
19:26:38
You have a point, that'd we'd actually distribute the "upstream binaries". If that matters, we could change things to copy the original signature into "our" binaries. The result might as well be identical. I have no idea how much extra work that'd be.
<@berrange:matrix.org>
19:26:47
heh. i'm fairly confident i'll succeed, but obviously if i fail, then my proposal is void. i wanted to at least get some feedback from FESCO on whether its worth investing more time in this approach... don't want todo the work if there's no chance of being accepted in fedora
<@sgallagh:fedora.im>
19:27:43
Yeah, that's wise. And I appreciate the hard work you're putting into this.
<@sgallagh:fedora.im>
19:28:18
Some of this is me being annoyed that there's no meaningful way for us to sign our own builds for this purpose.
<@sgallagh:fedora.im>
19:29:28
Among other things, I *really* don't like distributing "security" software that is reliant on an ancient build system that almost certainly has unpatched vulnerabilities in it
<@tstellar:fedora.im>
19:29:36
If in the end, if the RPMs include the binaries that we built in koji ourselves (and we aren't just copying the upstream binaries included as a 'source', then I think this part of it is fine. The main concerns I have are: 1) If it's realistic to always be able to produce byte-for-byte results 2) We have no way to fix bugs/security issues ourselves. 3) The custom toolchain, which I think should be bundled with the SGX package.
<@jistone:fedora.im>
19:29:36
How much of the binary is actually checked by the signature? All of it? or just sections like .text/.data? There might also be other Fedora stuff like annobin that we'd want to keep in our build, if the signing allows.
<@berrange:matrix.org>
19:30:04
yeah, i'm annoyed at that myself too, as it does undermine one of the key benefits of OSS .... but if you take the view that this is like 'firmware', then its miles ahead that usual situation of completely opaque firmware blobs
<@sgallagh:fedora.im>
19:30:43
danpb: Curses! You've caught me by my own favorite adage about perfection vs. good enough.
<@tstellar:fedora.im>
19:31:21
Also what about code like x = dlopen("somelib.so"); if (x) { do_something();} Binary compatibility does not necessarily mean it behaves the same always.
<@berrange:matrix.org>
19:31:28
i'm not 100% certain, but i think basically the entire of the elf binary is validated - eg even the .interp section is checked, despite that being irrelevant - i've got a todo to ask intel to remove the .interp section since its needlessly referencing a nixos path that doesn't need to exist
<@sgallagh:fedora.im>
19:32:46
Possibly a tangent, but is there an alternative being offered for similar behavior on non-x86 hosts? I can certainly see this being interesting for e.g. aarch64 systems in AWS
<@berrange:matrix.org>
19:32:49
while this is distributed as a ELF .so binary, AFAIK, its not something you can just dlopen() and execute from a regular Fedora program - they've just used ELF as a convenient binary format, and have a custom loader that extracts the code and loads it into the SGX enclave
<@berrange:matrix.org>
19:33:58
this is entirely Intel SGX/TDX x86 specific - other arches & vendors have their own completely different approach to confidential VMs, and most of them have all the code in opaque firmware.
<@sgallagh:fedora.im>
19:34:14
Ack
<@zbyszek:fedora.im>
19:35:22
> 1) If it's realistic to always be able to produce byte-for-byte results
In general, Debian and Arch have 80-90% reproducibility for all packages. For compiled packages, the expectation in general is 100% reproducibility. At least in Fedora, for many compiled packages we got full reproducibility very early.
<@sgallagh:fedora.im>
19:35:31
The rebuilds we'd be doing to compare for byte-for-byte match: they're prebuilt binaries of the compiler/linker?
<@sgallagh:fedora.im>
19:35:47
Or we will have those rebuilt in our infrastructure as well?
<@zbyszek:fedora.im>
19:36:03
Or maybe to put in a different way: for a package where some effort is put into reproducibility, it is expected to get full reproducibility without problem.
<@jistone:fedora.im>
19:36:21
What's your packaging plan for the custom toolchain? Can we ensure that nothing else uses it? Or do you have to use it when building your own SGX code using these runtimes?
<@berrange:matrix.org>
19:36:40
I would have to create toolchains in koji in the normal way, eg a 'sgx-gcc' and 'sgx-binutils' packages, which uses a specific required version
<@sgallagh:fedora.im>
19:37:21
OK, but they would be built, not just copied from upstream. I'm okay with that.
<@berrange:matrix.org>
19:37:47
those would install a /usr/bin/x86-64-intel-sgx-gcc binary for example - i'm thinking of this as a 'x86_64-intel-sgx' build target - and so its obvious these builds are not for general use
<@zbyszek:fedora.im>
19:37:50
> 2) We have no way to fix bugs/security issues ourselves.
Yeah, that's certainly annoying. But considering that the whole idea is to not trust the underlying host, i.e. in particular the distro installed by the vendor, there doesn't seem to be any way around this. The only solution is Intel releases fixed versions quickly.
<@sgallagh:fedora.im>
19:37:50
(I assume they'd bootstrap and be used to build themselves as the regular ones do)
<@tstellar:fedora.im>
19:37:51
My opinion is that the toolchains should be bundled and not distributed.
<@sgallagh:fedora.im>
19:38:33
Tom Stellard: I agree with "not distributed"
<@nirik:matrix.scrye.com>
19:38:37
less chance of anyone else trying to use them that way
<@jistone:fedora.im>
19:38:50
I wouldn't think so, they're still running on the normal host, like a cross compiler.
<@berrange:matrix.org>
19:38:54
so you mean build the required gcc/inbutils as part of the 'sgx' rpm build, and not package them as their own rpms ?
<@sgallagh:fedora.im>
19:38:54
We could probably exclude them from composes and keep them only in the buildroot for a special side-tag?
<@zbyszek:fedora.im>
19:39:01
That'd be very painful for the sgx package, because each build would take forever.
<@tstellar:fedora.im>
19:39:43
danpb: Right.
<@zbyszek:fedora.im>
19:39:45
We have a general rule that it's OK to package compat versions of packages. I think we should treat this as any other case, and maybe even use the normal compat-package-naming scheme.
<@sgallagh:fedora.im>
19:40:11
Josh Stone: I meant something different, but the specifics are a tangent we could discuss later.
<@nirik:matrix.scrye.com>
19:40:39
This seems like a long way to go for a pretty small user base, but I guess they might really like that someone did
<@tstellar:fedora.im>
19:40:41
zbyszek: Is this something that would be updated a lot?
<@zbyszek:fedora.im>
19:40:52
Frankly, I don't understand why you'd want that. It'd require a monstrous spec file with many unrelated parts that'd be ineffective and hard to maintain.
<@sgallagh:fedora.im>
19:41:14
danpb: Does Intel rev the build chain concurrently with the sgx binaries?
<@berrange:matrix.org>
19:41:43
intel do perhaps 3-4 releases a year of the SGX bits.... but the toolchain they use doesn't change very often...hence why it is on an annoyingly old gcc/binutils
<@sgallagh:fedora.im>
19:41:45
If so, maybe it makes sense to bundle them. If the build chain is largely static, we should probably keep it separate so sgx builds don't take literal days.
<@tstellar:fedora.im>
19:42:15
I don't think bundling gcc would take days.
<@berrange:matrix.org>
19:42:34
i get the impression they're pretty paranoid about the code that's generated, especially wrt to spectre related side channel mitigations, so uninclined to change toolchain versions often
<@tstellar:fedora.im>
19:43:37
Also, there are ways to speed it up, e.g. removing unneeded language support, and not doing a 3-stage build.
<@zbyszek:fedora.im>
19:44:24
Anyway, I'm not particularly oppposed to bundling it, but I don't think we should mandate this either way. I'd leave it to the maitainers of the package to make the decision. Possibly with different choices for different parts of the stack (gcc, binutils, some libraries, etc.)
<@tstellar:fedora.im>
19:44:36
I don't think we should be packaging custom toolchains. This is not the same as just packaging an old version of gcc. Their toolchain could be patches or have other modifications in it.
<@tstellar:fedora.im>
19:44:47
I don't think we should be packaging custom toolchains. This is not the same as just packaging an old version of gcc. Their toolchain could be patched or have other modifications in it.
<@berrange:matrix.org>
19:45:03
i guess packaging of toolchain is more of a minor detail we can debate if this is actually approved as a concept... i'm not too fussed on choices on that side personally
<@sgallagh:fedora.im>
19:45:38
Tom Stellard: If we don't do that, we default to either shipping their signed binary untested or not shipping SGX at all. Are those preferable?
<@berrange:matrix.org>
19:45:48
it is unpatched by intel at least - its a a standard NixOS package, and from what i see there's no patches - i've been using unmodified upstream tarballs for testnig thus far
<@tstellar:fedora.im>
19:45:49
We've been discussing for 45 minutes now. Do we have a proposal or something to vote on?
<@sgallagh:fedora.im>
19:46:01
s/untested/unvalidated/
<@sgallagh:fedora.im>
19:46:27
I'll make a proposal
<@tstellar:fedora.im>
19:46:44
What do you mean? We can still build our own identical copy of the SGX bits even if we don't distribute the custom toolchain.
<@jistone:fedora.im>
19:47:14
(i.e. %build-only bundling)
<@sgallagh:fedora.im>
19:47:34
Tom Stellard: Were you using "package" as a synonym for "distribute"?
<@tstellar:fedora.im>
19:47:35
Yeah, maybe I should be calling it something other than bundling.
<@sgallagh:fedora.im>
19:47:56
OK, I think that was the disconnect.
<@tstellar:fedora.im>
19:48:01
Yes.
<@sgallagh:fedora.im>
19:48:22
If you mean "we just don't distribute the custom toolchain", that's a huge difference from "we don't package it".
<@sgallagh:fedora.im>
19:48:26
Got it
<@tstellar:fedora.im>
19:48:56
Stephen Gallagher: You mean we could build RPMs for it, but keep it in the buildroot?
<@sgallagh:fedora.im>
19:49:03
Yes
<@sgallagh:fedora.im>
19:49:26
Like what we used to do for `glibc32` (not that I particularly like that idea, but it's possible and has precedent)
<@nirik:matrix.scrye.com>
19:50:00
others could still use it if it's in the buildroot
<@tstellar:fedora.im>
19:51:05
Stephen Gallagher: That makes sense from a technical perspective, but I'm really hesitant to go down that path, so we don't end up with a buildroot full of ibm-clang, intel-clang, amd-clang, swift-clang, pytorch-clang, etc.
<@sgallagh:fedora.im>
19:51:13
Proposal: Approved as long as we can produce binaries that match the signed ones from upstream using a toolchain built entirely in Fedora infrastructure. In this case, the upstream signed binary may be distributed via the Fedora repositories.
<@zbyszek:fedora.im>
19:51:44
+1
<@sgallagh:fedora.im>
19:51:52
(I am intentionally leaving the implementation of "a toolchain built entirely in Fedora infra" as an open question
<@sgallagh:fedora.im>
19:51:57
(I am intentionally leaving the implementation of "a toolchain built entirely in Fedora infra" as an open question)
<@tstellar:fedora.im>
19:52:31
I don't want to give blanket approval without knowing all the details about the toolchain, I think we should revisit, once there is a complete implementation.
<@tstellar:fedora.im>
19:52:47
Also the fact that we can't fix CVEs is concerning to me.
<@sgallagh:fedora.im>
19:53:04
Tom Stellard: Shall we take that as a -1 vote?
<@berrange:matrix.org>
19:53:34
fwiw, i'd expect to submit a Fedora Change proposal once we come to actually integrate this in Fedora
<@tstellar:fedora.im>
19:53:54
Yeah -1. I think the process of building byte identical binaries and distributing those should be allowed for this, but I have concerns about some of the other details.
<@sgallagh:fedora.im>
19:54:03
I'm personally willing to trust danpb to approach this in a manner that matches with Fedora's mission.
<@nirik:matrix.scrye.com>
19:54:04
I've not had the time to think about this in depth. I'd vote -1 or 0 today...
<@sgallagh:fedora.im>
19:54:57
Tom Stellard: I agree with your concerns, particularly around CVEs, but I don't know that we have any better options at this time.
<@jistone:fedora.im>
19:55:10
Can we require the future Change as part of the proposal we're voting on? That will also open up community discussion as mentioned earlier.
<@sgallagh:fedora.im>
19:56:09
I'd like to at least provide the virt folks with some assurance that if they go and do all this work, it won't be wasted.
<@nirik:matrix.scrye.com>
19:56:19
but if we approve it today, aren't we just approving the change before it exists?
<@zbyszek:fedora.im>
19:56:21
That is a good concern, but the way the whole concept is implemented in hardware and the policy that is built around that means that CVEs can only be fixed by the CPU vendor. So if you want to block on that, then that's essentially equivalent to never allowing this to be distributed in Fedora.
<@jistone:fedora.im>
19:56:54
or it means allowing it on the same terms as other firmware
<@tstellar:fedora.im>
19:57:34
zbyszek: I'm not saying I'll block on this, but this is the kind of thing that should be addressed in a change proposal with at least an explanation about the risks and the history if any of CVE response from upstream.
<@berrange:matrix.org>
19:58:22
i'd point out that Intel have a vested interest in promptly fixing CVEs in their enclaves, since this is the base of their root of trust, and any flaws are visible to all in the source that's open
<@tstellar:fedora.im>
19:58:30
I think this is a good goal.
<@berrange:matrix.org>
19:59:20
this meeting has already given me more confidence, since you didn't immediately dismiss the concept as I feared might happen.
<@tstellar:fedora.im>
19:59:26
So far we have (+2,0,-2) any other votes. We are almost at the one hour mark.
<@blackwell:fedora.im>
19:59:50
+1
<@humaton:fedora.im>
20:00:05
I was just reading on it bit more
<@sgallagh:fedora.im>
20:00:36
danpb: I'm not saying I love the idea, but so far it seems like the approach that best aligns with our mission AND provides assurance that we're not distributing something untrusted.
<@zbyszek:fedora.im>
20:00:38
There was actually only one -1 vote so far.
<@tstellar:fedora.im>
20:00:53
I'm going to wait 2 more minutes and then close the voting, we need to move on, since we are out of time.
<@humaton:fedora.im>
20:01:01
+1
<@sgallagh:fedora.im>
20:01:01
Jason Blackwell: Only FESCo members get a counted vote, but thank you for your participation :)
<@tstellar:fedora.im>
20:01:20
zbyszek: OK, I see nirik didn't actually vote.
<@tstellar:fedora.im>
20:01:39
(+3,0,-1) right now.
<@jistone:fedora.im>
20:01:41
0 - I don't think we should approve it now, but keep exploring and go for the Change
<@sgallagh:fedora.im>
20:01:44
zbyszek: Kevin had "-1 or 0"
<@tstellar:fedora.im>
20:02:25
(+3,1,-1) does anyone else want to vote?
<@sgallagh:fedora.im>
20:02:44
Does that include my implicit +1?
<@sgallagh:fedora.im>
20:03:03
(Looks like yes by my count)
<@tstellar:fedora.im>
20:03:14
Stephen Gallagher: jednorozec zbyszek with +1
<@sgallagh:fedora.im>
20:03:46
OK, we don't have anything approaching a consensus, so let's call that Proposal failed for now.
<@sgallagh:fedora.im>
20:04:01
danpb: Would you be willing to file a Change Proposal?
<@sgallagh:fedora.im>
20:04:07
I think that's probably the best next step
<@berrange:matrix.org>
20:05:09
yes, i'm happy enough to carry on working to provide a fully functional PoC of reproducibility and a Change proposal
<@zodbot:fedora.im>
20:05:23
No Fedora Accounts users have the @berrange:matrix.org Matrix Account defined
<@zodbot:fedora.im>
20:05:29
No Fedora Accounts users have the @berrange:matrix.org Matrix Account defined
<@zodbot:fedora.im>
20:05:42
No Fedora Accounts users have the @berrange:matrix.org Matrix Account defined
<@tstellar:fedora.im>
20:05:53
Do we need to record an official decision? It's not technically rejected, since not everyone voted, I think.
<@jistone:fedora.im>
20:05:59
look at all that karma floating away...
<@sgallagh:fedora.im>
20:06:33
Tom Stellard: A vote that doesn't pass maintains the status quo
<@zbyszek:fedora.im>
20:06:49
Tom Stellard: I think it was a valid decision. 5 people voted.
<@tstellar:fedora.im>
20:07:15
zbyszek: I think normally in this case,we would continue the vote in the ticket.
<@sgallagh:fedora.im>
20:07:16
Think of it as "The motion fails"
<@tstellar:fedora.im>
20:07:49
e.g. if this was an actual change proposal, then we couldn't reject it outright with these votes.
<@sgallagh:fedora.im>
20:07:55
Tom Stellard: Yeah, I think that's our usual policy, but I'm going to formally withdraw the proposal to make things easier :)
<@tstellar:fedora.im>
20:08:04
OK, let's move on.
<@tstellar:fedora.im>
20:08:09
!topic #3206 Nonresponsive maintainer: Lubomir Rintel lkundrak
<@zbyszek:fedora.im>
20:08:13
!action danpb to carry on working to provide a fully functional PoC of reproducibility and a Change proposal
<@tstellar:fedora.im>
20:08:19
!fesco 3206
<@berrange:matrix.org>
20:08:20
thank you all for your time and useful debate
<@zodbot:fedora.im>
20:08:22
**fesco #3206** (https://pagure.io/fesco/issue/3206):**Nonresponsive maintainer: Lubomir Rintel lkundrak**
● **Opened:** 5 days ago by lihis
● **Last Updated:** Never
● **Assignee:** Not Assigned
<@tstellar:fedora.im>
20:08:34
This was raised on the list. Quickly, what action do we need to take here?
<@sgallagh:fedora.im>
20:08:55
Why is this on the agenda? It hasn't been a week and no one proposed it with the `meeting` tag.
<@sgallagh:fedora.im>
20:09:12
NRM tickets are usually handled async.
<@tstellar:fedora.im>
20:09:45
Someone replied on the devel list to the agenda and asked about this. If there is nothing to do, we can move on.
<@zbyszek:fedora.im>
20:10:01
Proposal: Give the two packages to lihis.
<@jistone:fedora.im>
20:10:09
I don't see that -- did they reply privately?
<@tstellar:fedora.im>
20:10:29
Oh yeah, it was a private reply, sorry.
<@tstellar:fedora.im>
20:10:56
Ok, let's have this just be a reminder to review the ticket and vote, then.
<@zbyszek:fedora.im>
20:10:59
Withdrawn.
<@sgallagh:fedora.im>
20:11:05
ack
<@tstellar:fedora.im>
20:11:07
!topic Next week's chair
<@sgallagh:fedora.im>
20:11:22
I'll pick it up; I missed my last turn
<@tstellar:fedora.im>
20:11:33
Stephen Gallagher: Thank you!
<@tstellar:fedora.im>
20:11:45
!action Stephen Gallagher will chair next meeting
<@tstellar:fedora.im>
20:11:52
!topic Open Floor
<@tstellar:fedora.im>
20:12:04
Any other topics for discussion?
<@tstellar:fedora.im>
20:13:46
I'll close the meeting in 2 minutes if nothing else.
<@zbyszek:fedora.im>
20:14:40
Tom Stellard: thanks for chairing.
<@sgallagh:fedora.im>
20:15:00
Thanks for chairing, Tom Stellard . It was one of the more involved sessions.
<@zodbot:fedora.im>
20:16:06
sgallagh gave a cookie to tstellar. They now have 19 cookies, 4 of which were obtained in the Fedora 40 release cycle
<@tstellar:fedora.im>
20:16:29
!endmeeting