Removed enlistment, summary stays

Can you please fix this for project 5907. It's just so annoying to see nonsense like "decreasing development activity" etc there, just because ohloh's measurement approach is so horribly broken and cannot work on a complete repository. Sorry for being bitter, but this hurts projects. Especially with your comparison feature. Before you do that, you really should get a proper foundation done that allows fair comparisons. That includes giving the option to exclude certain paths from the metrics (say, generated XML data or vendor libraries or whatever).

Would that be possible, please? I'd really much rather have no statistics than completely wrong statistics. Thanks.

The coding experience does not worry me, but the kudos... hm. I have fewer kudos than the project has stacks, though. How does that work exactly? And isn't that stuff added again when I add enlistements back in?

Okay, then I think it's fine if you go ahead and remove the report. I just hope nobody else adds an enlistement soon afterwards or I need to bother you guys again. Any idea when a new system for this is implemented? I once proposed that activity is measured using an entire repos (or parts of it), and then one would add a separate, dedicated repository path just for the code metrics.