More nits fixed.

- Legacy-Id: 19903
This commit is contained in:
Lars Eggert 2022-02-01 08:29:55 +00:00
parent 53089a94f6
commit a507b31669
33 changed files with 87 additions and 175 deletions

View file

@ -173,7 +173,12 @@ class ReviewTests(TestCase):
r = self.client.get(url)
self.assertContains(r, review_req.team.acronym)
self.assertContains(r, review_req.team.name)
self.assertContains(r, author.name)
try:
# FIXME-LARS
self.assertContains(r, author.name)
except:
print(r.content)
self.assertContains(r, author.name)
url = urlreverse('ietf.doc.views_review.review_request_forced_login', kwargs={ "name": doc.name, "request_id": review_req.pk })
r = self.client.get(url)

View file

@ -42,8 +42,8 @@
</ul>
<p>
The API top endpoint is at
<a href="https://datatracker.ietf.org/api/v1/">https://datatracker.ietf.org/api/v1/</a>
. The top
<a href="https://datatracker.ietf.org/api/v1/">https://datatracker.ietf.org/api/v1/</a>.
The top
endpoint lists inferior endpoints, and thus permits some autodiscovery,
but there's really no substitute for looking at the actual ORM model classes.
Comparing a class in <code>models.py</code> with the equivalent endpoint may give
@ -66,8 +66,7 @@
<h3 id="framework-documents">Framework API: Documents</h3>
<p>
Documents are listed at
<a href="https://datatracker.ietf.org/api/v1/doc/document/">/api/v1/doc/document/</a>
.
<a href="https://datatracker.ietf.org/api/v1/doc/document/">/api/v1/doc/document/</a>.
</p>
<p>
In general, individual database objects are represented in the API with a path
@ -156,13 +155,11 @@ $ curl 'https://datatracker.ietf.org/api/v1/doc/document/?limit=0&name__contains
<code>{% url 'ietf.doc.views_doc.document_json' name='draft-ietf-poised95-std-proc-3' %}</code>
<a href="{% url 'ietf.doc.views_doc.document_json' name='draft-ietf-poised95-std-proc-3' %}">
<span class="bi bi-box-arrow-up-right"></span>
</a>
.
</a>.
You can also specify an RFC: <code>{% url 'ietf.doc.views_doc.document_json' name='rfc2026' %}</code>
<a href="{% url 'ietf.doc.views_doc.document_json' name='rfc2026' %}">
<span class="bi bi-box-arrow-up-right"></span>
</a>
.
</a>.
No API key is needed to access this.
</p>
<p>
@ -253,8 +250,8 @@ $ curl -S -F "apikey=DgAAAMLSi3coaE5TjrRs518xO8eBRlCmFF3eQcC8_SjUTtRGLGiJh7-1SYP
<h2 id="openid-connect">OpenID Connect</h2>
<p>
The datatracker supports
<a href="https://openid.net/connect/">OpenID Connect</a>
, but
<a href="https://openid.net/connect/">OpenID Connect</a>,
but
not dynamic registration. The OpenID Connect Issuer is
<code> {{ settings.IDTRACKER_BASE_URL }}{% url 'ietf.api.urls.oidc_issuer' %} </code>
</p>
@ -277,8 +274,7 @@ $ curl -S -F "apikey=DgAAAMLSi3coaE5TjrRs518xO8eBRlCmFF3eQcC8_SjUTtRGLGiJh7-1SYP
<code>{% url 'ietf.doc.views_ballot.api_set_position' %}</code>
<a href="#iesg-position-api">
above
</a>
.
</a>.
Personal API keys are available from your
<a href="{% url 'ietf.ietfauth.views.apikey_index' %}">
Account API Keys
@ -316,8 +312,8 @@ $ curl -S -F "apikey=DgAAAMLSi3coaE5TjrRs518xO8eBRlCmFF3eQcC8_SjUTtRGLGiJh7-1SYP
<a href="https://datatracker.ietf.org/doc/html/rfc7515">
RFC
7515: JSON Web Signature (JWS)
</a>
, using a public/private keypair with
</a>,
using a public/private keypair with
this public key:
</p>
<p>

View file

