[Rpm-ecosystem] redesign of rpm.org and moving issues to github tracker
podvody at redhat.com
Wed Apr 29 14:24:08 UTC 2015
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
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 :)
Pavel Odvody <podvody at redhat.com>
Software Engineer - EMEA ENG Developer Experience
5EC1 95C1 8E08 5BD9 9BBF 9241 3AFA 3A66 024F F68D
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the Rpm-ecosystem