On Wed, Apr 12, 2023 at 04:52:52PM +0300, Alex Wells wrote:

> Based on those issues and PHP, I propose moving the discussions elsewhere -
> to some kind of modern platform. Since this is quite a big change in the
> processes used, I imagine an RFC would be needed. But before I do that I
> want to measure the reactions. If it goes well, I'll proceed with an RFC
> draft.

Please: No.

The nice thing about email is that stuff just hits my mailbox and I deal with
it when I have time. I have my MUA (mutt) always running, I do not want to have
something else to monitor.

Your points:

* having to subscribe. An easy one off task.

* Archives: already done

* Having to learn rules, bottom posting. All communities have rules. As you
say: not hard

* Not way of editing: just send a follow up.

* No formatting. What is wrong with plain text, it is how PHP is written ?

* No reactions. If people are interested they will reply.

I agree that one flaw with email is that it is not good at remembering things,
that is why people do things like writing RFCs.

Note: I mainly lurk on this list, only occasionally making comments.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT 
Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: 
https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php

Reply via email to