@ -16,8 +16,7 @@
{% bootstrap_messages %}
<p>
The list currently tracks
<a href="{{ clist.get_absolute_url }}">{{ total_count }} document{{ total_count|pluralize }}</a>
.
<a href="{{ clist.get_absolute_url }}">{{ total_count }} document{{ total_count|pluralize }}</a>.
</p>
<p>
<a class="btn btn-primary" href="{{ clist.get_absolute_url }}">Back to list</a>
@ -61,8 +60,7 @@
Conveniently track individual documents in your personal list with the track icon
<span class="bi bi-bookmark"></span>
in
<a href="/doc/search/">search results</a>
.
<a href="/doc/search/">search results</a>.
</p>
<p>
You can also add documents here:

View file

@ -35,8 +35,7 @@
<h2>Add new subscription</h2>
<p class="text-muted">
The email addresses you can choose between are those registered in
<a href="{% url "ietf.ietfauth.views.profile" %}">your profile</a>
.
<a href="{% url "ietf.ietfauth.views.profile" %}">your profile</a>.
</p>
{% if form.fields.email.queryset %}
<form method="post">

View file

@ -10,7 +10,7 @@
Choose a short descriptive title for your request. Take time to choose a good initial title - it will be used to make the filename for your request's content. The title can be changed later, but the filename will not change.
</p>
<p>
For example, a request with a title of "A new important bit" will be saved as "bofreq-a-new-important-bit-00.md".
For example, a request with a title of "A new important bit" will be saved as <code>bofreq-a-new-important-bit-00.md</code>.
</p>
<form class="upload-content form-horizontal"
method="post"

View file

@ -15,8 +15,7 @@
</h1>
<p>
The shepherd needs to have a Datatracker account. A new account can be
<a href="{% url "ietf.ietfauth.views.create_account" %}">created here</a>
.
<a href="{% url "ietf.ietfauth.views.create_account" %}">created here</a>.
</p>
<form enctype="multipart/form-data" method="post">
{% csrf_token %}

View file

@ -28,9 +28,7 @@
{% if group.parent and group.parent.type_id == "area" %}
<th>{{ group.parent.type.name }}</th>
<td>
{{ group.parent.name }} (
<a href="{{ group.parent.about_url }}">{{ group.parent.acronym }}</a>
)
{{ group.parent.name }} (<a href="{{ group.parent.about_url }}">{{ group.parent.acronym }}</a>)
</td>
{% else %}
<th></th>

View file

@ -65,8 +65,7 @@
<td class="edit"></td>
<td>
{% for t, url in other_types %}
<a href="{{ url }}">{{ t }}</a>
{% if not forloop.last %},{% endif %}
<a href="{{ url }}">{{ t }}</a>{% if not forloop.last %},{% endif %}
{% endfor %}
</td>
</tr>
@ -130,8 +129,7 @@
{% else %}
Not available as plain text.
{% if other_types %}
<a href="{{ other_types.0.1 }}">Download as {{ other_types.0.0.upper }}</a>
.
<a href="{{ other_types.0.1 }}">Download as {{ other_types.0.0.upper }}</a>.
{% endif %}
{% endif %}
</div>

View file

@ -15,8 +15,7 @@
Send a publication request to the RFC Editor for {{ doc }} and move it to the <i>{{ next_state.name }}</i> stream state.
Please edit the message and remove any parts in brackets you do not
fill in. For independent submissions, see the
<a href="https://www.rfc-editor.org/indsubs.html">guidelines</a>
.
<a href="https://www.rfc-editor.org/indsubs.html">guidelines</a>.
</p>
{% if not doc.intended_std_level %}
<p class="alert alert-warning my-3">

View file

@ -29,8 +29,7 @@
</p>
<p>
The primary public face of the IETF is at
<a href="https://www.ietf.org/">www.ietf.org</a>
.
<a href="https://www.ietf.org/">www.ietf.org</a>.
</p>
</div>
<div class="p-5">

View file

@ -12,8 +12,7 @@
<p>
This page lists all active Internet-Drafts, grouped by responsible
group. For normal use, it is recommended to use the
<a href="{% url 'ietf.doc.views_search.search' %}">search page</a>
.
<a href="{% url 'ietf.doc.views_search.search' %}">search page</a>.
</p>
<p>
There is also an

View file

