[sr-dev] issue tracking system

Hello, sightly off-topic and cc-ed to users mailing lists, but hopefully there will be people giving valuable feedback based on their experience. When we started the integration of source code for kamailio and ser, we went for FlySpray as issue tracking system (aka bug tracker). The project seems to be dead, nothing happened to it for long time, no updates and there are warnings using latest php versions, that may result in malfunctionality or no-functionality with future versions. Therefore maybe it is the time to make a decision, rather soon than later, but this time we should look a bit more carefully to available options, to avoid ending up (in short time) to the same issue. I see two major options: A) going to use a source code hosting portal for bug traker (like sourceforge, berlios, github, a.s.o.) B) going to use an existing software to be installed on our server and managed by us I tend to go for A) as the maintenance of the software will not be done by us. I do not know which would be the best choice to go for. Of course, we should consider possible down times (like it happened in the past) or slow connection to their servers. B) will give us full control, but then it is about the time to maintain it (upgrades, security patches, a.s.o.). More than that, it is about selecting the right software to go with. Since SEMS code is now hosted in GIT repo of sip-router.org, maybe the tracker can be used by them as well, eventually by future related projects hosted in our git. Opinions? Thanks, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda