Fedora Budget repo migration

pbokoc commented

2026-05-11 14:24:51 +00:00

Owner

Summary

We should consider what to do with the old Fedora Budget repo.

Background

I was combing through unmigrated repos on Pagure and came across this one: https://pagure.io/fedora-budget. I'm wondering if we want to migrate it and either archive it and keep it for historical reasons, or possibly even revive it, either now or at some point in the future.

Details

The output is still being published on https://budget.fedoraproject.org/budget/docs/index.html, so if we don't want to use this anymore, we might want to take it down, because as it is it looks a bit silly when the latest info is from half a decade ago. Is there some other way Fedora Project publishes budget stats? Are there any legal requirements around this?

Summary

Why does this form have two "Summary" fields? :-D

### Summary We should consider what to do with the old Fedora Budget repo. ### Background I was combing through unmigrated repos on Pagure and came across this one: https://pagure.io/fedora-budget. I'm wondering if we want to migrate it and either archive it and keep it for historical reasons, or possibly even revive it, either now or at some point in the future. ### Details The output is still being published on https://budget.fedoraproject.org/budget/docs/index.html, so if we don't want to use this anymore, we might want to take it down, because as it is it looks a bit silly when the latest info is from half a decade ago. Is there some other way Fedora Project publishes budget stats? Are there any legal requirements around this? ### Summary Why does this form have two "Summary" fields? :-D

pbokoc added the

labels

2026-07-11 03:02:12 +00:00

jflory7 commented

2026-07-11 03:03:29 +00:00

Owner

+1 to live under the Council. But does anyone know how or where the site is actually deployed? I never figured out how budget.fedoraproject.org is actually deployed.

+1 to live under the Council. But does anyone know how or where the site is actually deployed? I never figured out how `budget.fedoraproject.org` is actually deployed.

jflory7 commented

2026-07-11 03:04:33 +00:00

Owner

Ouch, I also just noticed there are a ton of private issues on that repository… this was the repo where the FCA used to handle reimbursements and track spending.

Ouch, I also just noticed there are a _ton_ of private issues on that repository… this was the repo where the FCA used to handle reimbursements and track spending.

amoloney added the

Next Meeting

label

2026-07-27 16:53:19 +00:00

amoloney commented

2026-07-27 16:57:30 +00:00

Owner

Lets have a quick discussion on this at the next meeting. If those private tickets remain on pagure as read-only as an intermediary step then Im fine with that.

jflory7 commented

2026-07-27 18:45:18 +00:00

Owner

@amoloney wrote in #568 (comment):

If those private tickets remain on pagure as read-only as an intermediary step then Im fine with that.

After thinking about it, I am in favor of migrating the public website source code, the 33 public issues, and 24 public PRs to our Forgejo organization but leaving the Pagure private issues there to be purged/deleted.

The private issues primarily include PII data like mailing addresses and occasionally personal banking information from when reimbursements were processed in that repo. The last actual use of this repo for reimbursements seems to be in 2023. If it were me and my data (oops my data from 2018 is there 🙂), I would like to see it deleted, not carried through in perpetuity until some data leak/hack accidentally exposes it. (I am not saying that would happen, but also, you cannot get in trouble for exposing data you literally don't have.)

@amoloney wrote in https://forge.fedoraproject.org/council/tickets/issues/568#issuecomment-1070414: > If those private tickets remain on pagure as read-only as an intermediary step then Im fine with that. After thinking about it, I am in favor of migrating the public website source code, the 33 public issues, and 24 public PRs to our Forgejo organization but leaving the Pagure private issues there to be purged/deleted. The private issues primarily include PII data like mailing addresses and occasionally personal banking information from when reimbursements were processed in that repo. The last actual use of this repo for reimbursements seems to be in 2023. If it were me and my data (oops my data from 2018 is there 🙂), I would like to see it deleted, not carried through in perpetuity until some data leak/hack accidentally exposes it. (I am not saying that _would_ happen, but also, you cannot get in trouble for exposing data you literally don't have.)

amoloney commented

2026-07-30 11:28:42 +00:00

Owner

As per the council meeting agreement[1] and ack from the FCA(s)*, the Fedora Budget repo will be migrated from pagure to fedora forge and live under Council org. All private issues on pagure will be deleted and not migrate over.

*We had the luxury of having both current and incoming FCA at the meeting to discuss this with and reach a conclusion :)

[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-29/fedora-council-bi-weekly-meeting.2026-07-29-14.00.html

As per the council meeting agreement[1] and ack from the FCA(s)*, the Fedora Budget repo will be migrated from pagure to fedora forge and live under Council org. All private issues on pagure will be deleted and not migrate over. *We had the luxury of having both current and incoming FCA at the meeting to discuss this with and reach a conclusion :) [1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-29/fedora-council-bi-weekly-meeting.2026-07-29-14.00.html

amoloney closed this issue

2026-07-30 11:28:43 +00:00

Rows
Columns

Fedora Budget repo migration #568

Summary

Background

Details

Summary