Martin Storsjö via llvm-dev
2019-Oct-25 11:49 UTC
[llvm-dev] RFC: Switching from Bugzilla to Github Issues
On Fri, 25 Oct 2019, Martin Storsjö via llvm-dev wrote:> On Thu, 24 Oct 2019, James Y Knight via llvm-dev wrote: > >> We do not want to build supplementary notification systems to make github >> issues send additional emails that it is unable to send itself. We will >> only >> support what GitHub supports. That means: >> - You can subscribe to notification emails for activity in the entire >> llvm-project repository. >> - You can subscribe to notification emails on an individual issue. >> - Someone else can CC you on an individual issue to get your attention, and >> you will get notifications from that (unless you opt-out). > > One thing comes to mind wrt workflows and how I often use bugzilla: After > bisecting a regression and filing a bug with the reproducer, I try to add CCs > for the author of the commit and potentially the reviewers who were involved > with the commit. > > In bugzilla it's fairly easy to try type people's names (which you find > easily via the Phabricator review) and bugzilla will autocomplete and let you > pick whoever seems to match what you typed. > > In github I'd presume you need to know the github username of the ones you > want to CC. For the cases where it matches the Phabricator username, this is > straightforward, but I'm sure there's a significant number of users where the > mapping isn't obvious.Replying to myself here - I rememeberd that when viewing a commit on github, github is actually very good at replacing any references to the original author name with their github username (to the extent that it actually is hard to find the realname of the author when viewing a commit). So for CCing people on issues, the author/committer should be easy to discover; potential related reviewers are the only ones where discovering their github usernames might be tricky. And that's much less important. // Martin
Finkel, Hal J. via llvm-dev
2019-Oct-25 17:56 UTC
[llvm-dev] RFC: Switching from Bugzilla to Github Issues
On 10/25/19 6:49 AM, Martin Storsjö via llvm-dev wrote: On Fri, 25 Oct 2019, Martin Storsjö via llvm-dev wrote: On Thu, 24 Oct 2019, James Y Knight via llvm-dev wrote: We do not want to build supplementary notification systems to make github issues send additional emails that it is unable to send itself. We will only support what GitHub supports. That means: - You can subscribe to notification emails for activity in the entire llvm-project repository. - You can subscribe to notification emails on an individual issue. - Someone else can CC you on an individual issue to get your attention, and you will get notifications from that (unless you opt-out). One thing comes to mind wrt workflows and how I often use bugzilla: After bisecting a regression and filing a bug with the reproducer, I try to add CCs for the author of the commit and potentially the reviewers who were involved with the commit. In bugzilla it's fairly easy to try type people's names (which you find easily via the Phabricator review) and bugzilla will autocomplete and let you pick whoever seems to match what you typed. In github I'd presume you need to know the github username of the ones you want to CC. For the cases where it matches the Phabricator username, this is straightforward, but I'm sure there's a significant number of users where the mapping isn't obvious. Replying to myself here - I rememeberd that when viewing a commit on github, github is actually very good at replacing any references to the original author name with their github username (to the extent that it actually is hard to find the realname of the author when viewing a commit). So for CCing people on issues, the author/committer should be easy to discover; potential related reviewers are the only ones where discovering their github usernames might be tricky. And that's much less important. I disagree, this is extremely important. Many bugs are filed by people who don't know what commit is relevant, and other community members who watch the bugs list (including myself) help cc the right people. We must have a straightforward way to cc people. A list somewhere with people's names could be a fine solution, but the current autocomplete is an important part of the workflow, and a limited search is important (as I often don't remember exactly how various people's names are spelled). -Hal // Martin _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -- Hal Finkel Lead, Compiler Technology and Programming Languages Leadership Computing Facility Argonne National Laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191025/bd0e7aec/attachment-0001.html>
Shoaib Meenai via llvm-dev
2019-Oct-25 18:02 UTC
[llvm-dev] RFC: Switching from Bugzilla to Github Issues
In my experience, when you start typing @ in a GitHub comment, it brings up an autocomplete with tagging suggestions, and that autocomplete works for both usernames and real names (assuming people have their name on their GitHub account). From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of "Finkel, Hal J. via llvm-dev" <llvm-dev at lists.llvm.org> Reply-To: "Finkel, Hal J." <hfinkel at anl.gov> Date: Friday, October 25, 2019 at 10:56 AM To: Martin Storsjö <martin at martin.st>, James Y Knight <jyknight at google.com> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues On 10/25/19 6:49 AM, Martin Storsjö via llvm-dev wrote: On Fri, 25 Oct 2019, Martin Storsjö via llvm-dev wrote: On Thu, 24 Oct 2019, James Y Knight via llvm-dev wrote: We do not want to build supplementary notification systems to make github issues send additional emails that it is unable to send itself. We will only support what GitHub supports. That means: - You can subscribe to notification emails for activity in the entire llvm-project repository. - You can subscribe to notification emails on an individual issue. - Someone else can CC you on an individual issue to get your attention, and you will get notifications from that (unless you opt-out). One thing comes to mind wrt workflows and how I often use bugzilla: After bisecting a regression and filing a bug with the reproducer, I try to add CCs for the author of the commit and potentially the reviewers who were involved with the commit. In bugzilla it's fairly easy to try type people's names (which you find easily via the Phabricator review) and bugzilla will autocomplete and let you pick whoever seems to match what you typed. In github I'd presume you need to know the github username of the ones you want to CC. For the cases where it matches the Phabricator username, this is straightforward, but I'm sure there's a significant number of users where the mapping isn't obvious. Replying to myself here - I rememeberd that when viewing a commit on github, github is actually very good at replacing any references to the original author name with their github username (to the extent that it actually is hard to find the realname of the author when viewing a commit). So for CCing people on issues, the author/committer should be easy to discover; potential related reviewers are the only ones where discovering their github usernames might be tricky. And that's much less important. I disagree, this is extremely important. Many bugs are filed by people who don't know what commit is relevant, and other community members who watch the bugs list (including myself) help cc the right people. We must have a straightforward way to cc people. A list somewhere with people's names could be a fine solution, but the current autocomplete is an important part of the workflow, and a limited search is important (as I often don't remember exactly how various people's names are spelled). -Hal // Martin _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.llvm.org_cgi-2Dbin_mailman_listinfo_llvm-2Ddev&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=7ySRMQaIXwSNAv8ATQlH98qUhSBP0Xy2xn-naNyIpTA&s=-CcZjVMkkjVOrYYxh-p-e7hXEnWuJXLcRah7X0RP50k&e=> -- Hal Finkel Lead, Compiler Technology and Programming Languages Leadership Computing Facility Argonne National Laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191025/46945c5f/attachment.html>