council/tickets
5
0
Fork 0
Code Issues 13 Pull requests Projects Activity

Council Forgejo Migration Tracker #540

New issue
Open
opened 2025-08-07 13:37:31 +00:00 by amoloney · 1 comment
amoloney commented 2025-08-07 13:37:31 +00:00
Owner
Copy link

This is where we will track the work needed to migrate the Fedora Council ticket tracker to the new forge

This is where we will track the work needed to migrate the Fedora Council ticket tracker to the new forge
humaton commented 2025-08-13 13:59:08 +00:00
Owner
Copy link

Some links for the meeting:

Repositories from the Council Pagure project are now available in the Forgejo organization: Council.

Use the "Login by FAS" button to authenticate.

Council member accounts are not yet synced. I have added some of you manually from memory.

All current members have admin rights to the organization.

The council-docs repository failed to migrate in the production deployment, even though it works in staging.

Private issues are not yet migrated; I don't have access to them, nor do I want it. One of the council representatives will have to do that. Using the self-service migration tool.

Some links for the meeting: Repositories from the [Council](https://pagure.io/projects/Fedora-Council/%2A) Pagure project are now available in the Forgejo organization: [Council](https://forge.fedoraproject.org/Council). Use the **"Login by FAS"** button to authenticate. Council member accounts are not yet synced. I have added some of you manually from memory. All current members have admin rights to the organization. The `council-docs` repository failed to migrate in the production deployment, even though it works in staging. Private issues are not yet migrated; I don't have access to them, nor do I want it. One of the council representatives will have to do that. Using the self-service migration tool.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
budget
  
Closed As
approved
Closed with the reason of approved

  
Closed As
declined
Closed with the reason of declined

  
Closed As
deferred
Closed with the reason of deferred

  
Closed As
duplicate
Closed with the reason of duplicate

  
Closed As
no action needed
Closed with the reason of no action needed

  
Closed As
resolved
Closed with the reason of resolved

  
code-of-conduct

   
documentation

   
elections

   
events

   
hackfests

   
initiatives

   
In Progress

Topics that are being actively discussed orworked on

  
mindshare

   
Needs Review

   
Next Meeting

For tickets that need to be discussed at the next council meeting

  
policies

   
spending-request

"Budget" is for big-picture things. This is for as-we-go allocations.

  
ticket-vote

Hey, council members: Let's vote on this in this ticket, right now!

  
trademarks

   
urgent
No labels
budget
Closed As
approved
Closed As
declined
Closed As
deferred
Closed As
duplicate
Closed As
no action needed
Closed As
resolved
code-of-conduct
documentation
elections
events
hackfests
initiatives
In Progress
mindshare
Needs Review
Next Meeting
policies
spending-request
ticket-vote
trademarks
urgent
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Council and Forgejo Work
Assignees
Clear assignees
No assignees
amoloney
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: council/tickets#540
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?