forge/documentation
10
2
Fork 8
Code Issues Pull requests Activity Actions

Pagure migration doc: add follow-up checklist based on ours #10

Merged
t0xic0der merged 1 commit from adamwill/documentation:migration-quality-enhancements into main 2026-02-18 03:03:38 +00:00
Conversation 3 Commits 1 Files changed 1 +22
adamwill commented 2026-02-10 20:04:46 +00:00
Contributor
Copy link

As we (Quality team) were doing our migrations to Forge, we came
up with a checklist and some supplemental migration tools. This
adds a slightly tweaked version of the checklist to the migration
doc as we think it will be helpful for all other teams.

See quality/tickets#836
for the original.

Signed-off-by: Adam Williamson awilliam@redhat.com

As we (Quality team) were doing our migrations to Forge, we came up with a checklist and some supplemental migration tools. This adds a slightly tweaked version of the checklist to the migration doc as we think it will be helpful for all other teams. See https://forge.fedoraproject.org/quality/tickets/issues/836 for the original. Signed-off-by: Adam Williamson <awilliam@redhat.com>
As we (Quality team) were doing our migrations to Forge, we came
up with a checklist and some supplemental migration tools. This
adds a slightly tweaked version of the checklist to the migration
doc as we think it will be helpful for all other teams.

See quality/tickets#836
for the original.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
kparal requested changes 2026-02-11 11:41:44 +00:00
Dismissed
modules/ROOT/pages/migration/pagure_repository.adoc Outdated
@ -79,0 +83,4 @@
. Copy over the project URL for Forge manually. From _Pagure project -> Settings -> Project Details -> Project's url_ into _Forge project -> Settings -> Repository -> Website_.
. xref:../migrating_issue_dependencies.adoc[Migrate assignees and dependencies]. Verify that it worked correctly. Also inspect script output.
. Use link:https://forge.fedoraproject.org/quality/forge-helpers[forge_migrate_story_points.py] to migrate story points if your source repository used them. The script normalizes story point values to the set available as labels in Forge (1, 2, 3, 5, 8, 13). Verify that it worked correctly. Also inspect script output.
kparal commented 2026-02-11 11:39:56 +00:00
First-time contributor
Copy link

I would drop this line, Adam. That script looks at the story_points field, which is a custom field that we configured in our QA repositories only. I would be very surprised if anyone else used the same approach. I don't think this fits into a general guide. (The script is in the repo, and if some teams actually used a similar approach, they'll see it and can tweak it for their needs).

I would drop this line, Adam. That script looks at the `story_points` field, which is a custom field that we configured in our QA repositories only. I would be very surprised if anyone else used the same approach. I don't think this fits into a general guide. (The script is in the repo, and if some teams actually used a similar approach, they'll see it and can tweak it for their needs).
adamwill commented 2026-02-11 16:31:09 +00:00
Author
Contributor
Copy link

I figured other RH-y teams might have had the same idea, but sure, we can drop it if you like.

I figured other RH-y teams might have had the same idea, but sure, we can drop it if you like.
adamwill commented 2026-02-11 16:38:04 +00:00
Author
Contributor
Copy link

Tweaked. I also de-emphasized the label conversion script as it relies on the expected org label state and I don't think all orgs have the labels, and I'm not sure they get the same IDs in every org.

Tweaked. I also de-emphasized the label conversion script as it relies on the expected org label state and I don't think all orgs have the labels, and I'm not *sure* they get the same IDs in every org.
adamwill marked this conversation as resolved
adamwill force-pushed migration-quality-enhancements from 8e1d185250 to e8676cdfa7 2026-02-11 16:37:30 +00:00 Compare
kparal approved these changes 2026-02-12 13:55:30 +00:00
t0xic0der approved these changes 2026-02-18 03:03:30 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
kparal
t0xic0der
Labels
Clear labels
  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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
forge/documentation!10
No description provided.