Hi! > People can now cross-reference issues, discuss, get notifications, and > have some simplified/readable markup.
All this, except for markup, is available on bugs.php.net. And I don't think markup is that important - I'm pretty sure one can discuss bugs in plain text. > For the 99% of developers, this is better than any self-hosted tool with > its own workflow, and also more familiar (we all use Github, unless we > live under a rock, which is the 1%). There's a lot of use of github as code distribution/review tool, true. Github as a project management/bug tracking tool is much less widely used, and for a reason - it lacks a lot of capabilities such tools should have. It is a very mediocre bug tracking/project management tool, and that's charitable. It's not their fault - github never was targeted at this and their issue tracking capabilities clearly target smaller and simpler projects with less advanced needs. But I don't think it would work well for a bigger one. Trading superior solution for a clearly inferior one because "all cool boys do it" does not look like something we should do. > Still, activity buzzed after the move. > Yes, it is chaotic, but at least people can help out, cross-link, and > generally be more part of the workflow. Again, people can do all this on bugs.php.net. If there are real problem with it, we should fix it. If the problem is "oh, I need to type different URL, that's too much for me!" - maybe it's not the kind of buzzing we want to get. > As it currently stands, I only go to bugs.php.net <http://bugs.php.net> > to create a github issue where I link it as reference. What prevents you from being able to create proper issues on bugs.php.net? -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
