Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119965
MIME-Version: 1.0
References: <CABigaAUZAC-UgcajT5anUFJOxzTxMzNip34Jcst16A23ogpSLQ@mail.gmail.com>
 <CALKiJKqkVcnHRW=M-HByJtSRPNt9WJuwrsFZoXf3+Ju6N8MFjw@mail.gmail.com>
In-Reply-To: <CALKiJKqkVcnHRW=M-HByJtSRPNt9WJuwrsFZoXf3+Ju6N8MFjw@mail.gmail.com>
Reply-To: autaut03@gmail.com
Date: Wed, 12 Apr 2023 17:27:59 +0300
Message-ID: <CABigaAWNexHPJ=4azkMwaC6JNdFb0C7CPSLhcfEczbB5pY8q2w@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000df1d9c05f9246aa2"
Subject: Re: [PHP-DEV] Moving PHP internals to GitHub
From: autaut03@gmail.com (Alex Wells)

--000000000000df1d9c05f9246aa2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 12, 2023 at 5:16=E2=80=AFPM Rowan Tommins <rowan.collins@gmail.=
com>
wrote:

> I think "moving to a modern platform" presents a false dichotomy.
>
> Any move needs to be assessed on both the advantages and disadvantages of
> *both* (or all) options, not just what looks new and shiny if we move.
>
> Some starting points off the top of my head:
>
> * Ease of access (is subscribing to e-mail *really* harder than logging
> into Github?)
> * Notification of replies and new threads (I find Github pretty awful at
> controlling e-mails and giving useful activity overviews)
> * Handling of threads and sub-threads (at minimum, a tree view like a
> decent e-mail client; preferably, ability for trusted users to split and
> merge threads)
> * Spam control
>

Agreed. Notifications might not be the strong side of GitHub, but there's a
way to filter discussion notifications (same as subscribing to the mailing
list) and subscribe/unsubscribe to a specific discussion only. There are
also threads with replies, although there are no sub-threads.

--000000000000df1d9c05f9246aa2--