Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Sonar is the ultimate open source platform to manage code quality.

Title

Add portal layout to Sonar dashboards with low footprint

Keywords

Java, Ruby, JavaScript

Description

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
  • Add a way to personalize widgets

    Once this is completed dashboards will be fully configurable. A global Sonar Dashboard (similar to Jira dashboard but lighter) can be implemented. Example of widgets that could be added into the global dashboard :
    • My favorite projects
    • Top 5 worse projects (for tests/duplications/design/...)
    • Top 5 biggest projects
    • ...

Mentor(s)

Freddy Mallet , Simon Brandhof

Constraint

the footprint of the portal layout technology must be low



Title

Integration of Sonar in IDE to enable instant feedback to developer

Keywords

Java, Eclipse, IDEA

Description

The Sonar web server Live demo provides code quality information to development projects stakeholders : developers, architects, managers, customers,... From a developer's point of view, quality information should be directly available in his IDE to make use of Sonar fully efficient and make the whole process very natural.

  • 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 in the IDE.
  • Second version of the plugins will analyze locally the changes before they are committed. The following solutions could be explored :
    • Bootstrap the analyzers without need of Maven
    • Deactivate certain analyzers (for example Findbugs)
    • Run analyzers only on the code changed

Mentor(s)

Simon Brandhof, Freddy Mallet



Title

Extend Sonar to detect cross project dependencies and duplications

Keywords

Java, Maven, CPD, bytecode

Description

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.

Mentor(s)

Simon Brandhof, Freddy Mallet

  • No labels