summaryrefslogtreecommitdiff
path: root/templates
diff options
context:
space:
mode:
authorGuilherme Salgado <guilherme.salgado@linaro.org>2011-07-05 17:09:22 -0300
committerGuilherme Salgado <guilherme.salgado@linaro.org>2011-07-05 17:09:22 -0300
commitffd2f454c5953a518b64c2998c886d7ce3604667 (patch)
treecc80b4c30d3b3b72e45a0a49c585503d16d78d50 /templates
parent5cfd78caa44563e5987cf1018a59a34ec1f3612a (diff)
Show oldest patches on the front page plus some other changes that should've
been included in the previous commit - Fix rendering of charts on IE8 - Make patch-list filter more visible
Diffstat (limited to 'templates')
-rw-r--r--templates/patchmetrics/faq.html31
-rw-r--r--templates/patchmetrics/frontpage.html46
-rw-r--r--templates/patchwork/filters.html11
-rw-r--r--templates/patchwork/patch-list.html7
4 files changed, 63 insertions, 32 deletions
diff --git a/templates/patchmetrics/faq.html b/templates/patchmetrics/faq.html
index 0b6404a..8b7e0da 100644
--- a/templates/patchmetrics/faq.html
+++ b/templates/patchmetrics/faq.html
@@ -5,6 +5,25 @@
{% block body %}
+<h3>How often are the statistics updated?</h3>
+</p>The statistics are generated dynamically and include even the most
+recently submitted patches. The only exception is the "Patches per month"
+chart, which doesn't include statistics for the current month.</p>
+
+<h3>How do you know which patches have been accepted upstream?</h3>
+<p>Every day we scan commits on the upstream master branch for every project
+registered here and update the state of patches for which we find a matching
+commit. When a patch is changed before being committed upstream, though, we
+may not find the matching commit, so some patches have to be updated
+manually.</p>
+
+<h3>Why is there a big spike in the number of patches accepted in June
+ 2011?</h3>
+<p>Because this website went live on that month and engineers were then
+encouraged to go through their patches (including the ones submitted in
+previous months) and mark the ones that had been accepted upstream but were
+not picked up by our automated mechanism.</p>
+
<h3>What patches are included in Linaro statistics?</h3>
<p>Only patches that come from an @linaro.org address are included in our
statistics. If for any reason you cannot send patches using your @linaro.org
@@ -25,18 +44,6 @@ not included in our statistics:</p>
</li>
</ol>
-<h3>How often are the statistics updated?</h3>
-</p>The statistics are generated dynamically and include even the most
-recently submitted patches. The only exception is the "Patches per month"
-chart, which doesn't include statistics for the current month.</p>
-
-<h3>How do you know which patches have been accepted upstream?</h3>
-<p>Every day we scan commits on the upstream master branch for every project
-registered here and update the state of patches for which we find a matching
-commit. When a patch is changed before being committed upstream, though, we
-may not find the matching commit, so some patches have to be updated
-manually.</p>
-
<h3>How do you track the date a given patch was accepted?</h3>
<p>We use the date in which the patch was committed on the upstream's master
branch as the acceptance date. For patches whose state is updated manually,
diff --git a/templates/patchmetrics/frontpage.html b/templates/patchmetrics/frontpage.html
index 85a6f92..f5fec91 100644
--- a/templates/patchmetrics/frontpage.html
+++ b/templates/patchmetrics/frontpage.html
@@ -1,5 +1,7 @@
{% extends "base.html" %}
+{% load person %}
+
{% block title %}Linaro patch metrics{% endblock %}
{% block heading %}Patch metrics{% endblock %}
{% block headers %}
@@ -7,7 +9,7 @@
src="/js/jquery-1.3.min.js">
</script>
<!--[if lte IE 8]><script language="javascript" type="text/javascript"
- src="../excanvas.min.js"></script><![endif]-->
+ src="/js/excanvas.min.js"></script><![endif]-->
<script language="JavaScript" type="text/javascript"
src="/js/jquery.flot.min.js">
</script>
@@ -18,7 +20,7 @@
{% block body %}
-<h2>Statistics for patches submitted upstream by Linaro engineers</h2>
+<h1>Statistics for patches submitted upstream by Linaro engineers</h1>
<p><strong>{{submitted_on_month}}</strong> patches were submitted in
{{month}}, and <strong>{{submitted_and_accepted_on_month}}</strong>
@@ -40,19 +42,27 @@ older than 30 days.</p>
{{patches_per_month_chart|safe}}
</div>
<div class="yui3-u-1-3">
- <p><strong>Time-to-acceptance distribution</strong> (in days)</p>
+ <p><strong>Time-to-acceptance distribution</strong>
+ <span class="lesser">(in days)</span></p>
{{time_to_acceptance_chart|safe}}
</div>
<div class="yui3-u-1-3">
<p><strong>Patch age distribution</strong>
- (in days; only patches waiting for feedback)</p>
+ <span class="lesser">(in days; only patches waiting for feedback)</span>
+ </p>
{{patch_age_distribution_chart|safe}}
</div>
</div>
+<p>When analyzing the charts above, please take into account
+that the process which allows us to track patches was put in place at the end
+of January 2011 and that this website went live in June 2011.
+Check the <a href="{% url patchmetrics.views.faq %}">FAQ</a> for answers to
+common questions.</p>
+
<div class="yui3-g">
<div class="yui3-u-5-12" style="line-height: 2">
- <h3>Stats per project</h3>
+ <h2>Stats per project</h2>
{% for p in projects %}
<a href="{% url patchmetrics.views.project project_id=p.linkname %}"
>{{p.name}}</a>
@@ -63,7 +73,7 @@ older than 30 days.</p>
<div class="yui3-u-1-12"></div>
<div class="yui3-u-5-12" style="line-height: 2">
- <h3>Stats per team</h3>
+ <h2>Stats per team</h2>
{% for team in teams %}
<a href="{% url patchmetrics.views.team team_id=team.name %}"
>{{team.display_name}}</a>
@@ -72,8 +82,26 @@ older than 30 days.</p>
</div>
</div>
-<br />
-<p>Check the <a href="{% url patchmetrics.views.faq %}">FAQ</a> for answers to
-common questions.</p>
+<h2>Oldest patches not accepted yet</h2>
+<table class="patchlist" id="patchlist">
+ <thead>
+ <tr>
+ <th>Patch</th>
+ <th>Date</th>
+ <th>Author</th>
+ </tr>
+ </thead>
+
+ <tbody>
+ {% for patch in old_patches %}
+ <tr class="{% cycle 'odd' 'even' %}">
+ <td><a href="{% url patchmetrics.views.patch patch_id=patch.id %}"
+ >{{ patch.name|default:"[no subject]" }}</a></td>
+ <td>{{ patch.date|date:"Y-m-d" }}</td>
+ <td>{{ patch.author|personify }}</td>
+ </tr>
+ {% endfor %}
+ </tbody>
+</table>
{% endblock %}
diff --git a/templates/patchwork/filters.html b/templates/patchwork/filters.html
index 3698101..7fac6ac 100644
--- a/templates/patchwork/filters.html
+++ b/templates/patchwork/filters.html
@@ -141,10 +141,10 @@ function submitter_field_change(field)
<div class="filters">
<div id="filtersummary">
- <strong><a href="javascript:filter_click()">Filters</a>:</strong>
{% if filters.applied_filters %}
+ Found <strong>{{patch_count}}</strong> patches matching:
{% for filter in filters.applied_filters %}
- {{ filter.name }} = {{ filter.condition }}
+ <strong>{{ filter.name }} = {{ filter.condition }}</strong>
{% if not filter.forced %}
<a href="{{ filter.url_without_me }}"><img
width="16" height="16" alt="remove filter" title="remove filter"
@@ -152,11 +152,10 @@ function submitter_field_change(field)
{% endif %}
{% if not forloop.last %}&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;{% endif %}
{% endfor %}
+ (<a href="javascript:filter_click()">Change filters</a>)
{% else %}
- none
- <a href="javascript:filter_click()"><img
- width="16" height="16" alt="add filter" title="add filter"
- src="/images/16-circle-blue-add.png"></a>
+ Found <strong>{{patch_count}}</strong> patches.
+ (<a href="javascript:filter_click()">Add filters</a>)
{% endif %}
</div>
<div id="filterform" style="padding-top: 1em; display: none">
diff --git a/templates/patchwork/patch-list.html b/templates/patchwork/patch-list.html
index 70fd55a..e88a57f 100644
--- a/templates/patchwork/patch-list.html
+++ b/templates/patchwork/patch-list.html
@@ -1,14 +1,11 @@
{% load person %}
{% load listurl %}
-{% include "patchwork/pagination.html" %}
-
+{% include "patchwork/filters.html" %}
+<br />
<table class="patchlist">
<tr>
- <td class="patchlistfilters">
- {% include "patchwork/filters.html" %}
- </td>
{% if order.editable %}
<td class="patchlistreorder">
<form method="post" id="reorderform">