On Fri, Feb 22, 2013 at 8:44 AM, Martin Keckeis <martin.kecke...@gmail.com>wrote:
> 2013/2/21 Johannes Schlüter <johan...@schlueters.de> > > > On Thu, 2013-02-21 at 19:13 +0100, Pascal Chevrel wrote: > > > > > > I am specifically thinking of Bugzilla which is already used by many > > > open source projects. It has a lot more features than your current > > > bug > > > tracking system, it scales for large projects and it has a few > > > Mozilla > > > employees working full time on it. > > > > > I'm a passive user of bugzilla, not involved with any project using it > > but every time I have to report a bug on a project using it I think > > twice, why do I have to register and run away if I have to remember the > > password I used 2 years ago when reporting my last bug. > > > > bugs.php.net might not be as shiny as others but it makes reporting > > easy, fill in a captcha and you are done, no registration or such, you > > might even use a fake mail address (not that it necessarily helps to be > > unreachable for getting things resolved) > > > > And then there is a religious thing: Bugzilla is written in a legacy > > language ;-) > > > > And yes. it has some rough edges, but it get's it's job done, integrates > > with out user system, our "what's the current version"-notification > > system, ... > > > > > I think there may come many critics maybe, but why not move those things > also to github? > It's used by many people. it works, it's easy! > > Zend Framework also done the move from SVN, signing a CLA, own Bug tracking > system..... to github and I think it couldn't be better now! > it would require some changes in our process and infrastructure: - currently the bugtracker supports private bugs (mostly 0day security reports) AFAIK github doesn't have that, so we would have to use another channel (like using the secur...@php.net alone), which would be worse than the current solution when the security bugs (with all of the discussion) are opened up after the fix is released - currently we don't require a registration for reporting bugs, with the github issues the reporter needs to be registered and logged into github. - currently the bugtracker authenticates the contributers using their php.net credentials, github doesn't provide a way for that, so potentially ever contributer should be registered on github and added as a collaborator to be able to assign/edit/resolve issues. (and potentially the process should be automated, so when a php.net user is approved/granted karma he/she should be added to the collaborators automatically, I suppose there is a way to do that in the github api). - currently the bugtracker supports blocking the comments for a specific bug, github doesn't have that kind of feature. - currently the bugtracker supports providing version, OS information, the github issues doesn't have any way to have custom fields, maybe the labels/tags could be (ab)used for this, and we would need to automate this so when a new version is added, the label should automatically pushed to github. - currently the bugtracker supports providing package information, that would either require us to split the php-src repo into multiple repositories (ext/*, Zend/, etc. this would be a bad idea imo) or we would need to use labels for this also(and the labels should.be automatically updated when a new package is created). - currently the bugtracker supports providing bugtype information(bug, feature request, documentation issue, security), see above. - currently the bugtracker supports closing the issues with Quick Fixes, where there is a predefined comment automatically added to the bug so we don't have to copypaste the resolution message for similar bugs (that the website/docs related fixes needs time to propagate, that fixing a bug in the head means that it will be fixed in a future release etc.), github issues doesn't have this kind of feature. These are the issues(from the top of my head) which need to be resolved if/when we wanna move the tracker to github. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
