Re: Grammar issues reporting

On Thu, Jul 31, 2014 at 10:37 AM, guilhermeblanco@gmail.com <guilhermeblanco@gmail.com> wrote: > So, can we? Or does it need an RFC, blah blah blah in order to do it? > > Cheers, > > > On Thu, Jul 31, 2014 at 1:02 PM, Sara Golemon <pollita@php.net> wrote: > >> On Thu, Jul 31, 2014 at 8:30 AM, Andrea Faulds <ajf@ajf.me> wrote: >> > On 31 Jul 2014, at 03:57, guilhermeblanco@gmail.com wrote: >> >> Wouldn't be better to enable issues on Github php-langspec repo to allow >> >> faster, easier bug submission? >> >> I feel navigating through bugs.php.net overly confusing for something >> that >> >> is somehow not entirely part of php.net itself. >> > >> > I’d also like this. bugs.php.net should really be for the php.net >> implementation IMO, and GitHub issues are 1) nicer from a UX/UI standpoint, >> 2) integrate well with the repo and 3) would make it better independent >> from the implementation. >> > >> > >> +1 on using GitHub issues. I feel like they'll just get lost on >> bugs.php.net >> >> The only reason Joel and I pointed at bugs.php.net initially is that >> every other project under github.com/php has issues disabled in favor >> of bugs.php.net so the initial launch was "status quo". github is a mirror of the git.php.net repository, it is not the upstream repo. this "integration" you speak of likely means the issue referencing from commits to github issue tracker. This will clearly make absolutely no sense when using the upstream repo on git.php.net as these issue number do not exist and do not autolink or close. The same integration functionality is implemented between git.php.net and bugs.php.net. -Hannes