[PHP-DEV] Re: Bugsnet

Hi Joe, On Sun, May 9, 2021, 1:49 PM Joe Watkins wrote: > Morning internals, > > > Having moved our workflow to github, now seems to be the time to seriously > consider retiring bugsnet for general use, and using the tools that are > waiting for us - Github Issues. > yes! yes! yes! and we

Re: [PHP-DEV] Re: Bugsnet

Hi Stas, On Sun, May 9, 2021, 3:06 PM Stanislav Malyshev wrote: > Hi! > > > If at some time in the future, github becomes a less than suitable > > environment for us, we can just move, no problem. There's no sense in > > which we are locked into anything. > > I don't see how we could "just

Re: [PHP-DEV] Re: Bugsnet

On Tue, May 25, 2021 at 3:10 PM Christoph M. Becker wrote: > On 25.05.2021 at 14:57, Nikita Popov wrote: > > > To make some forward progress here, I think a good starting point would > be > > to enable GitHub issues on the doc-* repos to get some usage experience > in > > a more limited setting.

Re: [PHP-DEV] Re: Bugsnet

On 25.05.2021 at 14:57, Nikita Popov wrote: > To make some forward progress here, I think a good starting point would be > to enable GitHub issues on the doc-* repos to get some usage experience in > a more limited setting. Docs issues probably benefit more from being hosted > on GitHub than

Re: [PHP-DEV] Re: Bugsnet

On Mon, May 10, 2021 at 11:22 PM Christoph M. Becker wrote: > On 10.05.2021 at 17:10, Nikita Popov wrote: > > > * As was already mentioned, there's no support for security issues, so > > we'd retain bugs.php.net for that purpose, at least for the time being. > > But even if bugsnet would no

Re: [PHP-DEV] Re: Bugsnet

On 10.05.2021 at 17:10, Nikita Popov wrote: > * As was already mentioned, there's no support for security issues, so > we'd retain bugs.php.net for that purpose, at least for the time being. But even if bugsnet would no longer be required to file any new tickets, please keep it in read-only

Re: [PHP-DEV] Re: Bugsnet

On 10/05/2021 16:10, Nikita Popov wrote: Did I miss anything else that bugs.php.net does? The biggest difference I see between GH Issues and every other issue tracker I've ever seen is pre-defined fields. Labels can broadly do the same job, but they feel very different

Re: [PHP-DEV] Re: Bugsnet

On Mon, May 10, 2021 at 3:29 PM Dan Ackroyd wrote: > Hi Joe, > > > We have a spam problem on bugsnet > > I would snarkily say "maybe accept the PRs from people wanting to work > on it?", but I realise that ignores the underlying problem, that PHP > lacks people. And particularly lacks people who

Re: [PHP-DEV] Re: Bugsnet

Hi Joe, > We have a spam problem on bugsnet I would snarkily say "maybe accept the PRs from people wanting to work on it?", but I realise that ignores the underlying problem, that PHP lacks people. And particularly lacks people who can dedicate time to understanding, reviewing and saying no to

[PHP-DEV] Re: Bugsnet

Hi Joe, I don't think anybody denies that bugsnet isn't great, and that spam is an issue. I would argue that the main reason for the spam is, is that we don't require a sign-up. But I think we need to be really careful if we'd decide to move to something else. TLDR: I don't believe GitHub

Re: [PHP-DEV] Re: Bugsnet

Hi! 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

Re: [PHP-DEV] Re: Bugsnet

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

Re: [PHP-DEV] Re: Bugsnet

On Sun, May 9, 2021 at 11:58 AM Rowan Tommins wrote: > Can we do a throwaway import of a few hundred bugs to a test repo, and see > what that might look like? Is there a dump of public issues available somewhere? The closest to sufficient data export I can find is e.g.

Re: [PHP-DEV] Re: Bugsnet