@ -13,8 +13,7 @@
<a href="{% url 'ietf.doc.views_search.search' %}">
search
page
</a>
.
</a>.
</p>
<p>
There is also an
@ -35,8 +34,7 @@
<a href="{{ settings.IETF_ID_ARCHIVE_URL }}1id-abstracts.txt">Active Internet-Drafts with abstracts (text)</a>
</li>
<li>
<a href="{{ settings.IETF_ID_ARCHIVE_URL }}all_id2.txt">All Internet-Drafts (tab-separated)</a>
,
<a href="{{ settings.IETF_ID_ARCHIVE_URL }}all_id2.txt">All Internet-Drafts (tab-separated)</a>,
<a href="{{ settings.IETF_ID_ARCHIVE_URL }}all_id.txt">older version (with fewer fields)</a>
</li>
<li>

View file

@ -39,8 +39,7 @@
<p>
{% if group is not None %}
Below you can upload a document for the group {{ group.name }}
<a href="{% url "ietf.group.views.materials" acronym=group.acronym %}">({{ group.acronym }})</a>
.
<a href="{% url "ietf.group.views.materials" acronym=group.acronym %}">({{ group.acronym }})</a>.
The document will appear under the materials tab in the group pages.
{% elif doc.meeting_related %}
Below you can upload a document for the {{ doc.get_related_meeting }} meeting.
@ -50,8 +49,7 @@
<p>
{% if group is not None %}
Below you can upload a new revision of {{ doc_name }} for the group {{ group.name }}
<a href="{% url "ietf.group.views.materials" acronym=group.acronym %}">({{ group.acronym }})</a>
.
<a href="{% url "ietf.group.views.materials" acronym=group.acronym %}">({{ group.acronym }})</a>.
{% elif doc.meeting_related %}
Below you can upload a new revision of {{ doc_name }} for the {{ doc.get_related_meeting }} meeting.
{% endif %}

View file

@ -120,14 +120,9 @@
<span class="content"></span>
<span class="visually-hidden try-yourself">
(searched for
<a class="query-url" href="#">
"
<span class="query"></span>
"
</a>
, corresponding
<a class="query-data-url" href="#">export</a>
).
<a class="query-url" href="#">"<span class="query"></span>"</a>,
corresponding
<a class="query-data-url" href="#">export</a>).
</span>
You have to fill in link and content yourself.
</div>

View file

@ -46,11 +46,9 @@
{% else %}
{{ doc.group.name }}
{% endif %}
(
<a href="{% url "ietf.group.views.review_requests" group_type=review_req.team.type_id acronym=review_req.team.acronym %}">
(<a href="{% url "ietf.group.views.review_requests" group_type=review_req.team.type_id acronym=review_req.team.acronym %}">
{{ review_req.team.acronym }}
</a>
)
</a>)
</td>
</tr>
<tr>
@ -144,11 +142,7 @@
{{ a.review_request.team.acronym|capfirst }} {{ a.review_request.type.name }} review of -{{ a.reviewed_rev|default:"??" }} by {% person_link a.reviewer.person %}
{% endif %}
{% if a.reviewed_rev and a.reviewed_rev != a.review_request.doc.rev %}
(
<a href="{{ rfcdiff_base_url }}?url1={{ a.review_request.doc.name }}-{{ a.reviewed_rev }}&amp;url2={{ a.review_request.doc.name }}-{{ a.review_request.doc.rev }}">
diff
</a>
)
(<a href="{{ rfcdiff_base_url }}?url1={{ a.review_request.doc.name }}-{{ a.reviewed_rev }}&amp;url2={{ a.review_request.doc.name }}-{{ a.review_request.doc.rev }}">diff</a>)
{% endif %}
<br>
{% endfor %}

View file

@ -6,8 +6,7 @@
<body>
<h3>
This is a verification page for the
<a href="https://www.google.com/webmasters/tools/siteoverview">Google Webmaster Tools</a>
.
<a href="https://www.google.com/webmasters/tools/siteoverview">Google Webmaster Tools</a>.
</h3>
</body>
</html>

View file

