Fwd: [FAmNA Trac] #159: Migrating to Pagure

[Justin W. Flory]

Hello all,

As briefly discussed towards the end of this evening's FAmNA meeting, I 
noted that the bug that was blocking us from testing a migration to 
Pagure from Trac was fixed. I've created a ticket explaining the full 
details of this migration and how it would work in the ticket.

We can vote on this ticket at the next meeting, but if you will not be 
able to attend, feel free to leave a vote in the ticket. Since this is a 
major change from a tool we've been using for over half a decade, I 
figured it was worth highlighting this ticket on the mailing list.

After we have migrated our Trac, I would like to offer advice and 
guidance to other regions looking to migrate in the coming future so 
everyone can try to be on the same page (this is also a big opportunity 
for all of the regions to follow the same format and help keep a "single 
user experience" for all Ambassadors around the world in terms of what 
tools we use and how we use them).

Thanks everyone. :)

-------- Forwarded Message --------
Subject: [FAmNA Trac] #159: Migrating to Pagure
Date: Fri, 28 Oct 2016 06:17:07 -0000
From: FAmNA Trac 
Reply-To: [e-mail]

#159: Migrating to Pagure
--------------------+----------------------
Reporter:  jflory7  |      Owner:
     Type:  task     |     Status:  new
Priority:  blocker  |  Milestone:  meeting
Severity:  urgent   |   Keywords:  internal
--------------------+----------------------
  = Phenomenon =

On February 28, 2017, [https://communityblog.fedoraproject.org
  /fedorahosted-sunset-2017-02-28/ FedoraHosted is retiring] and will be set
  into read-only mode. FAmNA needs to migrate our Trac to Pagure to ensure
  we can continue working after Trac closes.

= Analysis =

A blocking bug was recently fixed in the [https://pagure.io/pagure-
  importer pagure-importer] tool that was preventing the data from being
  migrated. Now, this bug has been fixed and a first "test run" of the
  migration is available in the staging version of Pagure. You can find the
  **[https://stg.pagure.io/stg-famna/issues test repository for FAmNA
  here]**.

While the formatting for tickets has changed from wiki formatting to
  markdown, the change is relatively minor. All things like attachments to
  tickets (e.g. PDFs, images, etc.) have also imported.

Just like how Trac has things like milestones, severity, and priorities,
  this can be replicated in Pagure. In the repository settings, we can use
  milestones and roadmaps for tracking tickets for each release cycle (see:
  [https://pagure.io/fedora-commops/roadmap example roadmap]). Tickets can
  also be assigned severity levels for issues that need to be addressed
  sooner than others.

Trac milestones would become Pagure tags. Issues can be tagged in a
  variety of ways, e.g. "event", "meeting", "open", "budget", or any other
  amount of ways we choose. Multiple tags can be used for a ticket. A good
  example of how this would look is in the [https://pagure.io/fedora-
  commops/issues CommOps Pagure].

If approved, I will migrate the FAmNA Trac to Pagure, set up the tags and
  milestones as described above, and set this Trac instance as read-only.
  After a month of using Pagure, we can request the FAmNA Trac URL to
  redirect to our Pagure.

= Implementation =

1. FAmNA votes +1/-1 for migrating to Pagure after our next meeting.
  2. Trac is imported into a Pagure repository.
  3. New Pagure repository is set up with tags, milestones, and priorities
  similar to our Trac.
  4. Current Ambassadors are added to a FAmNA "group" in Pagure.
  5. This Trac instance is set as read-only.
  6. After one month to ensure everything is working as expected, we request
  the FAmNA Trac URL redirects to Pagure (if for some reason data needs to
  be recovered, it will still exist in Fedora Infra).