Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97825
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.218 cause and error)
MIME-Version: 1.0
In-Reply-To: <13d379ad-cf24-6ca2-b8b9-2cd7281114fa@heigl.org>
References: <CAL=_i_nuF0y8TC_GrWsX5e77sP-jKq+ed374SW0e=VxSPniVjg@mail.gmail.com>
 <CAF+90c935-XMWDeyLEuw-Pr7Njh+Q=ZR7HT+isD9Rry-R-g2uw@mail.gmail.com>
 <f432ec0d-1836-1c5c-43d5-455c0257459e@heigl.org> <47370a17-d428-b30d-183b-c1ec96d47872@gmail.com>
 <CAL=_i_m4zegT41zOKc7+zXYN-487umJ9NKDM0KMKqMZhY81vVw@mail.gmail.com>
 <8307a455-1f57-b289-74cb-71c3a0410c92@gmail.com> <CAL=_i_k3q3-gpj2B9mS_NjsfxYjjRi0a9Wq6GHD3GEYexh=wQw@mail.gmail.com>
 <4d79d06b-671e-02c8-0e8d-d019ff57b7e0@gmail.com> <CAL=_i_neXs5qdsyKKRoT9aXr5xH=5H1BTunjk8O5=ZZzd-X7Pw@mail.gmail.com>
 <CADyq6sLadXP+Ggo=_m6HwKEd4mk9LdxudOoGtGSgHzWkCp=f9w@mail.gmail.com>
 <bd8e9381-9e50-00f7-1638-91d35520cec4@gmail.com> <53556e09-af3a-e5b1-5c82-6c974742c407@gmx.de>
 <13d379ad-cf24-6ca2-b8b9-2cd7281114fa@heigl.org>
Date: Tue, 17 Jan 2017 18:47:09 +0100
Message-ID: <CANUQDCjkjv-XEUXj4ogkdg52jVdiP+jSCqEGaR_qm1rxc0M3ZA@mail.gmail.com>
To: Andreas Heigl <andreas@heigl.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1149c5f2adf85205464de346
Subject: Re: [PHP-DEV] bugsnet cleanup
From: me@kelunik.com (Niklas Keller)

--001a1149c5f2adf85205464de346
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2017-01-17 18:22 GMT+01:00 Andreas Heigl <andreas@heigl.org>:

> Hi All.
>
> Am 17.01.17 um 17:51 schrieb Christoph M. Becker:
> > On 17.01.2017 at 17:35, Stanislav Malyshev wrote:
> >
> >>> People can now cross-reference issues, discuss, get notifications, an=
d
> >>> have some simplified/readable markup.
> >>
> >> All this, except for markup, is available on bugs.php.net. And I don't
> >> think markup is that important - I'm pretty sure one can discuss bugs =
in
> >> plain text.
> >
> > Well, what is missing is a simple means to ping another developer =E2=
=80=93
> > currently the only way to do so is assigning the ticket to them, but
> > that's not always appropriate.
> >
> Personally I think it's best for a project like the PHP-Project to stay
> as independent as possible. And that also means have our own bugtracker.
> And as the whole project is about a programming language why the heck
> should that bugtracker not be written in (vanilla) PHP.
>
> That gives us the advantage that we can decide what we need and have the
> possibility to change it according to changing needs.
>
> But that also has the disadvantage that we have to decide what we need
> and that we have to change it according to changing needs. And that is
> where I currently see an issue.
>
> Searching Bugs is - lets put it diplomatic - a challenge. The
> fulltext-search doesn't work pretty well, the list of possible
> subprojects is endless and the pull request I submitted to be able to
> search for commenters names is still sitting in the PR queue for the
> last 16 months or so.
>
> Which brings me to the next thing: It isn't clear who's in charge.
> Issues with the bug-tracker are handled in a similar timely manner as
> some issues in the language itself. So why should one invest time to
> adapt the bugtracker to our needs when no one seems to notice or care.
>
> So no wonder people are looking for alternatives. And let's be honest
> here: The UI looks pretty =E2=80=93 2001? A facelift would make a differe=
nce:
> But who would do it? And when someone would do it: Who'd actually apply i=
t?
>
> For me the Bugtracker works pretty OK. There are things that could be
> handled better but for managing issues, assigning them etc it's OK.
> Definitely not worse than Github-issues!
>
> We should work on making transparent who's in charge for the
> issue-tracker and whom to address for issues with it. Only then it's
> possible to bring people back to it and add fixes to their own itches.
>
> Like adding a PR to notify people by mentioning them. Or by allowing
> code-samples to be formatted. Because formatted code *is* easier to read
> than unformatted code. And we already make formatting in plain text, so
> why not allow that in the bug-tracker?
>
> And because there are a lot of "should"s and "could"s in there: I'd love
> to help out: But someone will need to help me (or whoever else wants to
> help) in getting to know the details and internals of =E2=80=93 internals=
? =E2=80=93 the
> system=E2=80=A6
>
> Just my 0.02 =E2=82=AC
>
> Cheers
>
> Andreas


That's exactly the issue PHP currently has, no clear responsibilities. The
mailing system is one nobody understands, the bug tracker is something
nobody cares to maintain. I can completely understand people saying PHP
should stay as independent as possible, but that only works as long as
there's one if not many to maintain our own systems.

I could help improving the bug tracker, but it's only worth if those
updates will get deployed. I even tried to get it working locally some time
ago, but had issues setting it up, I think they were related to PEAR.

Regards, Niklas

--001a1149c5f2adf85205464de346--