@ -17,16 +17,15 @@
</h1>
<p class="my-3">
Below you can customize the draft states and tags used in the
<a href="{{ group.about_url }}">{{ group.acronym }} {{ group.type.name }}</a>
. Note that some states are
<a href="{{ group.about_url }}">{{ group.acronym }} {{ group.type.name }}</a>.
Note that some states are
mandatory for group operation and cannot be deactivated.
</p>
{% if group.type_id == "wg" %}
<p>
You can see the default Working Group I-D State Diagram
in
<a href="/doc/html/rfc6174#section-4.1">Section 4.1 of RFC6174</a>
.
<a href="/doc/html/rfc6174#section-4.1">Section 4.1 of RFC6174</a>.
</p>
{% endif %}
<h2 class="mt-5">States</h2>

View file

@ -19,14 +19,13 @@
<h2>About Status Updates</h2>
<p>
Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>
. Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>.
Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
<a href="https://mailarchive.ietf.org/arch/msg/saag/fo2b3KA47SM4MuQuYj5VIh-Tjok">
the Kitten report sent to SAAG for IETF94
</a>
or the
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>
.
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>.
</p>
</div>
{% endif %}

View file

@ -15,14 +15,13 @@
<h2>About Status Updates</h2>
<p>
Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>
. Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>.
Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
<a href="https://mailarchive.ietf.org/arch/msg/saag/fo2b3KA47SM4MuQuYj5VIh-Tjok">
the Kitten report sent to SAAG for IETF94
</a>
or the
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>
.
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>.
</p>
</div>
<form enctype="multipart/form-data" method="post">

View file

@ -101,11 +101,7 @@
-{{ alatest.reviewed_rev }}
</a>
{% if alatest.reviewed_rev != r.doc.rev %}
(
<a href="{{ rfcdiff_base_url }}?url1={{ rlatest.doc.name }}-{{ alatest.reviewed_rev }}&url2={{ r.doc.name }}-{{ r.doc.rev }}">
diff
</a>
)
(<a href="{{ rfcdiff_base_url }}?url1={{ rlatest.doc.name }}-{{ alatest.reviewed_rev }}&url2={{ r.doc.name }}-{{ r.doc.rev }}">diff</a>)
{% endif %}
:
<a href="{{ alatest.review.get_absolute_url }}">

View file

@ -42,8 +42,7 @@
6(1)&nbsp;f) of
<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679#d1e1888-1-1">
EU's General Data Protection Regulation
</a>
.
</a>.
</p>
<p>
The datatracker treats all personal information derived from draft documents and

View file

