Re: [STANDARDS] Grammar issues reporting

On Thu, Jul 31, 2014 at 2:54 PM, Andrea Faulds <[email protected]> wrote:
>
> On 31 Jul 2014, at 22:48, Hannes Magnusson <[email protected]> wrote:
>
>> I'm unclear on what you are unclear on, and what is the problem you
>> are attempting to resolve.
>>
>> The issue# to git commit and vice-versa is implemented in the PHP.net
>> infrastructure.
>> You report tickets at:
>> https://bugs.php.net/report.php?package_name=PHP+Language+Specification
>> You browse tickets at:
>> https://bugs.php.net/search.php?cmd=display&status=Open&package_name%5B%5D=PHP+Language+Specification
>> You reference ticket with "bug #xyz" in the commit message.
>> You push to git.php.net.
>> The ticket will be updated to include a reference to the commit.
>> You browse the git history and see a ticket# in the commit logs... You
>> look it up on bugs.php.net/<ticket>
>> If you reference a GitHub issue# in the commit message then looking up
>> that reference on bugs.php.net/ is not going to work.
>>
>> This is the same issue as when corporates have their own issue
>> trackers and reference their tickets in our repositories. These
>> references make no sense for PHP.net devs and should not be used.
>>
>> The GitHub repo is a fake mirror. It cannot be pushed to (well, it
>> can, but then you fuckup a lot of things, which is why "noone" has
>> push karma to the repos).
>>
>> If you require further explanation lets take it off list so we don't
>> have to waste everyone else time.
>
> Right, I just don’t understand why what you’ve described is a problem if we switch issues to GitHub. You cannot push *yourself* to GitHub, but it is still a mirror and thus (though this may need to be tested), I suspect pull request, commit and issue referencing *on GitHub* will work fine. Obviously it won’t sync with bugs.php.net, but the point is we’d be having specification bugs *on GitHub*, and *on GitHub* they will presumably work fine as, in the end, the source is on GitHub.
> --


Lets not be repainting the sheds on every topic here.
We have perfectly fine and capable infrastructure. There would need to
be severely compelling argument to change that. (and no, "I like blue
better" is not a valid argument).

Now, again I ask you, if you'd like to waste more time on the color,
lets do so off-list so not to waste everyones time.

-Hannes