SonarSource sponsors two mailing list communities, one for users of SonarQube, and one for people who want to extend SonarQube with plugins and other coding endeavors. We invite you to join us, and ask only that you respect a few basic courtesies.

User List

This list is for all the users of SonarQube, from the admins to the end users. If it has to do with installing, maintaining, updating, upgrading, analyzing or using the interface, this is the place to ask it. You can browse the list archive on Nabble or Markmail.
To post a message, you should first subscribe, read the guidelines below, and then send an email to user@sonar.codehaus.org.

Developer List

If you’re interested in SonarQube under the covers, this is the list for you. This community talks about developing SonarQube itself – plugins, web services and applications. You can browse the list archive on Nabble or Markmail.
To post a message, you should first subscribe, read the guidelines below, and then send an email to dev@sonar.codehaus.org.

Note that joining the list doesn’t make you a voting member – only plugin contributors and SonarQube developers get a vote, so when a vote is called, sit on your hands if you’re not a contributor.

Guidelines

  • Be polite – say “Hello” if it’s your first post. Don’t be rude or abrupt. Throw in a “thank you” every once in a while.
  • Explain yourself clearly – if you’re having a problem, give enough detail to help others help you. If you have a suggestion or an idea try to explain it clearly and give the advantages you see.
  • Don’t trash talk – everyone has feelings, and the members of SonarSource and the SonarQube community have worked hard to offer you a whole lot of high quality software for free. Please keep that in mind when you’re frustrated by some decision or “feature” that you consider short-sighted.
  • Don’t expect instant turnaround – operators are not standing by. There is no one who’s job it is to wait for your email and answer it immediately. The community is peopled primarily of users just like you who have jobs and lives that take up most of their time. In their free moments they try to help each other – and you – out.

Writing an effective post

When you write in to either community for help, there are a few things to include to help the community members help you

  • Version of SonarQube
  • If you’re having an analysis problem
    • Version of the analyzer – be sure to provide the details of how you’re analyzing, including which analysis engine you’re using, SonarQube Runner, Maven, etc., and its version
    • Project configuration file (sonar-project.properties, pom.xml, etc.)
    • Complete log from analysis run in debug mode (-X)
  • If you’re having some other problem
    • Version of the tool in question – for example if you need help with the Eclipse plugin, provide the version of Eclipse and the version of the plugin you’re running.

© 2008-2013, SonarSource S.A, Switzerland. All content is copyright protected. SONARQUBE and SONARSOURCE are
trademarks of SonarSource SA. All other trademarks and copyrights are the property of their respective owners. All rights are expressly reserved.