Our dear friend Petr was not re-elected to FESCo. Therefore, his Fedora Council seat as the FESCo representative needs to be filled by a current member.
So it turns out FESCo has a documented policy on this. Engineering reps do not have to be a member of FESCo, but if FESCo would like to keep Petr as the rep, that should be explicitly affirmed.
I think that it makes more sense generally to have a FESCo member there (this is not personal against Petr).
I'd like to recommend @dcantrell for the liaison position. I spoke to him about it earlier and he was amenable.
I think he'd be a good choice because he's shown that he's able to be impartial when discussing controversial topics and I think he'd represent FESCo's status fairly.
+1
I was about to recommend @dcantrell as well, but was waiting to hear back from him. I am gald that he's amenable.
@dcantrell received +9 votes, which is the max possible value. However, the policy says that "There will be a one week nomination period open for potential representatives."
Since the "People wishing to be nominees should have a solid understanding of FESCo process" I think we don't need to announce the nomination period anywhere (but feel free to do so).
As noted, during the meeting, I'm stepping down from the position, effective immediately: https://pagure.io/Fedora-Council/tickets/issue/304
Metadata Update from @ignatenkobrain: - Issue untagged with: meeting
Metadata Update from @ignatenkobrain: - Issue assigned to ignatenkobrain
Metadata Update from @churchyard: - Issue tagged with: pending announcement
Announced in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GIFKTON4IZPN2DQ5ZAKVLTF5Y4POBJJB/
@bcotton please make any necessary things to get @dcantrell on board.
Metadata Update from @ignatenkobrain: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Done