4:58 p.m.
#81: Migrating to Pagure
-------------------------+------------------------
Reporter: jflory7 | Owner: jflory7
Type: task | Status: new
Priority: this week | Milestone: ASAP
Component: General | Severity: not urgent
Keywords: nextmeeting |
-------------------------+------------------------
= phenomenon =
The [https://pagure.io/pagure-importer Pagure Importer] tool recently
added support for attachments. The CommOps Trac can migrate to Pagure.
= background analysis =
All fedorahosted.org instances (including Trac) is targeted to become
obsolete in 2017. This means all existing instances will be moved or
removed. Migrating on our own will save us time in the future, give us
time to adapt to a new tool, and save work for the Fedora Infrastructure
team later on.
The tool was demonstrated by cverna in
[https://stg.pagure.io/testcli/issues Exhibit A] (excluding tags in
import) and [https://stg.pagure.io/stg-fedora-commops/issues Exhibit b]
(including tags in import). A fair amount of manual work in updating tags,
milestones, and priorities will be needed, but it's better to begin doing
that now than even months later.
= implementation recommendation =
1. Play with test repos a little more to figure out how we could adapt
Pagure to our needs
2. Set target date for migration (two weeks from today?)
3. At date, move to new, official repository
4. Verify successful migration (all tickets present? all attachments
moved? all data accounted for?)
5. Update tags, milestones, priorities, other settings for Pagure
6. Give Trac one more month just in case of any mishaps, ensure all team
documentation points to Pagure instead of Trac
7. Request closure of Trac instance
--
Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/81>
Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps>
Community Operations (CommOps) aims to build and improve community infrastructure to
better communication across the Project and to help tell the story of Fedora.