Re: [Freeipa-devel] FedoraHosted.org sunset
On Fri, 2016-09-30 at 13:02 -0400, Robbie Harwood wrote: > Nathaniel McCallum writes: > > > On Fri, 2016-09-30 at 14:19 +0200, Martin Kosek wrote: > > > On 09/23/2016 09:54 AM, Jakub Hrozek wrote: > > > > On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: > > > > > > > > > > As you know, FedoraHosted.org will be decommissioned. > > > > > https://communityblog.fedoraproject.org/fedorahosted-sunset- > > > > > 2017 > > > > > -02-28/ > > > > > > > > > > We use Trac instance there. Let's discuss where we should > > > > > migrate > > > > > and what are our requirements. Then put results on one place. > > > > > For > > > > > that I've created: > > > > > http://www.freeipa.org/page/FedoraHosted_Migration > > > > > > > > > > > > > > > > That you for writing this up, there are some good points I > > > > didn't > > > > think about, like migrating the ticket numbers. Did you already > > > > file > > > > an issue that tracks this in Pagure (or asked if this is > > > > already > > > > possible)? > > > > > > > > > > > > I think the achieving the same ticket numbers should not be > > > difficult. During the migration, we would just need to make sure > > > we > > > insert dummy Pagure/Github/... tickets on when the original > > > ticket > > > was deleted, like > > > > > > https://fedorahosted.org/freeipa/ticket/2 > > > > > > A pro for github is that migration tools exist. This is a con for > > pagure. > > > Much as I want github... a migration tool does exist to go to pagure: > https://pagure.io/pagure-importer/ I have used it (on the gssproxy > fedorahosted as a test) and while I did not like it it did get the > job > done eventually. Thanks for the correction. I didn't see that the last time I looked. Nathaniel -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
Nathaniel McCallum writes: > On Fri, 2016-09-30 at 14:19 +0200, Martin Kosek wrote: >> On 09/23/2016 09:54 AM, Jakub Hrozek wrote: >>> On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: As you know, FedoraHosted.org will be decommissioned. https://communityblog.fedoraproject.org/fedorahosted-sunset-2017 -02-28/ We use Trac instance there. Let's discuss where we should migrate and what are our requirements. Then put results on one place. For that I've created: http://www.freeipa.org/page/FedoraHosted_Migration >>> >>> >>> That you for writing this up, there are some good points I didn't >>> think about, like migrating the ticket numbers. Did you already file >>> an issue that tracks this in Pagure (or asked if this is already >>> possible)? >> >> >> I think the achieving the same ticket numbers should not be >> difficult. During the migration, we would just need to make sure we >> insert dummy Pagure/Github/... tickets on when the original ticket >> was deleted, like >> >> https://fedorahosted.org/freeipa/ticket/2 > > A pro for github is that migration tools exist. This is a con for > pagure. Much as I want github... a migration tool does exist to go to pagure: https://pagure.io/pagure-importer/ I have used it (on the gssproxy fedorahosted as a test) and while I did not like it it did get the job done eventually. signature.asc Description: PGP signature -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
On Fri, 2016-09-30 at 14:19 +0200, Martin Kosek wrote: > On 09/23/2016 09:54 AM, Jakub Hrozek wrote: > > On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: > > > Hi all, > > > > > > As you know, FedoraHosted.org will be decommissioned. > > > https://communityblog.fedoraproject.org/fedorahosted-sunset-2017 > > > -02-28/ > > > > > > We use Trac instance there. Let's discuss where we should migrate > > > and > > > what are our requirements. Then put results on one place. For > > > that I've > > > created: > > > http://www.freeipa.org/page/FedoraHosted_Migration > > > > > > That you for writing this up, there are some good points I didn't > > think > > about, like migrating the ticket numbers. Did you already file an > > issue > > that tracks this in Pagure (or asked if this is already possible)? > > > I think the achieving the same ticket numbers should not be > difficult. During > the migration, we would just need to make sure we insert dummy > Pagure/Github/... tickets on when the original ticket was deleted, > like > > https://fedorahosted.org/freeipa/ticket/2 A pro for github is that migration tools exist. This is a con for pagure. The github API doesn't allow you to specify issue numbers. However, it does issue them incrementally. Thus, so long as the input to the conversion process is sorted by ticket number and there are no gaps, the ticket number will be retained. One issue I ran into was github's throttling limits. I worked around this by inserting a sleep() into the import loop which slowed down the process enough to bypass github's limiting. However, this also means that with a database as large as FreeIPA's import will take a long time. Nathaniel -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
On 09/23/2016 09:54 AM, Jakub Hrozek wrote: > On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: >> Hi all, >> >> As you know, FedoraHosted.org will be decommissioned. >> https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/ >> >> We use Trac instance there. Let's discuss where we should migrate and >> what are our requirements. Then put results on one place. For that I've >> created: >> http://www.freeipa.org/page/FedoraHosted_Migration > > That you for writing this up, there are some good points I didn't think > about, like migrating the ticket numbers. Did you already file an issue > that tracks this in Pagure (or asked if this is already possible)? I think the achieving the same ticket numbers should not be difficult. During the migration, we would just need to make sure we insert dummy Pagure/Github/... tickets on when the original ticket was deleted, like https://fedorahosted.org/freeipa/ticket/2 Martin -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
On 09/23/2016 02:09 PM, Martin Basti wrote: > > > On 23.09.2016 09:54, Jakub Hrozek wrote: >> On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: >>> Hi all, >>> >>> As you know, FedoraHosted.org will be decommissioned. >>> >>> https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/ >>> >>> We use Trac instance there. Let's discuss where we should migrate and >>> what are our requirements. Then put results on one place. For that I've >>> created: >>>http://www.freeipa.org/page/FedoraHosted_Migration >> That you for writing this up, there are some good points I didn't think >> about, like migrating the ticket numbers. Did you already file an issue >> that tracks this in Pagure (or asked if this is already possible)? >> > > Do we need review by field? It is recorded in commit and for ongoing > reviews we are assigning ourselves to pull requests, so everybody knows > if somebody is reviewing a PR. > > Martin^2 > Assigning to PR solves the issue for which "review by" was meant. So we may eventually drop it. Ideally when patch backlog on devel list is cleansed. In general, I'd not say that each individual field is a requirement, e.g. I can imagine that: keywords, source, component, maybe even a milestone and a priority can be tags/labels What would be nice is some reporting/filtering capability so that I don't have to script each view separately. -- Petr Vobornik -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
On 23.09.2016 09:54, Jakub Hrozek wrote: On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: Hi all, As you know, FedoraHosted.org will be decommissioned. https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/ We use Trac instance there. Let's discuss where we should migrate and what are our requirements. Then put results on one place. For that I've created: http://www.freeipa.org/page/FedoraHosted_Migration That you for writing this up, there are some good points I didn't think about, like migrating the ticket numbers. Did you already file an issue that tracks this in Pagure (or asked if this is already possible)? Do we need review by field? It is recorded in commit and for ongoing reviews we are assigning ourselves to pull requests, so everybody knows if somebody is reviewing a PR. Martin^2 -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
Re: [Freeipa-devel] FedoraHosted.org sunset
On Thu, Sep 22, 2016 at 06:09:43PM +0200, Petr Vobornik wrote: > Hi all, > > As you know, FedoraHosted.org will be decommissioned. > https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/ > > We use Trac instance there. Let's discuss where we should migrate and > what are our requirements. Then put results on one place. For that I've > created: > http://www.freeipa.org/page/FedoraHosted_Migration That you for writing this up, there are some good points I didn't think about, like migrating the ticket numbers. Did you already file an issue that tracks this in Pagure (or asked if this is already possible)? -- Manage your subscription for the Freeipa-devel mailing list: https://www.redhat.com/mailman/listinfo/freeipa-devel Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code