> > > Well, there are a couple of reasons. The first is that I don't really know > what it's going to take to fix these issues, I just have a decent idea of > what > kind of story point estimates we would have given these issues back when I > was doing this kind of work and I also have a decent idea of the kinds > of problems that might be contributing to these issues are... I also know > a good approximation for an average number of story points that Digium's > developers complete each week which is why I think this is going to be as > much work as it is. I fully expect this list of tasks to be riddled with > little > gotchas and for a lot of them to have a decent amount of startup time just > in figuring out how to reproduce them. The other reason I haven't fixed > them is because I don't get payed to work on Asterisk anymore and the > promise of maybe getting five-hundred dollars for what I predict to be over > 80 hours worth of work (and would quite likely be a lot more since > res_pjsip isn't one of my core areas of experience) just isn't worth the > effort. > This isn't about the complexities by the way, all the PJSIP components of > Asterisk are actually rather self-contained. > > I mean, feel free to give it a shot, but this bounty is hardly a real > incentive. >
Aaaand I just realized the post I was responding to was directed at the guy offering the bounty. My bad. -- *Jonathan R. Rose*Senior Systems Engineer Emergency CallWorks Motorola Solutions email: jonathan.r...@motorolasolutions.com
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
