{% extends "cacsremoteservice/views/layouts/master.html" %}

{% block secondary-nav %}
{% include "cacsremoteservice/views/developer-configuration/developer-configuration-header.html" with item=item tabs=tabs %}
{% endblock %}

{% block scripts %}
<script type="text/javascript">
  codescene.views.developerConfiguration.developersTable.init(
    {
      mountPoint:    document.getElementById('update-developers'),
      projectId: {{ item.id }},
      viewContext: '{{ view-context }}',
      product: 'enterprise',
      developers: {{ developers|json|safe }},
      potentialExDevs: {{ potential-ex-devs|json|safe }},
      teamlessAuthors: {{ teamless-authors|json|safe }},
      teams: {{ teams|json|safe }}
    }
  );
</script>
{% endblock %}


{% block main %}
<div class="developer-configuration-developers-view" id="page-body">
  <div class="text-content">
    <h2>Configure Developers: enable team and organizational analyses</h2>
    <p class="lead text-muted">
      Assign <a
               href='{{view-context}}/developer-configurations/{{item.id}}/teams'>teams</a> to your developer to enable the organizational analyses. You may also mark a developer as Ex-Developer to analyze the impact if those developers have left your organization.
    </p>
    <p class="lead text-muted">
      You can also use the <a href="{{view-context}}/developer-configurations/{{item.id }}/mapping"> Developer identity mapping
	interface</a> to associate multiple version control
      identities with the appropriate users, or to edit developer
      names.
    </p>
    {% if developers|empty? %}
    <div class="alert alert-warning text-content">
      <strong> The system doesn't have any developer information for your
        project.</strong> Make sure you run an initial analysis, which collects
      developer information and makes it available to edit on this page after the
      initial analysis.
    </div>
    {% else %}
    <h3>Terminology</h3>
    <p class="lead text-muted">
      <strong>Former Contributor</strong> is any developer who is no longer part of the team (left the company, moved to different product line, etc.). Used to calculate knowledge loss
      and risks. Check this box for all people who aren't part of the current team.
    </p>
    <p class="lead text-muted">
      <strong>Exclude from all Analyses</strong> This option is used to exclude non-human contributors like bots or build scripts from the analysis data. That way, bots don't appear
      in the knowledge maps inside the analysis.
      When checked, this option filters out all commits and code written by the excluded authors. Use sparingly.
    </p>
    <p class="lead text-muted">
      <strong>Remove from config</strong> Removes a specific developer from this configuration. Typically used in case you have ran an analysis with a repository that you later
      removed; pressing this button lets you clean-up the developer configuration from non-contributors.
    </p>
    <div id="update-developers"></div>
    {% endif %}
  </div>
</div>
{% endblock %}

{% block scripts %}
<script type="text/javascript">
 var settingsId = '{{item.id}}';
{% if teams|not-empty %}
codescene.views.developerConfiguration.developers.init(settingsId, true);
{% else %}
codescene.views.developerConfiguration.developers.init(settingsId, false);
  {% endif %}
  var devsTmp={{ developers|json|safe }};
  var teamsTmp={{ teams|json|safe  }};
</script>
{% endblock %}