Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116315
Return-Path: <nikita.ppv@gmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 91060 invoked from network); 10 Nov 2021 15:58:39 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 10 Nov 2021 15:58:39 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 9C2301804C4
	for <internals@lists.php.net>; Wed, 10 Nov 2021 08:52:08 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS15169 209.85.128.0/17
X-Spam-Virus: No
X-Envelope-From: <nikita.ppv@gmail.com>
Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Wed, 10 Nov 2021 08:52:08 -0800 (PST)
Received: by mail-ed1-f53.google.com with SMTP id r12so13087089edt.6
        for <internals@lists.php.net>; Wed, 10 Nov 2021 08:52:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=a6XGsfJ2RMcmp3TJijWQblY+J1pPOzZg+90ji40Db6k=;
        b=ks6x6xY19r6skEWTMp199h+JKcrwYavA78kmky+Jaxe/qUyr/5iNNTlCB8xgHa4lTz
         nDLcp+mmA0tF+234nmrIvBetA5nlOMsWoESlAua1bbgEM9Pb8FrLDQlZT0VI3fbRlEyq
         jIVUq15iRfQOssWnMGhXH1+uOrMh+IF1/yk9klMWzQEtridAF2d0iPS4qfvG0N7VzxXG
         OptkD725g+gCbfzi+2anWE1o0vjnDZAylHGln53yiuZq0Yb5UeL1DsX+KDnYGmTUbrd7
         mtfalP2I6JsZoeYAqTtaA6fRovrqmalnutxYtu9F6DmXyW9LAQSTkO8X3nMoH0Cr9EYe
         tstQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=a6XGsfJ2RMcmp3TJijWQblY+J1pPOzZg+90ji40Db6k=;
        b=dPXoFiZHmxXL8UWXQicnOLkgz6aSNAXPm38NONDMFTpH1+tGcKeLu8HEBhlyH7OH6q
         JBYES9ra7M9KiyUcZW0RexoRhquY4W2BX39AHCY6FUiI9nLmIf9ZSu/U09QzelV1NiQP
         M9pg9KzolY/2wbXKR/IDsSZArQNCeGNOuY6g6lQt6Hqqrv0vVUk62dCDeSyaEn/d0JyP
         DS9+MqJaFDxWwE6b2EB/oAO5QOeiRW/vxEHQ0gelhV1Z1beKOZKom+0q9IGyGMwXZ2eZ
         nVu4yxy38oy01rT3sWTp2xolOiPp7mlPhlHXvGPTQaxN7F11BMiCKmaZK3QMGkq/w0o9
         Iy4w==
X-Gm-Message-State: AOAM5322gXwJCHPdkSXvVmcnSAqB+xzeo/9lfdaRenvxlktg+rxEKGT3
	XvDShEd6PIzZ/mrzW5J1v8VtjAzCR/+mMOaJ6xRgVzez
X-Google-Smtp-Source: ABdhPJyO6Qui11C2c50RH/oWw/g4VxiLzBLZ0o0laZhIqbNtTlUTM2yypaykZ/uJteTureJuUkJ2WrR7HxFKmDUY/ro=
X-Received: by 2002:aa7:cdc9:: with SMTP id h9mr462177edw.370.1636563124133;
 Wed, 10 Nov 2021 08:52:04 -0800 (PST)
MIME-Version: 1.0
References: <CAF+90c90pTtjxuMaQ88h+njhByfbv4qs=xx72CVPSw40tde6Cg@mail.gmail.com>
 <CA+kxMuSmBVqgNdg0n1+aDd9vHC-dpcDK0x8q5Be8U5mVtck9CQ@mail.gmail.com>
In-Reply-To: <CA+kxMuSmBVqgNdg0n1+aDd9vHC-dpcDK0x8q5Be8U5mVtck9CQ@mail.gmail.com>
Date: Wed, 10 Nov 2021 17:51:47 +0100
Message-ID: <CAF+90c_hinbidrXTp7oghqo373VQB9XdeBpp3hF7010_ORH6Zg@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000aaa37c05d0720b79"
Subject: Re: [PHP-DEV] [RFC] Migrating to GitHub issues
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000aaa37c05d0720b79
Content-Type: text/plain; charset="UTF-8"

On Thu, Nov 4, 2021 at 5:58 PM Dan Ackroyd <Danack@basereality.com> wrote:

> On Tue, 2 Nov 2021 at 14:19, Nikita Popov <nikita.ppv@gmail.com> wrote:
> >
> > I'd like to formally propose to use GitHub for PHP implementation issues
> as
> > well: https://wiki.php.net/rfc/github_issues
>
> In general, yes please. The only bit I'll chime in on is:
>
> > bugs.php.net will remain active for the following purposes:
> > Reporting of issues against PECL extensions. (We may want to discontinue
> > this as well. Many actively maintained extensions already use GitHub
> issues
> > rather than bugs.php.net.)
>
>
> Providing a bug reporting site was a useful thing to do 23 years ago,
> as it would have been either expensive or time consuming for each
> project to set up their own. It doesn't seem as sensible now as:
>
> * Having bugs.php.net remain open for some bits of PHP, but not
> others, would be confusing for users.
>
> * Most extensions are hosted on a platform that already provides issue
> tracking - though it seems quite a few extensions (including Imagick)
> have not realised that there is a bug tracking setting that can/should
> be updated on pecl.
>
> * There's an ongoing issue of extensions becoming unmaintained over
> time. If people are opening bugs on the PHP issue tracker, it's
> natural for them to have an expectation that someone from the PHP
> project would work on that issue at some point.
>
> So unless someone has a strong argument for keeping the bugs.php.net
> open for PECL extensions, I think it shouldn't be.
>
> btw it would probably be useful to dump out a list of where to report
> bugs for different extensions and put that as a page on bugs.php.net
> though. If nothing else, Google thinks Imagick is an alias for
> ImageMagick far too often and sometimes pecl.php.net is unresponsive.


Yes, we should definitely migrate PECL extensions away from bugs.php.net as
well. I didn't cover this in the RFC because it doesn't really relate to
the setup described there and this part of the migration can happen in
parallel.

To migrate PECL extensions hosted by the PHP organization away from
bugs.php.net, we need to:
1. Enable GH issues on the repo.
2. Disable the package on bugs.php.net.
3. Update the bug tracker URL on pecl.php.net.
4. (Maybe) manually migrate outstanding open bugs.

For extensions not hosted by the PHP organization we may have to contact
maintainers to determine which issue tracker to use.

Regards,
Nikita

--000000000000aaa37c05d0720b79--