<@amoloney:fedora.im>
15:03:54
!startmeeting Fedora Council Meeting
<@meetbot:fedora.im>
15:03:55
Meeting started at 2024-12-18 15:03:54 UTC
<@meetbot:fedora.im>
15:03:55
The Meeting name is 'Fedora Council Meeting '
<@amoloney:fedora.im>
15:04:05
!topic Ticket Discussion
<@bookwar:fedora.im>
15:04:28
!hi
<@zodbot:fedora.im>
15:04:29
Aleksandra Fedorova (bookwar) - she / her / hers
<@rwright:fedora.im>
15:04:31
!hi
<@zodbot:fedora.im>
15:04:32
Robert Wright (rwright) - he / him / his
<@amoloney:fedora.im>
15:04:38
!info We will discuss tickets in the tracker that require wider council discussion
<@asamalik:fedora.im>
15:04:38
!hi
<@zodbot:fedora.im>
15:04:40
Adam Samalik (asamalik) - he / him / his
<@mattdm:fedora.im>
15:04:46
Are there urgent tickets _other_ than FInal Gitforge?
<@amoloney:fedora.im>
15:05:00
!link https://pagure.io/Fedora-Council
<@amoloney:fedora.im>
15:05:11
!topic Git Forge Replacement
<@amoloney:fedora.im>
15:05:19
mattdm: yes and no
<@amoloney:fedora.im>
15:05:38
so for the git forge one, we are at the 2-week window for feedback on our announcement to go with forgejo
<@mattdm:fedora.im>
15:05:41
heh. _why can't anything be simple?_
<@amoloney:fedora.im>
15:06:24
I have not heard nor seen anything that would make me reconsider Forgejo as the choice, so I will open a voting ticket for us to formally vote in this change
<@amoloney:fedora.im>
15:06:36
Please all council members prioritize this vote
<@amoloney:fedora.im>
15:07:07
Ideally we can announce the decision then on Monday 23rd, so that will give us 2 days to vote and create an announcement
<@rwright:fedora.im>
15:07:26
It will be a Christmas git forge!
<@amoloney:fedora.im>
15:07:42
gi(f)t - forge ;p
<@mattdm:fedora.im>
15:07:54
I know some people are away for the holidays, but I don't think any of them have a surprise -1
<@mattdm:fedora.im>
15:09:00
So I'm in support of making the final deadline the 23rd. We'll need at least 3 +1s and no -1s by then. But ideally, we'll have everyone's vote, or close to it.
<@amoloney:fedora.im>
15:09:53
!proposed Council will take a formal vote via ticket on opting to move Fedora to Forgejo as the git forge replacement. We will take a 'lazy' consensus as some members are already on vacation and no council members to date have expressed any -1's publicly or privately on choosing Forgejo. If the decision passes, an announcement will be released on Monday 23rd December
<@amoloney:fedora.im>
15:09:59
^ this sound ok?
<@mattdm:fedora.im>
15:11:00
Pendantically, this will be "full consensus", rather than "lazy". People have had _plenty_ of time.
<@dcantrell:fedora.im>
15:11:15
I dunno, did anyone check out Perforce?
<@amoloney:fedora.im>
15:11:24
Double pedantically - if we say full we are locked to that
<@mattdm:fedora.im>
15:11:43
see https://docs.fedoraproject.org/en-US/council/#decisions
<@amoloney:fedora.im>
15:11:54
and if folks are out, we cant agree until they have cast their vote
<@mattdm:fedora.im>
15:12:20
full is _defined_ as three +1s, no -1s. Lazy is "say you're going to do it, and if no one objects, just do it"
<@amoloney:fedora.im>
15:12:33
ah ok then
<@amoloney:fedora.im>
15:13:03
once it doesnt lock us to full council voting, and we can pass this with x3 +1's then Ill update and mark it as agreed
<@mattdm:fedora.im>
15:13:17
this may be a surprising definition if you haven't been deeply involved in group highly obsessed with the administration of consensus processes. but it's a fairly common thing -- not a fedora weirdness
<@mattdm:fedora.im>
15:13:43
thankfully we haven't _had_ to worry about that detail recently
<@dcantrell:fedora.im>
15:13:45
at least we're not IETF
<@mattdm:fedora.im>
15:14:08
yes
<@dcantrell:fedora.im>
15:14:54
(RFC 7282 for some fun reading for anyone interested)
<@mattdm:fedora.im>
15:15:06
don't threaten me with a good time
<@amoloney:fedora.im>
15:15:08
!agreed Council will take a formal vote via ticket on opting to move Fedora to Forgejo as the git forge replacement. We will follow the full consensus model as described in the Fedora council charter on making decisions, requiring three +1's to pass this decision as some members are already on vacation and no council members to date have expressed any -1's publicly or privately on choosing Forgejo. If the decision passes, an announcement will be released on Monday 23rd December
<@amoloney:fedora.im>
15:15:31
ok thats done
<@amoloney:fedora.im>
15:16:34
We have some other tickets in need of discussion, but they are marked private and are around the recent decision on removing packager rights from someone and how that process is handled. Is this something we should/can discuss in this meeting?
<@mattdm:fedora.im>
15:16:59
I think we should have a call to discuss with high bandwidth.
<@mattdm:fedora.im>
15:17:29
I know that transparency is part of the problem here, and I don't want to _add_ to that, so we shouldn't make any decisions that way... but I think we could benefit from talking
<@rwright:fedora.im>
15:18:11
I'd like to just add to the meeting that mattdm has been a great FPL - and I just want to acknowledge that in the meeting to thank him for all his years guiding the Fedora community!
<@amoloney:fedora.im>
15:18:25
+1
<@ffmancera:fedora.im>
15:18:28
<3
<@asamalik:fedora.im>
15:18:36
I would prefer to have a call to get on the same page. We can summarise and make any decisions publicly after we understand the issue fully.
<@jsteffan:fedora.im>
15:18:37
+1
<@bookwar:fedora.im>
15:18:39
We can state that yes, Council is going to look into the matter and will provide more information when ready
<@mattdm:fedora.im>
15:18:59
I'm going to send a meeting link to the private council channel, then.
<@mattdm:fedora.im>
15:19:24
in a minute, because I apparently need to restart wireplumber
<@jsteffan:fedora.im>
15:19:27
Also, if possible, transcripts from the council discussion via high bandwidth would go a long ways for transparency.
<@bookwar:fedora.im>
15:19:28
But I want to have initial call to set up the structure and expectations for this discussion.
<@amoloney:fedora.im>
15:20:34
Agreed. Im going to change the topic to metion those tickets and add a proposed statement, and then add an agreed just for completeness for thie minutes
<@amoloney:fedora.im>
15:20:56
!topic Private tickets regarding proven packager process gaps
<@mattdm:fedora.im>
15:21:05
are people around tomorrow if we need more followup
<@dcantrell:fedora.im>
15:21:35
I am around tomorrow
<@amoloney:fedora.im>
15:22:27
!proposed There are a number of private tickets for the council to review and discuss regarding a recent incident involving the proven packager guidelines and processes. The council is going to look into the matter and will provide more information when ready
<@amoloney:fedora.im>
15:23:32
I know its kinda vague but I agree that we should at least acknowledge it and then as Adam suggested get on the same page about what happened and how best to proceed
<@amoloney:fedora.im>
15:26:11
any alterations to be made to that proposal?
<@ffmancera:fedora.im>
15:27:11
I think it is fine
<@mattdm:fedora.im>
15:27:26
yes.
<@amoloney:fedora.im>
15:27:45
!agreed There are a number of private tickets for the council to review and discuss regarding a recent incident involving the proven packager guidelines and processes. The council is going to look into the matter and will provide more information when ready
<@amoloney:fedora.im>
15:28:02
!topic Ticket Admin
<@amoloney:fedora.im>
15:28:15
!topic F42 Codename Request
<@amoloney:fedora.im>
15:28:25
!link https://pagure.io/Fedora-Council/tickets/issue/509
<@amoloney:fedora.im>
15:28:58
this ticket has received x5 +1's and x1 0 - I am marking this as approved. Any objections?
<@ffmancera:fedora.im>
15:29:27
Not from me
<@amoloney:fedora.im>
15:43:44
!agreed The Codename request for F42 is approved, as per council votes in the ticket (+3, 1, 0)
<@amoloney:fedora.im>
16:05:06
This is all we will have time for this week, and on behalf of the Council, Merry Christmas, Happy holidays and a Happy New Year - cya in 2025!
<@amoloney:fedora.im>
16:05:08
!endmeeting