[Rpm-ecosystem] redesign of rpm.org and moving issues to github tracker
rholy at redhat.com
Wed Apr 29 12:35:10 UTC 2015
----- Original Message -----
> From: "Lubos Kardos" <lkardos at redhat.com>
> To: rpm-ecosystem at lists.rpm.org
> Sent: Wednesday, April 29, 2015 10:49:59 AM
> Subject: [Rpm-ecosystem] redesign of rpm.org and moving issues to github tracker
> because we want to have a new web page for rpm and that page won't be based
> TRAC we need to decide what to do with issues in TRAC issue tracker. And
> because we are using github for git we can also use github tracker for
> Some people already started using github issue tracker (now just one issue is
> there). So now we have two issue trackers.
> My proposal is to import all issues from TRAC into github, add comment in all
> active TRAC issues that the issues was moved to github and disable creating
> of new issues in TRAC. I tried possibilities of exporting from TRAC and
> importing to github and it is doable with some scripts. I tried those scripts
> and I imported all rpm issues in my github testing repo . A disadvantage
> is that all issues are created by me but there is a comment about original
> reporter in each issue. Also some issues needs manual editing because
> formatting tags are different in TRAC and github.
>  https://github.com/lkardos/test/issues
> Rpm-ecosystem mailing list
> Rpm-ecosystem at lists.rpm.org
If you are going to use Github as the main platform, it sounds good to me. I think it's better to have all the issues in one system thus it's worth the problems with original reporters not having a Github account or just not following the new ticket.
If you have not decided which platform it will be, I suggest taking a look at Phabricator before doing the migration. Also it seems that Kallithea is another alternative which has been discussed on PyCon.
Associate Software Engineer
Software Management Team
Red Hat Czech
More information about the Rpm-ecosystem