www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - PSF News: CPython is switching to GitHub issues

reply Seb <seb wilzba.ch> writes:
http://pyfound.blogspot.com/2019/05/mariatta-wijaya-lets-use-github-issues.html
https://www.python.org/dev/peps/pep-0581

Most of the arguments, ideas and solutions apply to D and its 
Bugzilla too.
May 29 2019
parent reply Robert burner Schadek <rburners gmail.com> writes:
On Wednesday, 29 May 2019 at 14:49:37 UTC, Seb wrote:
 http://pyfound.blogspot.com/2019/05/mariatta-wijaya-lets-use-github-issues.html
 https://www.python.org/dev/peps/pep-0581

 Most of the arguments, ideas and solutions apply to D and its 
 Bugzilla too.
https://github.com/dlang/projects/issues/43
May 29 2019
parent reply user4678 <user4678 2874.ch> writes:
On Wednesday, 29 May 2019 at 18:47:52 UTC, Robert burner Schadek 
wrote:
 On Wednesday, 29 May 2019 at 14:49:37 UTC, Seb wrote:
 http://pyfound.blogspot.com/2019/05/mariatta-wijaya-lets-use-github-issues.html
 https://www.python.org/dev/peps/pep-0581

 Most of the arguments, ideas and solutions apply to D and its 
 Bugzilla too.
https://github.com/dlang/projects/issues/43
This bring several problems, leading to the conclusion that it is not a good idea. 1. ownership of migrated issues, accounts How can you guarantee that the creator of a Bugzilla issue will have admin rights (e.g at least the ability to close) on the migrated issue ? Do you realize that not everybody has a GH account ? So that's it ? people would have to follow or stop reporting ? 2. Maintenance. Everybody can volunteer to maintain issues: - close invalid. - close issues fixed but not well referenced. - change the labels, e.g from "enhancement" to "normal". - and more. think for example to the "advant of bugfixes" initiative. moving to GH means that only members of the organization will be able to do this maintenance. regular registered users will be more limited than on Bugzilla. unregistered users will be fucked. 3. performance GH is slow, is subject to be down because it is constantly attacked while D Bugzilla is dedicated to a single task, is fast and quite confidential (i.e not targeted). 4. Categories There is no categories in GH issue system, only labels. Bugzilla have keywords, see also, importance, etc. 5. Other BTW you already have an example of what it would be like: DUB issues.
Feb 23
parent Mathias Lang <pro.mathias.lang gmail.com> writes:
On Monday, 24 February 2020 at 04:40:06 UTC, user4678 wrote:
 1. ownership of migrated issues, accounts

 How can you guarantee that the creator of a Bugzilla issue will 
 have admin rights (e.g at least the ability to close) on the 
 migrated issue ?

 Do you realize that not everybody has a GH account ?
 So that's it ? people would have to follow or stop reporting ?
More people have a Github account than an issue.dlang.org account. Regarding ability to close, either the bug is fixed, and we can close it, or the person realized it was not a bug / withdraw his/her enhancement request, and we can close it on demand. In practice the later happens very rarely.
 2. Maintenance.

 Everybody can volunteer to maintain issues:

 - close invalid.
 - close issues fixed but not well referenced.
 - change the labels, e.g from "enhancement" to "normal".
 - and more.

 think for example to the "advant of bugfixes" initiative.

 moving to GH means that only members of the organization will 
 be able to do this maintenance. regular registered users will 
 be more limited than on Bugzilla. unregistered users will be 
 fucked.
Did you read the issue ? Because this exact topic came up: https://github.com/dlang/projects/issues/43#issuecomment-497221490
 3. performance

 GH is slow, is subject to be down because it is constantly 
 attacked while D Bugzilla is dedicated to a single task, is 
 fast and quite confidential (i.e not targeted).
Github is also backed by a multi-billion dollars company throwing a lot of resources behind it. While it has downtimes, those are not frequent (and when it happens, the whole ecosystem is affected anyway so Bugzilla is the least of our concern here). I'm not sure what you refer to by "targeted". If you're worried about your privacy, it is simple to make a dummy Github account with a throwaway email, just like you'd do for Bugzilla.
 4. Categories

 There is no categories in GH issue system, only labels.
 Bugzilla have keywords, see also, importance, etc.
Keywords are just like labels (there can be multiple of them). For items where there can be only one (importance, platform), we could use Milestones, or just different labels with the same prefix (e.g. `type-enhancement`, `type-bug`, etc...). We could also automate some of it using dlang-bot. Github actually provide a mean to create multiple issue templates, which hopefully will better guide newcomers (see https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository).
 5. Other

 BTW you already have an example of what it would be like: DUB 
 issues.
What's wrong with DUB issues ? I do think the move from Bugzilla to Github is good and will make us more visible and more accessible. I understand that there are certain concerns over Microsoft's ownership of Github, but so far our experience has been very positive (when D started, you'd send an email to Walter to get something patched, so we had come a long way). Github has been supporting more and more good features, such as different workflow, many user-friendly items (issue / PR template, contributing guide, code suggestions) and introduced a very good cross platform CI system. On another level, a good Github profile is a good portfolio for a developer to show, while all the work done on Bugzilla is harder and less effective to demonstrate.
Feb 24