Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114320
To: Internals <internals@lists.php.net>
References: <CAOwTYAtOti3+Tv9Cu5fK6bQ3tjAibRHUWOctnQFfGJyaoQYExw@mail.gmail.com>
 <de8c00e1-bf7d-a5d6-03a9-6aaf85960d1a@gmail.com>
 <C67FE36C-8143-427B-AC9C-FAEBD658DDE3@gmail.com>
 <CAGgaK7Kv4vi-H2VnGkxduhHGYUWs7mBDSDpRWkcDfBVTkSJ1cg@mail.gmail.com>
Message-ID: <bc1ad84e-3919-d819-8c60-635539afc4c5@gmail.com>
Date: Sun, 9 May 2021 22:49:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <CAGgaK7Kv4vi-H2VnGkxduhHGYUWs7mBDSDpRWkcDfBVTkSJ1cg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Re: Bugsnet
From: rowan.collins@gmail.com (Rowan Tommins)

On 09/05/2021 16:30, Max Semenik wrote:
> Lots of large projects use GitHub for bug tracking: Go, Rust, 
> Kubernetes - seems to work well enough for them.


Those three look like good examples in terms of volume. It's hard to 
tell from the outside if people are happy with their processes, but we 
can get some idea of what those processes are, and whether PHP could do 
something similar.

In terms of "SaaS vs custom code", it's notable that all three run 
custom bots to add functionality not offered by Github, with both 
automatic actions (e.g. adding default labels, closing stale issues) and 
interactive ones (e.g. adding certain labels at user request, without 
the user needing permission in Github itself). Rust's bot is strongly 
integrated with their Zulip chat instance; Kubernetes' bot is part of 
the Prow CI application.

- https://github.com/golang/build/blob/master/cmd/gopherbot/gopherbot.go
- https://github.com/rust-lang/triagebot
- https://github.com/kubernetes/test-infra/tree/master/prow#bots-home

Go makes heavy use of Milestones; my impression is that these are 
assigned by Google employees working on the project full time.

Kubernetes and Rust both use prefixed labels for various attributes of 
the issue (Area, Status, Severity, etc): Kubernetes has a total of 196; 
Rust has a whopping 376, the best description I found of which is this: 
https://internals.rust-lang.org/t/how-the-rust-issue-tracker-works/3951

It might just be an illusion, but it feels like all three projects have 
a lot more resources to spend on all this than PHP does; Rust has 
"Working Groups", Kubernetes has "Special Interest Groups", and PHP 
struggles to assign each module a single maintainer. How that affects 
our tooling requirements, I'm not sure, but I suspect new contributor 
experience should be high on our priority list, either in terms of user 
interface or just documentation.

Regards,

-- 
Rowan Tommins
[IMSoP]