altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity

Fixed references (relative to absolute) in template ietf/templates/group/active_areas.html, fixed build failure on unused import in file 0006_auto_20150718_0509.py, commit ready for merge

Browse source 
- Legacy-Id: 9802
This commit is contained in:
Bartosz Balazinski 2015-07-18 15:32:57 +00:00
parent 7fb17b0b98
commit dba620f8f1
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
ietf/group/migrations/0006_auto_20150718_0509.py
View file

@ -1,7 +1,7 @@
# -*- coding: utf-8 -*-
from __future__ import unicode_literals
from django.db import models, migrations
from django.db import migrations
def add_area_descriptions(apps, schema_editor):
Group = apps.get_model("group","Group")

4
ietf/templates/group/active_areas.html
View file

@ -9,7 +9,7 @@
<h1>Areas</h1>
<p>The IETF divides its work into a number of areas, each comprised of working groups that relate to that area's focus. The area structure is defined by the IESG, and the IESG can add areas, redefine areas, merge areas, change the number of ADs assigned to an area, or close down areas.</p>
<p>Changes to the area structure affect the IETF in many ways; decisions to change the area structure are taken in consultation with the community.</p>
<p>When changing the area structure, the IESG can decide which members are responsible for new and changed areas, including making one sitting AD responsible for multiple areas, but the IESG can only add new members through the <a href="http://ietf.org/nomcom/index.html">nomcom process</a>.</p>
<p>When changing the area structure, the IESG can decide which members are responsible for new and changed areas, including making one sitting AD responsible for multiple areas, but the IESG can only add new members through the <a href="http://www.ietf.org/nomcom/index.html">nomcom process</a>.</p>
<p>The primary task of area management is handled by one or two Area Directors per area. An AD may be advised by one or more directorates, which are created, selected, chaired and if necessary disbanded by the AD. Directorates may be specific to an area, specific to a technology, or chartered in some other fashion.</p>
<p>The ADs for an area are jointly responsible for making sure the WGs in the area are well coordinated, that there is coverage for the technologies needed in the area, and that the challenges most important to the Internet in that area are indeed being worked on.</p>
<ul><li>A full list of active working groups, sorted by area, may be found at <a href="http://datatracker.ietf.org/wg/">http://datatracker.ietf.org/wg/</a>.</li></ul>
@ -19,5 +19,5 @@
<h2>{{area.name}} ({{area.acronym}})</h2>
<pre class="pasted">{{area.description}}</pre>
{% endfor %}
<p>For more information about the role of the IESG in areas and working groups, please see <a href="/rfc/rfc3710.txt">RFC 3710 ("An IESG charter")</a>, section 6 and <a href="/rfc/rfc2418.txt">RFC 2418 ("IETF Working Group Guidelines and Procedures")</a>.</p>
<p>For more information about the role of the IESG in areas and working groups, please see <a href="http://www.ietf.org/rfc/rfc3710.txt">RFC 3710 ("An IESG charter")</a>, section 6 and <a href="http://www.ietf.org/rfc/rfc2418.txt">RFC 2418 ("IETF Working Group Guidelines and Procedures")</a>.</p>
{% endblock %}