Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107220
MIME-Version: 1.0
References: <CA+kxMuTzACohxJcjs43f8xsJPGSMKtDygxje0r2QPmrhFiiRiQ@mail.gmail.com>
In-Reply-To: <CA+kxMuTzACohxJcjs43f8xsJPGSMKtDygxje0r2QPmrhFiiRiQ@mail.gmail.com>
Reply-To: bishop@php.net
Date: Wed, 18 Sep 2019 17:11:48 -0400
Message-ID: <CAEYWF=6BGFFu+c1VCZJoZA4Ax7hJnee514DLjbYpzd_XazV+rQ@mail.gmail.com>
To: Dan Ackroyd <Danack@basereality.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008b65600592da4aad"
Subject: Re: [PHP-DEV] Improving productivity of internals mailing list
From: bishop@php.net (Bishop Bettini)

--0000000000008b65600592da4aad
Content-Type: text/plain; charset="UTF-8"

On Wed, Sep 18, 2019 at 1:33 PM Dan Ackroyd <Danack@basereality.com> wrote:

>
> ...
>
> # Problem 1 - It's really hard to see what is being or could be worked on.
>
> People sometimes announce things that they think could be worked on
> through the internals list, in the hope that people might want to help
> them do that work. Or sometimes just as a hope that someone else would
> pickup that work.
>
> That information is really hard to find.
>
> # Solution
>
> As an experiment I'm going to attempt to keep a list of items that
> could be worked on over at
> https://github.com/Danack/RfcCodex/project_coordination.md alongside
> the curated summary of discussions of common ideas for RFC that failed
> to reach approval.
>

Thanks, Dan. While bugs.php.net is our canonical to do list, it doesn't
have much in the way of planning features. For the phar and imap extension,
I maintain a supplemental list on my whiteboard -- but that's no way to
share the load. I'd like to see bugs.php.net grow to be more of a project
management platform, but for now, I like where you're headed with a simple
list. I've created a PR for the extensions I maintain, and I hope other
maintainers will do the same.

--0000000000008b65600592da4aad--