On Sun, May 9, 2021 at 11:58 AM Rowan Tommins wrote: > This is my instinct as well - Github Issues seems to be adequate as a > lightweight bug tracker, but how well will it scale, and how much will we > miss "advanced" features like separately searchable and reportable fields > and statuses?

[PHP-DEV] Re: Bugsnet

On 09/05/2021 09:05, Stanislav Malyshev wrote: I don't see how we could "just move" if all our bug handling would be wired into Github. I can easily see how we could move a repo to any provider that supports git - git is a generic platform, Github is just a frontend. But there's no alternative

Re: [PHP-DEV] Re: Bugsnet

On 9 May 2021 08:33:08 BST, Stanislav Malyshev wrote: >It is not good that our infrastructure is "hidden away in a dark >corner", and it is true that bugs needs some TLC for a while. But >Github >Issues frankly sucks big time as a bug management system. It's hard to >fault them as it's not

Re: [PHP-DEV] Re: Bugsnet

Hi all, I shouldn't have said we can "just" move ... I'm not supposing it will be easy. We can "just move", in about the same sense that we can "just move" today. Considering the difficulty of problems we do not currently have is a waste of time. Cheers Joe On Sun, 9 May 2021 at 10:08,

Re: [PHP-DEV] Re: Bugsnet

Hey folks: Am 09.05.21 um 09:33 schrieb Stanislav Malyshev: > Hi! > [...] > > 1. Bug reporting templates> 2. Pre-filter on reported bugs> 3. Advanced search > 4. Custom fields like PHP version or CVE ID > 5. Private bugs that are accessible only to members of security team > 6. Custom statuses

[PHP-DEV] Re: Bugsnet

Hi! If at some time in the future, github becomes a less than suitable environment for us, we can just move, no problem. There's no sense in which we are locked into anything. I don't see how we could "just move" if all our bug handling would be wired into Github. I can easily see how we

[PHP-DEV] Re: Bugsnet

Hi Stas, I did mention that we're leaving aside the sec issue for now. > Let me list all it is lacking that we have right now, with current old and dusty bugs: 1)

Re: [PHP-DEV] Re: Bugsnet

Am 09.05.2021 um 09:33 schrieb Stanislav Malyshev: 1. Bug reporting template GitHub Issues has support for reporting templates. For instance, clicking "New issue" on https://github.com/symfony/symfony/issues will lead to you https://github.com/symfony/symfony/issues/new/choose. This is an

[PHP-DEV] Re: Bugsnet

Hi! Quite aside from spam problems, bugsnet is hidden away in a dark corner of the internet that requires a special login, doesn't integrate with source code or our current workflow (very nicely), and doesn't get updated or developed. Having moved our workflow to github, now seems to be the

[PHP-DEV] Re: bugsnet cleanup

On 08.01.2017 at 14:31, Joe Watkins wrote: > Leaving them open isn't helping anyone or anything, and if it overwhelms me > to see that many, you can be pretty sure it has scared a bunch of people > away. I have to agree. Since others already have expressed to be in favor of a "mass cleanup",

[PHP-DEV] Re: bugsnet cleanup

Morning Christoph, > Just wiping those under the carpet wouldn't be an improvement, in my opinion. Remember that the bugs won't go anywhere, they just won't present themselves as important to new contributors, and old alike. It's very overwhelming to see a list of five thousand things that may

[PHP-DEV] Re: bugsnet cleanup

On 08.01.2017 at 07:46, Joe Watkins wrote: > Some of you may have noticed that a few of us have put considerable effort > into cleanup of pull requests on github, these are now manageable and I'm > quite confident that we will be able to merge pull requests in a timely > manner, and stay on top

[PHP-DEV] Re: bugsnet cleanup

Hi Joe, W dniu 08.01.2017 o 07:46, Joe Watkins pisze: Morning internals, Some of you may have noticed that a few of us have put considerable effort into cleanup of pull requests on github, these are now manageable and I'm quite confident that we will be able to merge pull requests in a timely