Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119991
Message-ID: <173f41e5-7271-cf59-c8aa-b4adc83f8802@cubiclesoft.com>
Date: Wed, 12 Apr 2023 12:36:02 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120327
 Thunderbird/11.0.1
Content-Language: en-US
To: autaut03@gmail.com, PHP Developers Mailing List <internals@lists.php.net>
References: <CABigaAUZAC-UgcajT5anUFJOxzTxMzNip34Jcst16A23ogpSLQ@mail.gmail.com>
In-Reply-To: <CABigaAUZAC-UgcajT5anUFJOxzTxMzNip34Jcst16A23ogpSLQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Moving PHP internals to GitHub
From: thruska@cubiclesoft.com (Thomas Hruska)

On 4/12/2023 6:52 AM, Alex Wells wrote:
> Hey.
> 
> PHP currently uses internals@lists.php.net for communication. That includes
> mostly RFCs (or their votings, or their pre-discussion) and sometimes
> questions about the implementation or possible bugs.
> 
> What are your thoughts?

The subject line reads as if the mailing list is actually moving.


This is the second major mailing list in the past few weeks that I'm on 
where this exact topic has arisen.  On the other list, the developers of 
the project were the ones who proposed it and the idea was universally 
and unilaterally rejected by all participants.

Communication on GitHub is awkward at best.  GitHub works well as an 
issue tracker for bugs and hosting source code in a central location in 
a way that allows merges to get done without driving everyone up a wall. 
  It's largely terrible at everything else.

As someone who maintains an email server, I completely understand that 
maintaining a functioning email server today has intentionally been made 
prohibitively difficult by Google, Microsoft, and major telecoms in 
their overzealous and extremely misguided attempts to bounce block all 
incoming messaging even from properly configured servers.  And those 
same companies are also to blame for creating broken-by-design email 
clients that no one should be using.  But the IETF shares the majority 
of the blame for _actively_ not fixing numerous issues with email at the 
protocol level.  Running away from email isn't the right solution though.

-- 
Thomas Hruska
CubicleSoft President

CubicleSoft has over 80 original open source projects and counting.
Plus a couple of commercial/retail products.

What software are you looking to build?