#662 Migration of FPC trac to pagure
Closed: fixed 4 years ago Opened 4 years ago by tibbs.

Might as well open a ticket for this. Trac is going away in February and we need to move to pagure.

I will take care of this move. The new location will be https://pagure.io/packaging-committee, which I have created (just to reserve it) but have not worked on yet.

A trac->pagure issue importer exists. I have done a test run and the results are visible in the pagure staging instance: https://stg.pagure.io/packaging-committee/issues

I let the importer create tags from keywords, which... wasn't a great idea. I actually cleaned up many of the tags that were created. I'll do another import soon without that.

The importer will soon grow the ability to convert trac ticket resolutions to pagure close statuses, so things won't all show up as either "fixed" or "invalid".

I will manually add tags for each of the statuses set up in our workflow (needinfo, meeting, etc.) and tag the open tickets appropriately. We can't yet separate tags used for process from tags used to indicate ticket content; hopefully we'll get that at some point in the not too distant future. Until then I would suggest that we not try to

Pagure has the ability to present different templates for tickets, but interacting with it is somewhat magical; there's a separate git repo that you check out and you commit new ticket templates there. Somehow that gets hooked up sort of like trac's components. I have to experiment quite a bit more.

Anyway, that's the current status and a vague list of what I need to do. I'd like to be converted by the new year if possible, but that will depending on the tooling more than anything.

We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2016-12-08/fpc.2016-12-08-17.00.txt):

  • Ticket #662 Migration of FPC trac to pagure (geppetto, 17:31:04)

Metadata Update from @james:
- Issue assigned to tibbs

4 years ago

And guess where I'm typing this…

Right now I am setting up tags. All committee members are admins of the new pagure repo at https://pagure.io/packaging-committee

Still to be done:

  • Finish assigning tags to open tickets
  • Decide if we care about close statuses of old tickets and if so, spend some time moving those over. I've already created them all but I didn't manage to get the importer to move them, and I just didn't think it was important enough to delay the conversion while I figured it out.
  • Figure out what to do about needinfo. I need to file a pagure RFE for something that more closely resembles the bugzilla needinfo state. In the meantime I can add a tag for it and do that, I guess, but the set of needinfo (and, really, meeting) tickets needs to be audited. I did add a big red "waiting on tibbs" tag (though I called it "committee").
  • Create a couple of "reports" (Really pagure's reports are nothing compared to what you get with trac.) The automatic tag filters are probably good enough.

Later we can decide if we want any additional process and then I can either set it up or work with the pagure devs to implement it.

Metadata Update from @tibbs:
- Issue close_status updated to: None
- Issue tagged with: committee

4 years ago

Some progress:

  • I've set up tags corresponding to the states we were using in trac, plus a couple of extras.
  • I filed pagure#1932 asking for something resembling bugzilla's needinfo state. In the meantime, there's a needinfo tag which I'll just stick on the relevant tickets. We'll just have to do manual sweeps before each meeting to make sure things don't stick around in that state.
  • I ported over the intro page from trac.
  • I filed fedora-infrastructure#5973 to have the redirect put in place so that things go over to pagure automatically.

And that's about it for the migration, I think.

Thanks for working on this.

At this point it's as done as it's going to be unless we decide we want to pull out all of the old close statuses.

Metadata Update from @tibbs:
- Issue untagged with: committee
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.