[Rpm-ecosystem] redesign of rpm.org and moving issues to github tracker
jzeleny at redhat.com
Thu Apr 30 07:53:19 UTC 2015
On 29. 4. 2015 at 16:24:08, Pavel Odvody wrote:
> On Wed, 2015-04-29 at 08:35 -0400, Radek Holy wrote:
> > ----- 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
> > >
> > > Hi,
> > >
> > > because we want to have a new web page for rpm and that page won't be
> > > based
> > > on
> > > 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
> > > issues.
> > > 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.
> > >
> > > Lubos
> > >
> > >  https://github.com/lkardos/test/issues
> > > _______________________________________________
> > > Rpm-ecosystem mailing list
> > > Rpm-ecosystem at lists.rpm.org
> > > http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
> > 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.
> How about Gitlab¹, or Gogs²?
> Github is easy, it's already well established and accessible from the
> web (well maybe except for China :)). So I believe that the question
> really is: use something that's already there or roll our own
> self-hosted service.
> Since we already have domain and server (not sure about the specs),
> hosting our own service should be straight DevOps.
> That being said, I vouch for Github as the other solutions I see as
> being just Github without "Github" in the title :)
Agreed. I especially like the fact that a lot of people already have github
account, thus it will be easier to get them filing tickets, working with us on
pull requests and all the other stuff that comes with it.
One question on the side: Assuming the tickets are migrated to github and all
our rpm-based projects are at one place, is it possible to use that and bounce
github tickets back and forth between the different projects? That's one aspect
I like about bugzilla, you can easily reassign the bug if you find it's
actually somewhere else.
More information about the Rpm-ecosystem