Re: [STANDARDS] Grammar issues reporting

On Fri, Aug 1, 2014 at 9:16 AM, Joel Marcey <[email protected]> wrote:
>
>
> On 7/31/14, 3:09 PM, "Andrea Faulds" <[email protected]> wrote:
>
>>I don¹t really want to argue much more about it, but there are legitimate
>>reasons to consider not using the php.net infrastructure, if anything
>>because it¹s associated with the php.net implementation. I suppose it
>>would make sense given we¹re already using git.php.net to use the bug
>>tracker, granted, but as I have said, it would work fine with GitHub
>>issues. A key advantage of GitHub is that it is simpler and more
>>user-friendly, plus it actually directly supports markdown, including in
>>bug reports and pull requests. It also means we could completely separate
>>php.net implementation and documentation bugs (go to php.net), HHVM
>>implementation and documentation bugs (go to HHVM¹s tracker), and bugs in
>>the language specification itself (go to the language spec Issues on
>>GitHub).
>
> So where are we landing on this? GitHub or no GitHub? One thing that is
> good about GitHub is the consistency of UI for both pull requests and
> issues. On the other hand, it would diverge from the norm. We should
> decide soon because there is momentum for feedback. I saw PHP Language
> Specification under Package affected at bugs.php.net (it is the very last
> option; maybe we can bump that towards the top, at least initially while
> the iron is hot for the spec??).


The README has a direct link that prefills the "package name":
https://bugs.php.net/report.php?package_name=PHP+Language+Specification

I'm unsure where it fits better then at the bottom of the list, all
other "top level" items are php specifc?

-Hannes