title: Using sonar in pretty big team
body: <p>We have something about 20 people in our team and we are using sonar for now to analyse new code before submiting it to the main stream. So each designer uses it's own Sonar installed on his machine.  </p>
  
  <p>What I'm trying to do is to create a one instance of the Sonar which each designer will be able to use. The only concern I have is what will happen if:</p>
  
  <ol>
  <li>One designer will launch analysis on one revision of file and right after that the second designer will launch analysis on another revision of this file (in the worst case we can have a bunch of such a files). First designer won't be able to see his violations and won't be able to see code he wrote at all. Do we have some mechanism to overcome this?</li>
  <li>What will happen if two designers will analyse the same project at the same time? AFAIK, Sonar won't allow them to do so. Any workaround for this?  </li>
  </ol>
  
  <p>Of course, we can, somaehow, create a project on the sonar side for each team member, but this has it's drawbacks, such as issues, marked as false positive in one proect won't appear as such an issues in another project and so on.  </p>
  
  <p>Any ideas on such an issues?</p>