@ -56,23 +56,22 @@
<p class="alert alert-danger my-3">
This IPR disclosure does not comply with the formal requirements of Section 5,
"IPR Disclosures," of
<a href="https://www.rfc-editor.org/rfc/rfc8179.txt">RFC 8179</a>
, "Intellectual Property Rights in IETF Technology."
<a href="https://www.rfc-editor.org/rfc/rfc8179.txt">RFC 8179</a>,
"Intellectual Property Rights in IETF Technology."
</p>
{% else %}
<p class="alert alert-danger my-3">
This IPR disclosure does not comply with the formal requirements of Section 6,
"IPR Disclosures," of
<a href="https://www.rfc-editor.org/rfc/rfc3979.txt">RFC 3979</a>
, "Intellectual Property Rights in IETF Technology."
<a href="https://www.rfc-editor.org/rfc/rfc3979.txt">RFC 3979</a>,
"Intellectual Property Rights in IETF Technology."
</p>
{% endif %}
{% endif %}
{% if ipr.has_legacy_event %}
<p>
The text of the original IPR disclosure is available in the
<a href="{% url "ietf.ipr.views.history" id=ipr.id %}">disclosure history</a>
.
<a href="{% url "ietf.ipr.views.history" id=ipr.id %}">disclosure history</a>.
</p>
{% endif %}
<div>
@ -107,9 +106,7 @@
{% if item.source.state.slug == "removed" %}
"{{ item.source.title }}" (which was removed at the request of the submitter)
{% else %}
"
<a href="{% url "ietf.ipr.views.show" id=item.source.id %}">{{ item.source.title }}</a>
"
"<a href="{% url "ietf.ipr.views.show" id=item.source.id %}">{{ item.source.title }}</a>"
{% endif %}
</div>
{% endfor %}
@ -132,9 +129,7 @@
{% elif item.target.state.slug == "parked" %}
"{{ item.target.title }}"
{% else %}
"
<a href="{% url "ietf.ipr.views.show" id=item.target.id %}">{{ item.target.title }}</a>
"
"<a href="{% url "ietf.ipr.views.show" id=item.target.id %}">{{ item.target.title }}</a>"
{% endif %}
</div>
{% endfor %}
@ -158,9 +153,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -188,9 +181,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -245,11 +236,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -309,11 +296,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -397,11 +380,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -439,11 +418,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -501,11 +476,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -568,11 +539,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -609,11 +576,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}
@ -661,11 +624,7 @@
<tr class="text-center">
<th class="ipr-prev col-5">
{% if prev.state.slug == "posted" %}
Previous (
<a href="{% url "ietf.ipr.views.show" id=prev.id %}">
#{{ prev.id }}
</a>
)
Previous (<a href="{% url "ietf.ipr.views.show" id=prev.id %}">#{{ prev.id }}</a>)
{% else %}
Previous (#{{ prev.id }}, {{ prev.state }})
{% endif %}

View file

@ -40,8 +40,7 @@
Fields marked with
<label class="required"></label>
are required. For detailed descriptions of the fields see the
<a href="{% url 'liaison-help-fields' %}">field help</a>
.
<a href="{% url 'liaison-help-fields' %}">field help</a>.
</p>
{% endif %}
<form role="form"

View file

@ -122,8 +122,8 @@
<sup><small>(2)</small></sup> The IETF Secretariat,
<a href="mailto:statements@ietf.org">
&lt;statements@ietf.org&gt;
</a>
, is automatically blind-copied on every liaison statement sent by the IETF.
</a>,
is automatically blind-copied on every liaison statement sent by the IETF.
</p>
<p>
<sup><small>(3)</small></sup> Any addresses included in the "Response Contact" and "Technical Contact" fields of a liaison statement will also receive copies of the liaison statement.

View file

@ -88,8 +88,8 @@
</table>
<p>
<sup><small>(1)</small></sup> The
<a href="mailto:statements@ietf.org">IETF Secretariat &lt;statements@ietf.org&gt;</a>
, is automatically blind-copied on every liaison statement sent to the IETF.
<a href="mailto:statements@ietf.org">IETF Secretariat &lt;statements@ietf.org&gt;</a>,
is automatically blind-copied on every liaison statement sent to the IETF.
</p>
<p>
<sup><small>(2)</small></sup> Any addresses included in the "response contact" and
@ -102,4 +102,4 @@
{% block js %}
<script src="{% static "ietf/js/list.js" %}">
</script>
{% endblock %}
{% endblock %}

View file

@ -63,8 +63,7 @@
Make a
<a href="{% url "ietf.meeting.views.new_meeting_schedule" num=meeting.number owner=schedule.owner_email name=schedule.name %}">
new agenda from this
</a>
.
</a>.
</div>
{% endif %}
<div class="edit-grid {% if not can_edit %}read-only{% endif %} my-3">
@ -420,4 +419,4 @@
</div>
</div>
</div>
{% endblock %}
{% endblock %}

View file

@ -45,13 +45,11 @@
<td>
{{ d.name.desc|linkify|urlize_ietf_docs }}
{% if first and d.name.slug == 'openreg' or first and d.name.slug == 'earlybird' %}
<a href="https://www.ietf.org/how/meetings/register/">Register here</a>
.
<a href="https://www.ietf.org/how/meetings/register/">Register here</a>.
{% endif %}
{% if d.name.slug == 'opensched' %}
To request a Working Group session, use the
<a href="{% url 'ietf.secr.sreq.views.main' %}">IETF Meeting Session Request Tool</a>
.
<a href="{% url 'ietf.secr.sreq.views.main' %}">IETF Meeting Session Request Tool</a>.
If you are working on a BOF request, it is highly recommended
to tell the IESG now by sending an email to
<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>
@ -59,23 +57,19 @@
{% endif %}
{% if d.name.slug == 'cutoffwgreq' %}
To request a Working Group session, use the
<a href="{% url 'ietf.secr.sreq.views.main' %}">IETF Meeting Session Request Tool</a>
.
<a href="{% url 'ietf.secr.sreq.views.main' %}">IETF Meeting Session Request Tool</a>.
{% endif %}
{% if d.name.slug == 'cutoffbofreq' %}
To request a BOF, please see instructions on
<a href="https://www.ietf.org/how/bofs/bof-procedures/">Requesting a BOF</a>
.
<a href="https://www.ietf.org/how/bofs/bof-procedures/">Requesting a BOF</a>.
{% endif %}
{% if d.name.slug == 'idcutoff' %}
Upload using the
<a href="{% url 'ietf.submit.views.upload_submission' %}">ID Submission Tool</a>
.
<a href="{% url 'ietf.submit.views.upload_submission' %}">ID Submission Tool</a>.
{% endif %}
{% if d.name.slug == 'draftwgagenda' or d.name.slug == 'revwgagenda' or d.name.slug == 'procsub' or d.name.slug == 'revslug' %}
Upload using the
<a href="{% url 'ietf.meeting.views.materials' num=meeting.number %}">Meeting Materials Management Tool</a>
.
<a href="{% url 'ietf.meeting.views.materials' num=meeting.number %}">Meeting Materials Management Tool</a>.
{% endif %}
</td>
</tr>

View file

@ -18,7 +18,6 @@
</p>
<p>
You should be able to access the final version of IETF {{ meeting_num }} Proceedings via the
<a href="https://www.ietf.org/meeting/proceedings.html">IETF Online Proceedings page</a>
.
<a href="https://www.ietf.org/meeting/proceedings.html">IETF Online Proceedings page</a>.
</p>
{% endblock %}

View file

@ -46,9 +46,7 @@
<td>{{ role.name.name }}</td>
<td>
<a href="{% url 'ietf.group.views.group_about' acronym=role.group.acronym %}">{{ role.group.name }}</a>
(
<a href="{% url 'ietf.group.views.group_about' acronym=role.group.acronym %}">{{ role.group.acronym }}</a>
)
(<a href="{% url 'ietf.group.views.group_about' acronym=role.group.acronym %}">{{ role.group.acronym }}</a>)
</td>
<td>
<a href="mailto:{{ role.email.address }}">{{ role.email.address }}</a>

View file

@ -82,8 +82,7 @@
or see the
<a href="{% url "admin:stats_affiliationalias_changelist" %}">existing known aliases</a>
and
<a href="{% url "admin:stats_affiliationignoredending_changelist" %}">generally ignored endings</a>
.
<a href="{% url "admin:stats_affiliationignoredending_changelist" %}">generally ignored endings</a>.
</p>
{% endif %}
{% if alias_data %}

View file

@ -70,8 +70,8 @@
<a href="https://www.wikipedia.org/wiki/H-index">
measure of the
productivity and impact of the publications of an author
</a>
. An
</a>.
An
author with an h-index of 5 has had 5 publications each cited at
least 5 times - to increase the index to 6, the 5 publications plus
1 more would have to have been cited at least 6 times, each. Thus a

View file

@ -12,8 +12,7 @@
</h1>
<p>
In case you think a country or an alias is missing from the list, you can
<a href="mailto:{{ settings.SECRETARIAT_ACTION_EMAIL }}">file a ticket</a>
.
<a href="mailto:{{ settings.SECRETARIAT_ACTION_EMAIL }}">file a ticket</a>.
</p>
{% if request.user.is_staff %}
<p>

View file

@ -137,7 +137,7 @@
</th>
<td>
<p>
Button to start the automated posting process with submitter authentication. Once clicked, an email message will be sent to the parties who can verify the sybmission. For a new draft (-00), that will be the authors listed in the document. For -01 and subsequent drafts, the confirmation message is sent to the authors of the <b>previous</b> version. One of the recipients of the confirmation message will need to open the email message via his or her email application, and click the link provided in the message body.
Button to start the automated posting process with submitter authentication. Once clicked, an email message will be sent to the parties who can verify the submission. For a new draft (<code>-00</code>), that will be the authors listed in the document. For -01 and subsequent drafts, the confirmation message is sent to the authors of the <b>previous</b> version. One of the recipients of the confirmation message will need to open the email message via his or her email application, and click the link provided in the message body.
</p>
<p>
Once a link in the email body is clicked, the document gets pushed to the IETF Web and FTP sites, a notification is sent to the authors of the document, and an I-D Action announcement will be sent out within the next 15 minutes.