36 lines
1.6 KiB
HTML
36 lines
1.6 KiB
HTML
{% extends "base.html" %}
|
|
{# Copyright The IETF Trust 2015, All Rights Reserved #}
|
|
{% load origin %}
|
|
{% load django_bootstrap5 %}
|
|
{% block title %}Edit status for {{ group.type.name }} ({{ group.acronym }}){% endblock %}
|
|
{% block content %}
|
|
{% origin %}
|
|
<h1>
|
|
Edit status update for {{ group.type.name }}
|
|
<br>
|
|
<small class="text-muted">{{ group.acronym }}</small>
|
|
</h1>
|
|
<div class="my-3 alert alert-info">
|
|
<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://github.com/ietf-tools/datatracker/issues/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://wiki.ietf.org/group/rtg/IETF94summary">Routing area high level summaries for IETF94</a>.
|
|
</p>
|
|
</div>
|
|
<form enctype="multipart/form-data" method="post">
|
|
{% csrf_token %}
|
|
{% bootstrap_form form %}
|
|
<button type="submit"
|
|
class="btn btn-primary"
|
|
name="submit_response"
|
|
value="Submit">Submit</button>
|
|
<a class="btn btn-secondary float-end"
|
|
href="{% url "ietf.group.views.group_about" acronym=group.acronym %}">Back</a>
|
|
</form>
|
|
{% endblock %} |