Legal
======

This section specifies the supported restrictions in CodeScene's functionality.

Appply Legal Restrictions
-------------------------

Some analysis information from CodeScene may be considered sensitive from a legal perspective. This is a topic
that varies between different jurisdictions and/or company policies. Thus, CodeScene provides configuration
options that let you disable such information.

Disable the Author Statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CodeScene provides an aggregated view of all author contributions. This information is intended as descriptive data that
lets you find long-term contributors as shown in :numref:`detailed-author-statistics`.

.. figure:: DetailedAuthorStatistics.png
   :alt: An example of detailed author statistics
   :name: detailed-author-statistics

   The detailed author statistics show the aggregated contributions.

You disable this analysis by logging in as an administrator, click the Configuration tab in the top bar, and check the box as shown in :numref:`configure-hide-sensitive`.

.. figure:: HideSensitiveInformation.png
   :alt: Configure the visibility of sensitive information
   :name: configure-hide-sensitive

   The configuration lets a CodeScene administrator disable sensitive information.

Disable the Off-Boarding Simulation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The off-boarding simulation lets you simulate the impact in case individual developers leave the organization.
You disable the off-boarding simulation as shown in :numref:`disable-simulator2`.

.. figure:: disable-simulator.png
   :alt: Disable the off-boarding simulator
   :name: disable-simulator2

   The off-boarding simulation can be disabled in the global configuration.

A Warning on Performance Evaluations
------------------------------------

The detailed author statistics are useful in order to find the people that carry the history of your codebase and product in their head.
Their stories often complement the analysis results and help you put your findings into context.

We strongly recommend against using this data for performance evaluations. That isn't the purpose of these analyses.
The reason we advice against this is part ethical and part practical. In particular, once someone starts to evaluate
contributors people will adapt by optimizing for what's being measured. For example, if I'm evaluated by how many commits
I do I'll increase the number of commits. My commits will no longer carry any meaning, but my statistics "improve". In
addition, using this data for performance evaluation is likely to destroy the team dynamics. Again, if I'm measured by
how many commits or lines of code I produce I'm less likely to invest time in supporting my peers and we end up with
local optimizations that hurt the overall productivity.

Open Source Attributions
------------------------

D3
~~

.. code-block:: text

        Copyright 2010-2020 Mike Bostock
        All rights reserved.

        Redistribution and use in source and binary forms, with or without modification,
        are permitted provided that the following conditions are met:

        * Redistributions of source code must retain the above copyright notice, this
          list of conditions and the following disclaimer.

        * Redistributions in binary form must reproduce the above copyright notice,
          this list of conditions and the following disclaimer in the documentation
          and/or other materials provided with the distribution.

        * Neither the name of the author nor the names of contributors may be used to
          endorse or promote products derived from this software without specific prior
          written permission.

        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
        ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
        WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
        DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
        ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
        (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
        LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
        ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
        (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
        SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
