Re: Moving PHP internals to GitHub
| From: | Lydia de Jongh | Date: | Wed, 12 Apr 2023 20:10:55 +0000 |
| Subject: | Re: Moving PHP internals to GitHub | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119998@lists.php.net to get a copy of this message | ||
Hi,
Interesting discussion....
I do prefer a good organised forum above a mailinglist:
- better overview
- better searchable
- quicker to read
- less mail
- possibility to give likes
As a newcomer here, it is hard to find previous information. Even on
externals.io.
That signing on to the mailinglist is a little difficult is an advantage
for a list like this and at the other hand should not be a problem for a
developer...;-p
But Github would not be my choice for a forum.
Greetz,
flexJoly
Op wo 12 apr 2023 om 16:16 schreef Rowan Tommins <rowan.collins@gmail.com>:
> On Wed, 12 Apr 2023 at 14:53, Alex Wells <autaut03@gmail.com> wrote:
>
> >
> > Based on those issues and PHP, I propose moving the discussions
> elsewhere -
> > to some kind of modern platform.
>
>
>
> This has been discussed before, many times, so I'll keep this brief and let
> you find the old discussions.
>
> 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
>
> Regards,
> --
> Rowan Tommins
> [IMSoP]
>