Re: Experimental opening of php/doc-en issues

On Fri, Oct 22, 2021 at 10:42 AM Peter Cowburn <[email protected]>
wrote:

>
>
> On Thu, 21 Oct 2021 at 16:02, Christoph M. Becker <[email protected]>
> wrote:
>
>> On 21.10.2021 at 16:33, Nikita Popov wrote:
>> >
>> > To follow up on this, I'd like to disable the option to submit a
>> > "Documentation Problem" on bugs.php.net with
>> > https://github.com/php/web-bugs/pull/107. Instead, submitters are
>> directed
>> > to issues on php/doc-en. This avoids having two places where new
>> > documentation bugs may be submitted. Are there any objections to doing
>> > this? (It's still possible to reclassify submitted bugs as doc problems
>> > after the fact.)
>>
>> +1
>>
>
> In principle, I'm +1.
>
> Is there any project/team that would be blocked by this? I'm thinking
> along the lines of maaaaybe a PECL package that doesn't have their docs in
> php/doc-* but does use the bug tracker.
>

Here's the intersection of "Documentation Problem" and "PECL":
https://bugs.php.net/search.php?limit=40&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=Documentation+Problem&project=PECL
From a cursory look I can only spot the "uuid" extension missing from
php.net -- and the bug report is complaining about precisely that fact :)
So it doesn't seem like PECL exts are using bugs.php.net to track their
custom documentation.


> I'm going to assume this also affects the "Documentation Problem" package
> as well as the ticket type, right?
>

I haven't disabled that one yet, but I agree we should. Actually, this
should have happened ages ago, ever since "Documentation Problem" became a
separate bug type rather than a package.


> If directing submitters to one other place to create their issue, it
> should be an appropriate place for all documentation issues.
> github.com/php/doc-en is not that place.
>

To clarify, are you talking about translations here? We could adjust the
issue creation process on doc-en to link to other repos for translation
issues, though I think it's also fine to let people report translation
issues on doc-en, which we then transfer to a more appropriate repo.
Depends on how common they are. In either case doc-en would be the entry
point though, just a question of adjusting issue templates.

Regards,
Nikita