Re: [eclipse.org-committers] Experience using GitHub verus Eclipse.org Hosted Git
Thanks everyone for your input.
It seems there is rough agreement that the Eclipse.org tools are better and that the GitHub tools are good enough. There was also the suggestion that one could mix and match (keep using Eclipse Bugzilla instead of GitHub Issue tracker). Despite the fact that I am one of the few people in the world that "like" Bugzilla (after using many different other bug systems), mixing and matching seems bad to me. There are likely all sorts of integrations available to help, but still something seems wrong with the idea.
I think we will eventually do the move, but there is currently some short term chaos that means we need to delay the decision for a week or two. We need to also discuss this with the committers on the Orion list.
Once again, thanks for your input,
Gunnar Wagenknecht ---03/30/2016 09:08:26 AM---Hi Steve, >
From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
To: Steve Northover/Ottawa/IBM@IBMCA
Cc: eclipse.org-committers@xxxxxxxxxxx, Discussions for new Eclipse projects <incubation@xxxxxxxxxxx>
Date: 03/30/2016 09:08 AM
Subject: Re: [eclipse.org-committers] Experience using GitHub verus Eclipse.org Hosted Git
> Am 29.03.2016 um 21:01 schrieb Steve Northover <snorthov@xxxxxxxxxx>:
> Rather, I'm interested in things like GitHub Issues versus Bugzilla.
GitHub Issues is a separate concern from Git hosting. You can use GitHub just for Git hosting and continue using Bugzilla for issue tracking. Keep in mind that GitHub Issues are not integrated with the Eclipse project infrastructure. GitHub issues has a nice UI and the feature set is a bit more limited, though. Webmasters have a solution for backing up your data (in case case GitHub goes away).