What don't you switch to GitHub issues

[rjframe]

On Sun, 31 Dec 2017 17:19:22 -0700, Jonathan M Davis wrote:

> Yes, it would be a pain to switch away from github at this point, but if
> github went down permanently tomorrow, it would just be an annoying
> roadblock. We almost certainly wouldn't lose any code (at most, a few
> commits, if no one pulled recently enough), and we wouldn't lose any bug
> reports. We'd have to go to the trouble of setting up our own gitlab or
> switching to bitbucket or something like that and pointing all of the
> automated stuff to the new place, and it would be a royal pain, but we
> wouldn't lose any information. If all of the issues were on github, and
> github went away, we'd lose them.
> 
> Sure, github is unlikely to go away, but I see no reason to tie
> ourselves to it thoroughly enough that we're going to lose data if they
> go away - especially since I don't actually see any benefit in switching
> to github issues.

If only one person has access to Bugzilla, we're actually at a greater 
risk now than if we used Github for issues. If we don't have regular 
backups to a location accessible to multiple members of the core team, we 
shouldn't consider Bugzilla to be a reliable data repository.


--Ryan