Re: [STANDARDS] Grammar issues reporting
[email protected] (Andrea Faulds)
| Newsgroups | php.standards |
|---|---|
| Message-ID | <[email protected]> |
On 31 Jul 2014, at 22:58, Hannes Magnusson <[email protected]> wrote: > 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. I really don’t think this is a bicycle-shed kind of issue. Granted, it’s off-topic from what this thread should be about but we should still discuss this. 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). Related to that, it’s worth discussing docs here. Are they to be implementation-independent and mention no implementation? Should they cover what multiple implementations do, including HHVM? I notice HHVM also has docs, a fork of the php.net ones. Anyhow, I won’t speak much more on this. I am only to willing to send one more email on this matter, at least in this thread. If someone else thinks it’s important enough, they can start a new thread. -- Andrea Faulds http://ajf.me/