Google Summer of Code started the previous week, I can’t believe I haven’t blogged anything yet about the topic.
Let me talk a little about me, my name is Néstor Salceda and I’m studying Computer Science and, perhaps, someone will known me yet because this is my second year as student in the Summer of Code, the first year was wonderful and I decided apply other time 
This year, my goal is to enhace Gendarme in order to be more useful to the Mono Project itself. For achieving this goal I have identified 4 key tasks:
- Apply the existing rules.
- Write new rules, putting special effort in write useful rules for implementing the class libraries.
- Apply the new rules to the class libraries.
- Automated Gendarme Reports generation and publication.
And finally, good luck for all students, and thanks to Mono Project for the opportunity
4 comments ↓
I was thinking that it might be interesting for you to add collapsing support to results if you had the time. I don’t know if you already have it in the report view. But I think it would be cool to allow grouping of rows like google conversations. The criteria for grouping could be things like same class, namespace, etc.
Yes, currently in the HTML views, Sebastien added support for collapsing results, files and rules.
Take a look at this page
Thanks for the suggestion!
Ok, I think it is good that it has collapsing for those rules. I guess, what is different is that this is a rule-oriented presentation of the results. If you had another view for source code results then I would imagine something like this:
System.XML (9) defects.
System.Collections.* (10).
Basically it would be nice to have a better overview if I had a large source code base.
That way I can examine the defects a little easier. In that one there was 367.
Ahh, okey okey.
Yes, currently this week I’m working in that. I hope the next week, I will have something to show.
This is my inspiration: Findbugs Report
Are you referring this, aren’t you?
Leave a Comment