Le 21/02/2013 18:56, Ferenc Kovacs a écrit :
it is, and it is a chicken and egg problem: even though that the usual "my C-fu is weak" argument doesn't apply there, we still lack contributors, and the archaic nature of the current codebase doesn't really helps bringing in new people. even if a newcomer would come around with a rewrite of the current bugtracker based on some modern framework (ZF2/sf2/etc.), it would be a hard decision, because who who knows what new bugs that codebase has and there would be a real issue if the original author leaves and there would be no people left having familiar with the codebase. the current codebase sucks, but it had time for the bugs to surface, and the people who work on it are familiar with it.
Maybe using a bug tracking system that is maintained by another project would be a good idea?
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.
Pascal -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
