Sonar is the ultimate open source platform to manage code quality.
Add a light portal layout to Sonar dashboards
Widgets can already be added to Sonar dashboards (Live example on Nemo). However, those widgets cannot be organized by the end user.
Add a way to drag & drop widgets
Add a way to add & remove widgets
Optionally add a way to personalize widget
Once done the Sonar project dashboards will be fully configurable and a new global Sonar Dashboard (kind of light Jira dashboard) could be implemented with the same technology. Example of global widgets :
My favorite projects
Top 5 worst projects (by tests/duplications/design/...)
Top 5 biggest projects
Freddy Mallet , Simon Brandhof
the footprint of the portal layout technology must be light
Bring a new dimension to the Sonar platform with the Sonar-IDE plugins
Java, Eclipse, IDEA
The Sonar web server Live demo provides code quality information to any stakeholders on a development project : developers, architects, managers, customers,... But from a developer's point of view, all those quality information should be directly available in his favorite IDE to make use of Sonar fully efficient.
First version of the plugins should make available at file level the following information stored remotely on the Sonar Web Server : violations, duplications, code coverage and metrics (loc, statements, complexity, lcom4, rfc, ...). The source code should be decorated on the fly into the IDE.
Second version of the plugins should allow developers to analyse locally theirs changes before committing anything. This second version could imply the following things :
Possibility to bootstrap the Sonar analysers without need of Maven
Integration of this bootstrap into the Sonar-IDE plugins
Possibility to deactivate some analyser (for instance Findbugs)
Possibility to launch analysers only on code changes
Simon Brandhof, Freddy Mallet
Extend Sonar to detect cross project dependencies and duplications
Java, Maven, CPD, bytecode
Sonar can fully analyse any java project according to 7 quality axes : duplications, complexity distribution, design, unit tests, comments, coding best practices, potential bugs. But two axes (duplications and design) will be more valuable if a cross-projects analysis was also done. Indeed :
That good to don't have any duplications inside a projet but it's even better to don't share any source code with another project
Robert C. Martin's metrics like Instability, Abstractness and Distance doesn't mean anything when external ingoing and outgoing dependencies are not taken into account.
The mission is : find a way to detect and report those cross projects dependencies and duplications.