<@amoloney:fedora.im>
14:00:57
!startmeeting Fedora Council Bi-Weekly Meeting
<@meetbot:fedora.im>
14:00:58
Meeting started at 2026-07-29 14:00:57 UTC
<@meetbot:fedora.im>
14:00:58
The Meeting name is 'Fedora Council Bi-Weekly Meeting'
<@amoloney:fedora.im>
14:01:22
!topic Roll Call
<@pboy:fedora.im>
14:01:25
!hi
<@amoloney:fedora.im>
14:01:25
!hi
<@zodbot:fedora.im>
14:01:26
Aoife Moloney: Aoife Moloney (amoloney)
<@zodbot:fedora.im>
14:01:26
Peter Boy (ServerWG, Docs): Peter Boy (pboy)
<@shaunm:matrix.org>
14:01:29
!hi
<@churchyard:fedora.im>
14:02:06
!hi
<@zodbot:fedora.im>
14:02:13
mhroncok: Miro Hrončok (churchyard) - he / him / his or they / them / theirs
<@nimbinatus:matrix.org>
14:02:51
!hi
<@zodbot:fedora.im>
14:02:52
nimbinatus: Laura Santamaria (nimbinatus) - she / her / hers
<@t0xic0der:fedora.im>
14:03:00
!hi
<@zodbot:fedora.im>
14:03:01
Akashdeep Dhar / আকাশদীপ ধর: Akashdeep Dhar (t0xic0der) - he / him / his
<@amoloney:fedora.im>
14:04:20
I know we dont have Jef today, he is commuting during this meetings time
<@decathorpe:fedora.im>
14:04:23
!hi
<@zodbot:fedora.im>
14:04:24
Fabio Valentini 🌈: Fabio Valentini (decathorpe) - he / him / his
<@decathorpe:fedora.im>
14:04:47
(took me a while to find this room, element web updated itself and now the room list is unusable)
<@amoloney:fedora.im>
14:05:55
will kick off the agenda after another minute in case we have any more council members running late, but we have quorum i think for the meeting (I count 7 so far)
<@bookwar:fedora.im>
14:06:03
!hi
<@zodbot:fedora.im>
14:06:06
bookwar: Aleksandra Fedorova (bookwar) - she / her / hers
<@amoloney:fedora.im>
14:07:24
!topic Agenda
<@amoloney:fedora.im>
14:07:29
#558 - Fedora Forge Usage Policy
<@amoloney:fedora.im>
14:07:29
#460 - Re-licence fedora-logos
<@amoloney:fedora.im>
14:07:29
#410 - Abolish Fedora Contributor Agreement
<@amoloney:fedora.im>
14:07:29
Ticket Discussions:
<@amoloney:fedora.im>
14:07:29
Reminders and Announcements
<@amoloney:fedora.im>
14:07:29
Open Floor
<@amoloney:fedora.im>
14:07:29
<@amoloney:fedora.im>
14:07:29
Next Meeting Topics
<@amoloney:fedora.im>
14:07:29
#568 - Budget repo migration
<@amoloney:fedora.im>
14:07:44
!link https://discussion.fedoraproject.org/t/fedora-council-bi-weekly-meeting-agenda-22026-07-29/197800
<@amoloney:fedora.im>
14:07:50
Righteo, first topic
<@amoloney:fedora.im>
14:07:58
!topic Announcements/Reminders
<@amoloney:fedora.im>
14:08:30
Does anyone have any announcements or reminders they need bubbled up to council?
<@amoloney:fedora.im>
14:08:39
I dont have anything today, afaik
<@bookwar:fedora.im>
14:08:45
shaunm maybe :)
<@shaunm:matrix.org>
14:09:12
The public announcement of the role change goes live tomorrow, I think.
<@shaunm:matrix.org>
14:09:32
I suppose it's in public minutes now :)
<@bookwar:fedora.im>
14:10:08
sorry )
<@amoloney:fedora.im>
14:11:06
I look forward to things being officially official, in an official way
<@shaunm:matrix.org>
14:11:50
It's fine. We'd have done it yesterday, but we wanted to publish the Flock retro piece on the magazine first.
<@t0xic0der:fedora.im>
14:12:09
Likewise, welcome aboard, future Mindshare chair person ;P
<@amoloney:fedora.im>
14:12:45
With that being semi-announced, lets move to the ticket discussions. We have a few but hopefully we can make some progress on them
<@amoloney:fedora.im>
14:12:50
!topic Ticket Discussions
<@amoloney:fedora.im>
14:13:29
!topic Fedora Forge Usage Policy
<@amoloney:fedora.im>
14:13:56
!link https://forge.fedoraproject.org/council/tickets/issues/558
<@amoloney:fedora.im>
14:14:58
This is garnering some good conversation. Could we try to align on what we want this piece of work to be, make the edits and then repropose it?
<@bookwar:fedora.im>
14:15:25
I desribed some thougths in teh comments, but i might be a bit overenginnering. Can we do a quick poll for two items separately:
<@bookwar:fedora.im>
14:15:30
1) do you think we need the archiving close
<@bookwar:fedora.im>
14:15:31
2) do you think we need the notice period commitment
<@bookwar:fedora.im>
14:15:43
Just to check the mood in the room, not to decide yet
<@nimbinatus:matrix.org>
14:15:49
I think Timothée nailed it in saying that removing the word "automatically" would solve the issues, though
<@nimbinatus:matrix.org>
14:15:58
https://forge.fedoraproject.org/council/tickets/issues/558#issuecomment-1071357
<@amoloney:fedora.im>
14:16:44
nimbinatus: agreed, and I like Maxwells sentence edit too
<@bookwar:fedora.im>
14:17:11
I described some thoughts in the comments, but i might be a bit overengineering. Can we do a quick poll for two items separately:
<@amoloney:fedora.im>
14:17:50
the very last comment
<@decathorpe:fedora.im>
14:17:59
I think this?
<@decathorpe:fedora.im>
14:17:59
<@decathorpe:fedora.im>
14:17:59
> Perhaps the policy can explicitly state the Forge organization owners are responsible for archiving repos that are dormant or unmaintained in their respective orgs.
<@nimbinatus:matrix.org>
14:18:08
Ah, got it
<@amoloney:fedora.im>
14:18:10
Maxwell says "'d say that management of repos in organizations owned by an active group should be left up to the group's owners team. Perhaps the policy can explicitly state the Forge organization owners are responsible for archiving repos that are dormant or unmaintained in their respective orgs."
<@amoloney:fedora.im>
14:18:16
I like the sentence he proposed
<@churchyard:fedora.im>
14:19:04
I don't really understand how archiving repos saves resources. why does it matter?
<@bookwar:fedora.im>
14:19:24
I don't think this will work, because the initial archiving discussion was meant for situations when the owners of the org are not there/ We can add guildelines for owners additionally, but it is not the same situation
<@amoloney:fedora.im>
14:19:31
It doesnt save any resources
<@bookwar:fedora.im>
14:19:40
https://forge.fedoraproject.org/council/tickets/issues/558#issuecomment-1071667
<@pboy:fedora.im>
14:20:10
If is doesn't save ressources, why so eager to archive it?
<@pboy:fedora.im>
14:20:42
As long as the owning group is active, why not leave it to them?
<@nimbinatus:matrix.org>
14:21:08
>Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. The Infrastructure team reserves the right to automatically archive repositories that have seen no activity for 6 months.
<@nimbinatus:matrix.org>
14:21:08
>Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. Active Forge organization owners should archive repos as necessary. If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity for 6 months after trying to contact the organization owners.
<@nimbinatus:matrix.org>
14:21:08
to
<@nimbinatus:matrix.org>
14:21:08
So change from:
<@amoloney:fedora.im>
14:21:14
I like Maxwells comment because it puts the expectation explicitly on the owners to follow the expectation
<@nimbinatus:matrix.org>
14:21:15
to
<@nimbinatus:matrix.org>
14:21:15
So change from:
<@nimbinatus:matrix.org>
14:21:15
<@nimbinatus:matrix.org>
14:21:15
> Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. The Infrastructure team reserves the right to automatically archive repositories that have seen no activity for 6 months.
<@nimbinatus:matrix.org>
14:21:15
> Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. Active Forge organization owners should archive repos as necessary. If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity for 6 months after trying to contact the organization owners.
<@churchyard:fedora.im>
14:21:24
we probably want to develop some mechanism wrt. communicating an entire org is obsolete/etc. but it doe snot need to be automated.
<@nimbinatus:matrix.org>
14:21:27
> Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. Active Forge organization owners should archive repos as necessary. If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity for 6 months after trying to contact the organization owners.
<@nimbinatus:matrix.org>
14:21:27
> Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. The Infrastructure team reserves the right to automatically archive repositories that have seen no activity for 6 months.
<@nimbinatus:matrix.org>
14:21:27
<@nimbinatus:matrix.org>
14:21:27
<@nimbinatus:matrix.org>
14:21:27
So change from:
<@nimbinatus:matrix.org>
14:21:27
to
<@nimbinatus:matrix.org>
14:21:27
<@churchyard:fedora.im>
14:21:34
we probably want to develop some mechanism wrt. communicating an entire org is obsolete/etc. but it does not need to be automated.
<@decathorpe:fedora.im>
14:22:03
nimbinatus: I think this is a good compromise, and basically sidesteps all the open questions.
<@amoloney:fedora.im>
14:22:09
Im fine with the above edit, but with change from 6 months to 12
<@churchyard:fedora.im>
14:22:41
nimbinatus: I like your change, but would go even further: If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity, after trying to contact the organization owners.
<@nimbinatus:matrix.org>
14:23:01
So remove the timeframe?
<@churchyard:fedora.im>
14:23:16
entirely. this is about human communication, not about automated cleanups
<@amoloney:fedora.im>
14:23:17
I am also fine with no timeframe :D
<@nimbinatus:matrix.org>
14:23:37
I think the timeframe is mostly just to make it clearer for folks who need more guardrails.
<@bookwar:fedora.im>
14:23:43
"if needed" does a lot of heavy lifting there, but yeah, that kind puts it on Fedora Infra to be reasonable. And they usually are :)
<@bookwar:fedora.im>
14:24:00
"if needed" does a lot of heavy lifting there, but yeah, that kind of puts it on Fedora Infra to be reasonable. And they usually are :)
<@churchyard:fedora.im>
14:24:09
It acknowledges that it's up on them
<@decathorpe:fedora.im>
14:24:21
it's not as if this is an irreversible action, either. if the organization is still active, the owners should be able to un-archive a repo themselves, right?
<@amoloney:fedora.im>
14:24:38
Lets go with nimbinatus phrasing, without any timeline and we might just have to see what happens over time
<@nimbinatus:matrix.org>
14:24:46
The timeframe was in the original, so I kept it. Personally, I think providing *some* kind of timeframe is helpful, even if it's more along the lines of "Fedora Infra will start poking at an inactive repo in 6 months just so you know they'll ask if it's active"
<@nimbinatus:matrix.org>
14:25:22
Otherwise, some folks may get territorial 🤷♀️ But I really don't have a strong opinion here
<@bookwar:fedora.im>
14:25:51
I would prefer no timeline. Gives Infra folks some freedom
<@churchyard:fedora.im>
14:25:57
I'd rather not make any promisses/add work to infra folks. If they want to, they can poke. They don't have to
<@nimbinatus:matrix.org>
14:26:02
Yup, it's a living document. We can always come back to change it if we realize we need a timeline :)
<@pboy:fedora.im>
14:26:04
I prefer no timeframe.
<@nimbinatus:matrix.org>
14:26:39
<@nimbinatus:matrix.org>
14:26:39
to
<@nimbinatus:matrix.org>
14:26:39
<@nimbinatus:matrix.org>
14:26:39
>Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. The Infrastructure team reserves the right to automatically archive repositories that have seen no activity for 6 months.
<@nimbinatus:matrix.org>
14:26:39
<@nimbinatus:matrix.org>
14:26:39
New change from:
<@nimbinatus:matrix.org>
14:26:39
>Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. Active Forge organization owners should archive repos as necessary. If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity after trying to contact the organization owners.
<@churchyard:fedora.im>
14:26:41
and then if I am dissatisfied that there are dead repos about X, I can open an infra ticket to ask them to poke
<@bookwar:fedora.im>
14:26:54
1. do you think we need the archiving clause
<@churchyard:fedora.im>
14:26:57
(X as in whatever, not as in Twitter)
<@pbokoc:fedora.im>
14:27:32
!hi
<@pbokoc:fedora.im>
14:27:35
Sorry, I'm here now
<@jflory7:fedora.im>
14:27:52
!hi
<@jflory7:fedora.im>
14:27:55
Sorry, I'm here now too
<@churchyard:fedora.im>
14:28:09
Don't be sorry for being here, we are glad to have you :)
<@churchyard:fedora.im>
14:28:19
Don't be sorry for being here, we are glad to have you :) (both)
<@jflory7:fedora.im>
14:28:31
I am having the same problem TBH ☹️ Anyways, I'll start reading back and catching up…
<@nimbinatus:matrix.org>
14:30:09
(except s = a, but yes :p
<@nimbinatus:matrix.org>
14:30:12
(except s = a, but yes :p )
<@amoloney:fedora.im>
14:30:21
yeah I am v bad with typos :D
<@nimbinatus:matrix.org>
14:30:30
:D just being silly
<@amoloney:fedora.im>
14:31:45
Ok I think I can put an agreed statement on that and move to our next sticky topic?
<@amoloney:fedora.im>
14:31:55
!agreed The Fedora Council propose to make an edit to the archiving clause to read 'Archiving: Projects that are no longer actively maintained should be archived (marked as read-only) to signal their status to the community. Active Forge organization owners should archive repos as necessary. If needed (e.g., in the case of an inactive organization), the Infrastructure team reserves the right to archive repositories that have seen no activity after trying to contact the organization owners.' Once this edit is in the document, the proposal will go through the policy change policy of a 2 week community feedback period. If no grievous issues are found, the policy will become official. We intend to start this process on Thursday, 30 July 2026
<@amoloney:fedora.im>
14:32:32
!topic Abolish Fedora Contributor Agreement
<@amoloney:fedora.im>
14:32:35
!link https://forge.fedoraproject.org/council/tickets/issues/460
<@jflory7:fedora.im>
14:32:36
I'm all caught up and agree with everything y'all said 👍️
<@jflory7:fedora.im>
14:32:44
(on the Forge policy)
<@jflory7:fedora.im>
14:32:52
nimbinatus++
<@zodbot:fedora.im>
14:32:53
Sorry, could not get info from FASJSON (code 401)
<@jflory7:fedora.im>
14:33:02
Feel better soon, FreeIPA
<@amoloney:fedora.im>
14:33:19
This one - Ive proposed we close it out. I strongly believe we cannot work on this, even if we wanted to as I dont know who would have the time to do all the necessary due diligence this would need
<@decathorpe:fedora.im>
14:33:31
ack
<@nimbinatus:matrix.org>
14:33:38
Wait, is that the right ticket?
<@amoloney:fedora.im>
14:33:45
aw crap its not
<@nimbinatus:matrix.org>
14:34:01
ok, just making sure I'm looking at the right one before I say yes to close it out 😂
<@amoloney:fedora.im>
14:34:04
!link https://forge.fedoraproject.org/council/tickets/issues/410
<@decathorpe:fedora.im>
14:34:08
!forge issue council tickets 410
<@zodbot:fedora.im>
14:34:09
● **Last Updated:** 23 hours ago
<@zodbot:fedora.im>
14:34:09
**council/tickets #410** (https://forge.fedoraproject.org/council/tickets/issues/410):**Abolish Fedora Project Contributor Agreement**
<@zodbot:fedora.im>
14:34:09
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
14:34:09
<@zodbot:fedora.im>
14:34:09
● **Opened:** 3 years ago by ref
<@jflory7:fedora.im>
14:34:13
+1 to close as deferred
<@jflory7:fedora.im>
14:34:26
OMG wow, need to commit this alias to my brain memory
<@bookwar:fedora.im>
14:34:28
for the record, I am +1 on just closing the https://forge.fedoraproject.org/council/tickets/issues/460 too
<@nimbinatus:matrix.org>
14:34:39
+1 to close and defer as I replied in the ticket :)
<@amoloney:fedora.im>
14:34:46
(me too bookwar , me too)
<@amoloney:fedora.im>
14:35:15
ok new proposal - close out both #460 and #410?
<@churchyard:fedora.im>
14:35:17
I abstain -- I admit I have not been following those two
<@jflory7:fedora.im>
14:35:20
Does anyone need time to process/review/discuss #410, or can we resolve and move forward?
<@decathorpe:fedora.im>
14:35:51
I'm OK to close #410 as inactionable, but I haven't had enough time to read up on #460
<@jflory7:fedora.im>
14:35:51
!info This topic is now tying both #460 and #410 together as collectively closing as `wontfix` / `deferred`
<@amoloney:fedora.im>
14:35:51
Ive given myself 2 weeks to try process it and I cannot reach a conclusion on what to even do
<@pboy:fedora.im>
14:36:25
I don't think it is good to abolish without any replacement.
<@jflory7:fedora.im>
14:36:29
TL;DNR: We got advice from Legal a year or so ago(?) that basically relicensing them is not really likely
<@pboy:fedora.im>
14:36:39
I don't think it is NOT good to abolish without any replacement.
<@jflory7:fedora.im>
14:36:45
We are agreeing to keep the status quo with FPCA. No abolishing, no replacing
<@smoliicek:fedora.im>
14:36:55
i just know how much hastle it would be from the infra side, since so many stuff is tied to the fcpa being signed...
<@jflory7:fedora.im>
14:37:07
We may revisit one day in the future because the FPCA has some holes in it, but we are deferring that future conversation to Some Day Later™
<@jflory7:fedora.im>
14:37:26
that too
<@jflory7:fedora.im>
14:37:29
It would be a big lift
<@jflory7:fedora.im>
14:37:33
Technically speaking
<@smoliicek:fedora.im>
14:37:49
not just infra though, elections are one that also come to mind
<@jflory7:fedora.im>
14:38:38
Fedora Verified/whatever-we-want-to-call-it was the ideal solution for the election eligibility thing, but we decided in April or so that we have enough spinning plates in the air that we need to stop spinning before trying to do something big like Fedora Verified/whatever-other-name-fits
<@jflory7:fedora.im>
14:38:53
Anyways, kind of a tangent
<@jflory7:fedora.im>
14:38:57
Aoife Moloney: What next here?
<@amoloney:fedora.im>
14:39:12
working on the proposal statement 2 mis
<@amoloney:fedora.im>
14:40:24
!proposal The Council agreed to close out both tickets #410 and #460. The council do not have capacity right now to investigate a replacement for the FPCA, or do due diligence on what dependencies will be affected with the abolishment of the FPCA, as is requested by ticket #410. The Council wishes to adhere to the advice provided by Red Hat legal regarding ticket #460 requesting to re-licence fedora-logos that this action is not possible for Council to take. These tickets are closed as deferred/wont-fix
<@amoloney:fedora.im>
14:41:04
^^ edits welcome on this proposal statement
<@jflory7:fedora.im>
14:41:17
+1, although wasn't sure if others felt ready to vote on #460
<@decathorpe:fedora.im>
14:41:39
eh, "lawyer says no" is sufficient reason for me :)
<@jflory7:fedora.im>
14:41:44
(probably better if people write `+1` / `+0` / `-1` because emoji reactions won't get into the meeting notes/logs)
<@bookwar:fedora.im>
14:41:48
I like it. This is actually much better than "closing as Won'tFix" as I would write :)
<@decathorpe:fedora.im>
14:41:48
+1
<@bookwar:fedora.im>
14:41:58
+1
<@pbokoc:fedora.im>
14:41:59
We've been discussing 460 for a while, too, let's finally put it down
<@pbokoc:fedora.im>
14:42:02
+1
<@nimbinatus:matrix.org>
14:42:06
+1
<@pboy:fedora.im>
14:42:16
+1
<@amoloney:fedora.im>
14:42:50
+1 for posterity :)
<@t0xic0der:fedora.im>
14:42:59
+1
<@amoloney:fedora.im>
14:43:03
!agreed The Council agreed to close out both tickets #410 and #460. The council do not have capacity right now to investigate a replacement for the FPCA, or do due diligence on what dependencies will be affected with the abolishment of the FPCA, as is requested by ticket #410. The Council wishes to adhere to the advice provided by Red Hat legal regarding ticket #460 requesting to re-licence fedora-logos that this action is not possible for Council to take. These tickets are closed as deferred/wont-fix
<@jflory7:fedora.im>
14:43:19
2-for-1, nice
<@amoloney:fedora.im>
14:43:24
Small note - thank you all for being so engaged :)
<@amoloney:fedora.im>
14:43:29
anyway, next topic
<@zodbot:fedora.im>
14:43:38
Sorry, could not get info from FASJSON (code 401)
<@amoloney:fedora.im>
14:44:09
!topic Fedora Budget Repo Migration
<@amoloney:fedora.im>
14:44:13
!link https://forge.fedoraproject.org/council/tickets/issues/568
<@jflory7:fedora.im>
14:44:31
I think this one is a `!action @jflory7` but also likely is relevant for shaunm too
<@jflory7:fedora.im>
14:44:49
Unless anyone has opinions about private financial records/data being preserved from Pagure to Forgejo
<@amoloney:fedora.im>
14:44:50
Justin Wheeler: is this just more an ack from council that budget lives in council repo?
<@amoloney:fedora.im>
14:45:17
Will they still be available on pagure for those who have the right perms as read-only?
<@jflory7:fedora.im>
14:45:20
I think this is mostly that Pagure goes to a final resting place at the end of the week and whatever we don't move now will be hard later
<@decathorpe:fedora.im>
14:45:29
migrating all the public things and letting the old personal data be deleted sounds good to me. though note that migrating PRs does only preserve them, they won't actually be mergeable as-is.
<@jflory7:fedora.im>
14:45:37
Honestly, I'd like all of the private issues to simply go away forever and be purged
<@jflory7:fedora.im>
14:45:45
I cannot think of any good reason for keeping them
<@bookwar:fedora.im>
14:45:54
I would drop the private issues completely
<@amoloney:fedora.im>
14:45:55
well I suppose theres likely personal financial stuff there so +1 to that
<@jflory7:fedora.im>
14:45:56
There might be a sliver of insight there, but I guess I could clone the issues repo and call it a day?
<@jflory7:fedora.im>
14:46:06
I actually have no idea how private issues work with the issues repo on Pagure
<@amoloney:fedora.im>
14:46:13
and I am +1 to budget repo living under counci;
<@bookwar:fedora.im>
14:46:14
Keep and migrate the repo, and archive immediately.
<@jflory7:fedora.im>
14:46:28
Well, I do think the budget.fp.o source code lives there
<@nimbinatus:matrix.org>
14:46:35
+1 to dropping private issues completely, along with all of the private data
<@jflory7:fedora.im>
14:46:37
It was Bex's ledger workflow, and I do know shaunm uses ledger already
<@t0xic0der:fedora.im>
14:46:40
Is it even maintained?
<@jflory7:fedora.im>
14:46:44
Both me and Marie were not ledger people
<@jflory7:fedora.im>
14:46:49
See above
<@t0xic0der:fedora.im>
14:47:00
Gotcha
<@shaunm:matrix.org>
14:47:16
I actually stopped using ledger. Just using the big magic spreadsheet now.
<@jflory7:fedora.im>
14:47:21
I always _wanted_ to get budget data from 2020 to present into there. And we do have that data in Google Sheets
<@jflory7:fedora.im>
14:47:25
So many Google Sheets
<@bookwar:fedora.im>
14:47:27
Not going to argue about archiving. It was just an offer. If someone wants to keep it for something, even just to think a little bit more about it - fine by me
<@amoloney:fedora.im>
14:47:37
!proposal The Fedora Budget repo will be migrated to the Council space on Fedora Forge. All private issues on pagure can be deleted and will not migrate over.
<@amoloney:fedora.im>
14:47:45
Justin Wheeler: want to add anything more?
<@t0xic0der:fedora.im>
14:47:48
Less misleading that way...
<@t0xic0der:fedora.im>
14:47:48
Then it just makes sense to point the budget fpo to a static wiki page
<@decathorpe:fedora.im>
14:48:00
+1
<@jflory7:fedora.im>
14:48:24
Happy to defer for shaunm to decide what to do there. I _do_ think there is historical value of publishing the old data, but I literally have zero ideas how it is built/published other than probably `asciibinder` which was the pre-Antora tool we/Bex experimented with in 2017
<@shaunm:matrix.org>
14:48:27
Sorry, there was a lot to catch up on in the issue. I agree with purging the private issues, migrating the repo for historical interest, archiving it. I also think we should take down the website, unless it's going to get updates.
<@jflory7:fedora.im>
14:48:32
+1
<@t0xic0der:fedora.im>
14:48:47
+1
<@bookwar:fedora.im>
14:48:47
+1 for proposal
<@amoloney:fedora.im>
14:48:53
Lets agree on the repos new home and then let shaunm nuke it or revive it, whatever he sees fit
<@nimbinatus:matrix.org>
14:49:39
+1
<@pbokoc:fedora.im>
14:49:55
+1
<@pboy:fedora.im>
14:49:58
+1
<@churchyard:fedora.im>
14:49:58
Generally, I don't like losing data. But it's not mine data, so :/
<@churchyard:fedora.im>
14:50:06
Generally, I don't like losing data. But it's not my data, so :/
<@jflory7:fedora.im>
14:50:15
Lots of IBANs 😛
<@jflory7:fedora.im>
14:50:27
And PayPal emails
<@bookwar:fedora.im>
14:50:29
There is a lot of pernal info in that particular chunk of data though. I think it is a good one to lose
<@churchyard:fedora.im>
14:50:34
lots of GDPR :) nuke it I guess :)
<@bookwar:fedora.im>
14:50:35
There is a lot of personal info in that particular chunk of data though. I think it is a good one to lose
<@churchyard:fedora.im>
14:50:35
+1
<@amoloney:fedora.im>
14:50:51
!agreed The Fedora Budget repo will be migrated to the Council space on Fedora Forge. All private issues on pagure can be deleted and will not migrate over.
<@amoloney:fedora.im>
14:51:01
YAAAY We reached the agenda end!!!!!
<@jflory7:fedora.im>
14:51:09
Am I dreaming? 😛
<@jflory7:fedora.im>
14:51:18
Or is it that Aoife is back to running Council meetings?
<@nimbinatus:matrix.org>
14:51:21
Look at us just marching right through :p
<@decathorpe:fedora.im>
14:51:21
ha
<@amoloney:fedora.im>
14:51:39
We are literally on Next meeting agenda and open floor 😂😂
<@t0xic0der:fedora.im>
14:51:41
Aoife Moloney++
<@zodbot:fedora.im>
14:51:42
Sorry, could not get info from FASJSON (code 401)
<@amoloney:fedora.im>
14:51:51
!topic Next Meeting Agenda and Open Floor
<@bookwar:fedora.im>
14:52:12
What are the next steps for Privacy policy discussion?
<@amoloney:fedora.im>
14:52:13
(Ive merged those to make it to the end for real)
<@amoloney:fedora.im>
14:52:37
is this the conflict of interest?
<@bookwar:fedora.im>
14:52:46
not privacy, sorry, the conflict of interest
<@amoloney:fedora.im>
14:52:53
I need to action myself to do the eedit and start the process for the forge use policy too
<@bookwar:fedora.im>
14:53:14
ok, so you will be the one working on it. Thanks a lot )
<@jflory7:fedora.im>
14:53:35
Given the decent amount of action items coming out of this meeting already, I wouldn't mind deferring the Conflict of Interest Policy topic to next meeting. I haven't had a chance to go through the Fedora Discussion post yet
<@churchyard:fedora.im>
14:53:38
I think I like the one sentence policy about decisions involving humans betterthan the entire policy
<@amoloney:fedora.im>
14:53:41
I like your proposal to contain them to a decision-making aid for private or semi-private decisions for governance groups to use if they need to
<@jflory7:fedora.im>
14:53:42
So, some more time to refresh/review would be helpful
<@churchyard:fedora.im>
14:53:43
I think I like the one sentence policy about decisions involving humans better than the entire policy
<@amoloney:fedora.im>
14:54:17
lets keep it open for feedback for another week?
<@bookwar:fedora.im>
14:54:44
yeah, i didn't want to have the big discussion right now, just more of a - is there anything else expected at this point or have i done my part for now :)
<@jflory7:fedora.im>
14:54:52
misc also identified in #pride:fedoraproject.org some things that may warrant a closer look and caution about revealing people's personal situations in an uncomfortable way
<@amoloney:fedora.im>
14:55:03
to be clear - that draft is only in a drafted state now. its not in the policy change process at_all
<@jflory7:fedora.im>
14:55:14
useful clarification
<@jflory7:fedora.im>
14:55:36
Does it have to be next week, or could we aim for the next Council meeting as a decision point for the policy change policy?
<@jflory7:fedora.im>
14:55:55
Knowing fully well that we are likely to get feedback in the two week public comments period which we may want to incorporate into revisions
<@amoloney:fedora.im>
14:56:09
we can punt it to next meeting. Technically we are fulfilling the topic by identifying it as a nect meeting topic :)
<@jflory7:fedora.im>
14:56:35
+1 for Conflict of Interest Policy for next meeting. Plus, I _think_ we would have Jef back by that time too, anyways
<@amoloney:fedora.im>
14:56:47
Does anyone want to own redrafting? Or will I take it? I think we need a v.2 soon from the feedback so far as well
<@bookwar:fedora.im>
14:56:53
I would prefer to have it updated on discourse before we talk about it in the meeting again
<@jflory7:fedora.im>
14:57:19
I don't have capacity for redrafting
<@amoloney:fedora.im>
14:57:51
Im happy to take it if theres no other takers
<@bookwar:fedora.im>
14:58:01
Also, this is not the most urgent issue, from my perspective. So if something else takes priority over it - it should be ok.
<@jflory7:fedora.im>
14:58:07
TBH, you seem to be doing well with it so far Aoife Moloney
<@amoloney:fedora.im>
14:58:18
I need to do the action statements anyway so whats another one ;)
<@jflory7:fedora.im>
14:58:29
Also, thanks for helping refresh the ticket and getting this one done, it is… old and overdue
<@churchyard:fedora.im>
14:59:13
quick, drop a nasty vote bomb about AI, we have 1 minute :D
<@decathorpe:fedora.im>
14:59:25
I wanted to note something very short for Open Floor - we have an open issue where FESCo is collecting info about potentially updating the "responsibilities of the FESCo council rep" docs with more actionable information (fesco/tickets#3613). if Council members have any input for this topic, a view from that side of things would be appreciated too :)
<@bookwar:fedora.im>
14:59:36
FESCo did the drop for this week
<@bookwar:fedora.im>
14:59:42
No more drops allowed
<@churchyard:fedora.im>
14:59:50
what was it?
<@bookwar:fedora.im>
15:00:21
I was referring to the change discussion about change process :)
<@churchyard:fedora.im>
15:00:22
https://forge.fedoraproject.org/fesco/tickets/issues/3613
<@amoloney:fedora.im>
15:00:24
!action @amoloney to make the edit to Fedora Forge use policy and propose it through the policy change policy on Thursday 30 July 2026
<@jflory7:fedora.im>
15:00:24
Oh nice
<@jflory7:fedora.im>
15:00:55
I think that is really worth doing, and we can link to the role page/section from the Council docs too so it is visible
<@amoloney:fedora.im>
15:01:04
!action @amoloney to refraft the Conflict of Interest guidelines to include feedback gathered so far and repost to discourse before next council meeting on Aug 12 2026
<@amoloney:fedora.im>
15:01:33
!action All council members to review and provide feedback on FESCo ticket for FESCo rep responsibilities
<@jflory7:fedora.im>
15:01:45
!link https://forge.fedoraproject.org/fesco/tickets/issues/3613
<@amoloney:fedora.im>
15:01:47
everyone gets a job for the last one :)
<@jflory7:fedora.im>
15:01:55
Seems fair enough 🙂
<@amoloney:fedora.im>
15:02:03
and with that, thank you all very much for todays meeting!!
<@amoloney:fedora.im>
15:02:07
!endmeeting
<@nimbinatus:matrix.org>
15:02:10
yay! you get a job, and you get a job, and *you* get a job
<@zodbot:fedora.im>
15:02:19
Sorry, could not get info from FASJSON (code 401)
<@zodbot:fedora.im>
15:02:21
Sorry, could not get info from FASJSON (code 401)
<@churchyard:fedora.im>
15:02:24
no cookies
<@decathorpe:fedora.im>
15:02:25
oh the bots are all sad
<@churchyard:fedora.im>
15:02:29
bye :)
<@amoloney:fedora.im>
15:02:30
goshdangit why zodbot
<@amoloney:fedora.im>
15:02:40
!endmeeting
<@amoloney:fedora.im>
15:02:58
please
<@nimbinatus:matrix.org>
15:03:04
So, last time I had to set a topic then immediately did endmeeting
<@nimbinatus:matrix.org>
15:03:10
to get it to work this week
<@amoloney:fedora.im>
15:03:23
!topic End this Eternal Meeting, please bot
<@nimbinatus:matrix.org>
15:03:24
it's like the keyword doesn't always trigger any longer
<@amoloney:fedora.im>
15:03:29
!endmeeting
<@pbokoc:fedora.im>
15:03:40
RELEASE ME!
<@conan_kudo:matrix.org>
15:03:45
!endmeeting
<@decathorpe:fedora.im>
15:03:58
no luck
<@jflory7:fedora.im>
15:04:01
Meet Bot: endmeeting
<@bookwar:fedora.im>
15:04:27
We were to good with the agenda so now we are punished for it
<@nimbinatus:matrix.org>
15:04:27
!endmeeting
<@amoloney:fedora.im>
15:04:29
you used up your magic wish last time Neal Gompa (Fedora)
<@t0xic0der:fedora.im>
15:04:33
Aight, heading to bed now, see ya!
<@jflory7:fedora.im>
15:04:52
This is the time when I would normally page nirik or Aurélien B for Matrix bot help
<@amoloney:fedora.im>
15:05:11
!topic This meeting is over, we just cant get the bots to obey the humans anymore to end it
<@nimbinatus:matrix.org>
15:05:20
😂
<@nimbinatus:matrix.org>
15:05:25
!endmeeting
<@nimbinatus:matrix.org>
15:05:34
oh come on meetbot
<@nirik:matrix.scrye.com>
15:05:36
I can look, I am in a meeting too.... please hang on
<@decathorpe:fedora.im>
15:05:55
the way things are going, we are all going to be stuck in three meetings
<@nimbinatus:matrix.org>
15:05:56
(we're just trolling the bot; please don't take our silliness as a note on you!)
<@conan_kudo:matrix.org>
15:06:01
if it helps, it seems id.fp.o is hanging on chat.fp.o login
<@conan_kudo:matrix.org>
15:06:12
I can't get into my other account 😅
<@amoloney:fedora.im>
15:06:28
shall we have a competition for the silliest topic names?
<@nimbinatus:matrix.org>
15:06:34
hmm...
<@nimbinatus:matrix.org>
15:06:38
!topic !endmeeting
<@nimbinatus:matrix.org>
15:06:44
bugger
<@nimbinatus:matrix.org>
15:07:01
!topic endmeeting
<@nimbinatus:matrix.org>
15:07:21
!endmeeting !topic
<@nimbinatus:matrix.org>
15:07:21
!endmeeting !topic
<@decathorpe:fedora.im>
15:07:25
the aurelien-bot summary is going to be funny for this one
<@jflory7:fedora.im>
15:07:58
The Fedora Council concludes the meeting aboard the Titantic, as we sail across the Atlantic Ocean.
<@conan_kudo:matrix.org>
15:08:05
!endmeeting
<@nimbinatus:matrix.org>
15:08:08
!topic Meet Bot The Meeting Topic is now !endmeeting
<@amoloney:fedora.im>
15:08:23
!end
<@amoloney:fedora.im>
15:08:28
!fin
<@amoloney:fedora.im>
15:08:32
!bye
<@conan_kudo:matrix.org>
15:08:33
!die
<@nimbinatus:matrix.org>
15:08:38
we're having way too much fun now
<@nirik:matrix.scrye.com>
15:08:39
can you all stop please?
<@nimbinatus:matrix.org>
15:08:44
sorry
<@amoloney:fedora.im>
15:08:50
sorry
<@nirik:matrix.scrye.com>
15:12:15
I'm trying to stop it, but it's a mess...
<@nirik:matrix.scrye.com>
15:21:47
!endmeeting
<@nirik:matrix.scrye.com>
15:22:41
!endmeeting
<@niknikovsky:fedora.im>
15:24:41
!endmeeting
<@amoloney:fedora.im>
15:26:25
Sorry if our messing made it worse Kevin :(
<@nirik:matrix.scrye.com>
15:26:52
no, doesn't matter really...
<@nirik:matrix.scrye.com>
15:26:57
I'm just cranky
<@niknikovsky:fedora.im>
15:50:47
!endmeeting
<@niknikovsky:fedora.im>
15:51:05
!topic testing
<@niknikovsky:fedora.im>
15:51:09
!endmeeting
<@niknikovsky:fedora.im>
15:51:14
!help
<@niknikovsky:fedora.im>
15:51:14
!help
<@zodbot:fedora.im>
15:51:14
● `!forge <subcommand> [...]` - Query information from Fedora Forge
<@zodbot:fedora.im>
15:51:14
● `!version ` - return information about this bot
<@zodbot:fedora.im>
15:51:14
● `!help [commandname]` - list commands
<@zodbot:fedora.im>
15:51:14
● `!help [commandname]` - list commands
<@zodbot:fedora.im>
15:51:14
● `!version ` - return information about this bot
<@zodbot:fedora.im>
15:51:14
● `!pagureissue <project> <issue_id>` - return a pagure issue
<@zodbot:fedora.im>
15:51:14
● `!bug <bug_id>` - return a bugzilla bug
<@zodbot:fedora.im>
15:51:14
● `!infra <subcommand> [...]` - Fedora Infrastructure commands
<@zodbot:fedora.im>
15:51:14
● `!user <subcommand> [...]` - Get information about Fedora Accounts users
<@zodbot:fedora.im>
15:51:14
● `!forge <subcommand> [...]` - Query information from Fedora Forge
<@zodbot:fedora.im>
15:51:14
● `!whoowns <package>` - Retrieve the owner of a given package
<@zodbot:fedora.im>
15:51:14
● `!group <subcommand> [...]` - Query information about Fedora Accounts groups
<@zodbot:fedora.im>
15:51:14
● `!user <subcommand> [...]` - Get information about Fedora Accounts users
<@zodbot:fedora.im>
15:51:14
● `!infra <subcommand> [...]` - Fedora Infrastructure commands
<@zodbot:fedora.im>
15:51:14
● `!bug <bug_id>` - return a bugzilla bug
<@zodbot:fedora.im>
15:51:14
● `!cookie <subcommand> [...]` - Commands for the cookie system
<@zodbot:fedora.im>
15:51:14
● `!cookie <subcommand> [...]` - Commands for the cookie system
<@zodbot:fedora.im>
15:51:14
● `!group <subcommand> [...]` - Query information about Fedora Accounts groups
<@zodbot:fedora.im>
15:51:14
● `!whoowns <package>` - Retrieve the owner of a given package
<@zodbot:fedora.im>
15:51:14
● `!pagureissue <project> <issue_id>` - return a pagure issue
<@zodbot:fedora.im>
15:51:14
● `!cookie <subcommand> [...]` - Commands for the cookie system
<@zodbot:fedora.im>
15:51:14
● `!help [commandname]` - list commands
<@zodbot:fedora.im>
15:51:14
● `!version ` - return information about this bot
<@zodbot:fedora.im>
15:51:14
● `!pagureissue <project> <issue_id>` - return a pagure issue
<@zodbot:fedora.im>
15:51:14
● `!forge <subcommand> [...]` - Query information from Fedora Forge
<@zodbot:fedora.im>
15:51:14
● `!whoowns <package>` - Retrieve the owner of a given package
<@zodbot:fedora.im>
15:51:14
● `!group <subcommand> [...]` - Query information about Fedora Accounts groups
<@zodbot:fedora.im>
15:51:14
● `!user <subcommand> [...]` - Get information about Fedora Accounts users
<@zodbot:fedora.im>
15:51:14
● `!infra <subcommand> [...]` - Fedora Infrastructure commands
<@zodbot:fedora.im>
15:51:14
● `!cookie <subcommand> [...]` - Commands for the cookie system
<@zodbot:fedora.im>
15:51:14
● `!bug <bug_id>` - return a bugzilla bug
<@zodbot:fedora.im>
15:51:14
● `!infra <subcommand> [...]` - Fedora Infrastructure commands
<@zodbot:fedora.im>
15:51:14
● `!user <subcommand> [...]` - Get information about Fedora Accounts users
<@zodbot:fedora.im>
15:51:14
● `!group <subcommand> [...]` - Query information about Fedora Accounts groups
<@zodbot:fedora.im>
15:51:14
● `!whoowns <package>` - Retrieve the owner of a given package
<@zodbot:fedora.im>
15:51:14
● `!forge <subcommand> [...]` - Query information from Fedora Forge
<@zodbot:fedora.im>
15:51:14
● `!pagureissue <project> <issue_id>` - return a pagure issue
<@zodbot:fedora.im>
15:51:14
● `!version ` - return information about this bot
<@zodbot:fedora.im>
15:51:14
● `!help [commandname]` - list commands
<@zodbot:fedora.im>
15:51:14
● `!bug <bug_id>` - return a bugzilla bug
<@niknikovsky:fedora.im>
15:51:41
nirik: can you try to end ?
<@nirik:matrix.scrye.com>
15:51:53
That is a differnet bot... I am working on it.
<@niknikovsky:fedora.im>
15:52:07
the meeting bot works I think
<@abompard:fedora.im>
15:52:18
!endmeeting
<@niknikovsky:fedora.im>
15:52:29
i think only the chair can do it
<@niknikovsky:fedora.im>
15:52:29
idk
<@abompard:fedora.im>
15:52:34
`sudo` !endmeeting
<@niknikovsky:fedora.im>
15:52:47
i wonder if it thinks that no meeting is on
<@niknikovsky:fedora.im>
15:52:59
!startmeeting test
<@meetbot:fedora.im>
15:53:00
Meeting already in progress
<@niknikovsky:fedora.im>
15:53:03
ok good
<@niknikovsky:fedora.im>
15:53:06
!endmeeting
<@zodbot:fedora.im>
15:53:33
Sorry, could not get info from FASJSON (code 401)
<@niknikovsky:fedora.im>
15:53:48
wdym unauthorized
<@farchord:fedora.im>
15:54:31
guessing something in the fedora infra is unavailable
<@nirik:matrix.scrye.com>
15:55:12
yes, and we are working on it. :) Just poking it isn't helping us much...
<@abompard:fedora.im>
16:04:54
please try endmeeting now
<@abompard:fedora.im>
16:04:58
!endmeeting