David Humphrey wrote:
Those people who have offered to help almost also come with changes that
would make dxr work for non-Mozilla use cases. Those are fine, but they
don't solve the main issues I get asked about by you guys.
I feel badly that dxr isn't all it could be yet, but am quite simply
overwhelmed with all the projects I lead or participate in for Mozilla.
[...] The next time I'll have any is next spring/summer.
I don't expect that the Mozilla dev will have much time to invest in
dxr, so your best chance to find more resources is to get involvement
from people outside the Mozilla team, and this is what makes having dxr
work for non-Mozilla uses a good thing to do first.
Outside of you actually *working* on dxr, some info about what is
supposed to be working, as well as what's expected or known to be broken
would be greatly useful (what you're just providing here, actually).
As well as the way you'd recommend to go for using dxr on a non-mozilla
project, is it the patch in bug 553490 ?
If you don't expect to have time until next summer, I think the best
would be to have it published somewhere where people can play and try
new changes more easily.
What would you think if someone used the Hg-Git Plugin to host a copy of
the dxr repository ( http://hg.mozilla.org/webtools/dxr ) on github ?
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
