Re: Why don't you use the Github issue system?
On 2016-03-04 00:54, cym13 wrote: We'd still lose all pull requests though and all discussions about them. Does any, hmm, "pullrequestzilla" thing exist? There's GitLab, which is basically like GitHub but it's open source and you can host it yourself. They do have hosting as well. GitLab supports pull requests (they call it merge requests), issues, wiki, all the stuff that GitHub supports, plus they have a built-in CI system as well. They even have the "auto merge" feature built-in. We use it at my job and it works really well. -- /Jacob Carlborg
Re: Why don't you use the Github issue system?
On Wednesday, 2 March 2016 at 23:59:49 UTC, Seb wrote: Hey, I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. GitHub issues is okay for one-man projects or small teams that do not want to bother much with bugs, issues, support requests, etc. For anything serious I suggest you forget GitHub issues... A common problem is that you have a project that spans multiple repositories (a library, a service, etc). You want a *single place* to deal with issues, not multiple places (each repository has own issues)! As people already mentioned, Bugzilla is a robust, feature-rich system. Use it (or something similar)!
Re: Why don't you use the Github issue system?
On Thursday, 3 March 2016 at 23:54:15 UTC, cym13 wrote: On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: On 3/2/2016 3:59 PM, Seb wrote: I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. 1. Bugzilla is working famously for us. 2. I've had occasion to use github issues, and was surprised by how lame it was compared to Bugzilla. There's no contest. 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. We'd still lose all pull requests though and all discussions about them. Does any, hmm, "pullrequestzilla" thing exist? phabricator does a pretty good job (better than github in many cases IMO).
Re: Why don't you use the Github issue system?
On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: On 3/2/2016 3:59 PM, Seb wrote: I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. 1. Bugzilla is working famously for us. 2. I've had occasion to use github issues, and was surprised by how lame it was compared to Bugzilla. There's no contest. 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. We'd still lose all pull requests though and all discussions about them. Does any, hmm, "pullrequestzilla" thing exist?
Re: Why don't you use the Github issue system?
On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: On 3/2/2016 3:59 PM, Seb wrote: I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. 1. Bugzilla is working famously for us. Is it Kardashian famous? 2. I've had occasion to use github issues, and was surprised by how lame it was compared to Bugzilla. There's no contest. 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. I don't know, Both Khloe and Kim Kardashian went dark and they seem to be ok? Seriously... Sorry!
Re: Why don't you use the Github issue system?
On 03/02/2016 07:57 PM, sigod wrote: On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. This annoys me a lot in all repository hosting services. Hear hear!
Re: Why don't you use the Github issue system?
On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: On 3/2/2016 3:59 PM, Seb wrote: I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. 1. Bugzilla is working famously for us. 2. I've had occasion to use github issues, and was surprised by how lame it was compared to Bugzilla. There's no contest. 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. Wow that was a short & insightful discussion - thanks for sharing your thoughts. No further questions, your honour ;-)
Re: Why don't you use the Github issue system?
On Thursday, 3 March 2016 at 00:27:39 UTC, Walter Bright wrote: 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable. This annoys me a lot in all repository hosting services.
Re: Why don't you use the Github issue system?
On 3/2/2016 3:59 PM, Seb wrote: I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. 1. Bugzilla is working famously for us. 2. I've had occasion to use github issues, and was surprised by how lame it was compared to Bugzilla. There's no contest. 3. If Github goes dark, we still have our local complete copies of the git database. If Github issues goes dark, we lose it all. We control the Bugzilla database. This database is ABSOLUTELY CRITICAL to D's future, and not having a copy of it is absolutely unacceptable.
Re: Why don't you use the Github issue system?
On Wednesday, 2 March 2016 at 23:59:49 UTC, Seb wrote: Hey, I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. Con: - Bugzilla is working fine - More than five years of history - Github doesn't have voting yet (it's supposed to come soon) Pro: - Unified issue tracking (source code, PR, issues) - Some handy features (mentioning users, markdown, reference, ...) [1] I know that manpower is very limited, but there a couple of migration scripts existing [2,3]. In any case I am just interested where you stand on this issue ;-) [1] https://guides.github.com/features/issues/ [2] https://gist.github.com/jussi-kalliokoski/4375613 [3] https://github.com/mikej888/BugzillaMigrate As a simple user I can say that it would be worst. Currently bugzilla is **very permissive** (and that's a good thing !). Once you're registered you can open, close, assign any issue. On GH only members of an organization can really do stuff on bugs. About the first Con: the bot already links PR and bugzilla (auto-close, notification when a PR references an issue).
Re: Why don't you use the Github issue system?
On Wednesday, 2 March 2016 at 23:59:49 UTC, Seb wrote: Hey, I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. I HATE Github issues. When they are not filled with unhelpful, annoying, and signal drowning comments like "+1" and tens of gifs, they are useless in other ways, such as not allowing attachments, providing no priority mechanism, and providing no mechanism for reporting OS and version with the bug. The biggest issue is that the project maintainers have to tag everything as either an enhancement request, regression, etc. That means that a least one mod would have to scan each issue to signal what it is to contributors. That's a dramatic increase in needed effort. Having bugzilla on a separate service also increases the cost of making comments enough that low info posts aren't made, but not high enough that bugs aren't reported.
Why don't you use the Github issue system?
Hey, I am just curious whether you have already considered moving from Bugzilla to the Github issue system and where your current opinion is. Con: - Bugzilla is working fine - More than five years of history - Github doesn't have voting yet (it's supposed to come soon) Pro: - Unified issue tracking (source code, PR, issues) - Some handy features (mentioning users, markdown, reference, ...) [1] I know that manpower is very limited, but there a couple of migration scripts existing [2,3]. In any case I am just interested where you stand on this issue ;-) [1] https://guides.github.com/features/issues/ [2] https://gist.github.com/jussi-kalliokoski/4375613 [3] https://github.com/mikej888/BugzillaMigrate
