diff --git a/ietf/release/urls.py b/ietf/release/urls.py index 5f6068d8e..0f86ddad1 100644 --- a/ietf/release/urls.py +++ b/ietf/release/urls.py @@ -1,7 +1,11 @@ from django.conf.urls import patterns +from django.views.generic import TemplateView urlpatterns = patterns('', (r'^$', 'ietf.release.views.release'), (r'^(?P[0-9.]+.*)/$', 'ietf.release.views.release'), + (r'^about/?$', TemplateView.as_view(template_name='release/about.html')), + (r'^todo/?$', TemplateView.as_view(template_name='release/todo.html')), + ) diff --git a/ietf/templates/ietf.html b/ietf/templates/ietf.html index ed82ca56c..388304469 100644 --- a/ietf/templates/ietf.html +++ b/ietf/templates/ietf.html @@ -128,6 +128,7 @@

{% if version_num %} + About | IETF Datatracker | Version {{ version_num }} | {{revision_date}} | diff --git a/ietf/templates/release/about.html b/ietf/templates/release/about.html new file mode 100644 index 000000000..06ce9fe21 --- /dev/null +++ b/ietf/templates/release/about.html @@ -0,0 +1,105 @@ +{% extends "ietf.html" %} + +{% block title %}About the Datatracker{% endblock %} + +{% block content %} +

+

About the IETF Datatracker

+ +

+ + The IETF Datatracker is the primary day-to-day front-end to the IETF database for people + who work on IETF standards. It contains data about the documents, working groups, + meetings, agendas, minutes, presentations, etc. of the IETF. + +

+

+ + The primary public face of IETF is at www.ietf.org. + +

+ + +

Version 6.0.0: Facelift using Bootstrap

+

+ + During more than a year, from July 2013 to late 2014, Lars Eggert worked intensively + on a major facelift to the datatracker, porting the GUI to Bootstrap. The work + took + + 287 separate commits + , and comprised changes to 1016 different files. + +

+

+ + This work has turned the IETF Datatracker website into a responsive website which + support use on a much larger variety of devices, from small mobile devices to desktops. + +

+

+ + The work continues to build on the Django + framework which the datatracker has been using since version + 2.00, and relies heavily on the capabilities of + Bootstrap. It also uses icons from FontAwesome, and functions from + django-bootstrap3. + +

+

+ + Additional + + page conversion work + has been done by Ole Laursen, with final + tweaks by Henrk Levkowetz, giving it a distinct + colour palette + (with the addition of complementing red and green colours for success and error indications), + and a selection of fonts + (PT Serif, + PT Sans Caption, and PT Mono) from + ParaType, provided by + Google Fonts. + +

+ +

Version 5.0.0: Shim Removal

+ +
+ To be written. +
+ +

Version 4.0.0: New Database Schema

+ +
+ To be written. +
+ +

Version 3.0.0: Django Port of the IESG Datatracker Pages

+ +
+ To be written. +
+ +

Version 2.0.0: Django Port of the Public Datatracker Pages

+ +
+ To be written. +
+ +

Version 1.0.0: Initial Perl/MySQL database and web-pages

+ +

+ The first version of the idtracker was commissioned by the IESG under Harald + Alvestrand in 2001, and the IESG started using it at the beginning of 2002. It was + written by Michael Lee in Perl, with direct SQL statements. It provided a + major improvement in visibility of the progress of drafts by the IESG. + The first + public presentation of it and its capabilities was made 2002-11-20 + in Atlanta by Thomas Narten. +

+ + + +
+{% endblock %} diff --git a/ietf/templates/release/todo.html b/ietf/templates/release/todo.html new file mode 100644 index 000000000..d17023a6a --- /dev/null +++ b/ietf/templates/release/todo.html @@ -0,0 +1,70 @@ +{% extends "ietf.html" %} + +{% block title %}About the Datatracker{% endblock %} + +{% block content %} +
+
+

Facelift ToDo

+ +
+

Pre-Release

+ +
    + +
  • DONE Initial merge with trunk (on separate branch)
    • +
  • DONE Re-style to make people recognise that they are at the datatracker
    • +
  • DONE Use a designed colour palette rather than arbitrary element colours
    • +
  • DONE The extra FontAwesome add-in seems to add glyphs already bundled in + glyphicons, which adds page load time and update complexity; see if we + can reduce to only the bundled glyphs. Conclusion: not feasible
    • +
  • DONE Have a look at using slightly more readable fonts than the current + one, and change font families if it looks reasonable
    • +
  • DONE Align the use of info and warning background colours with the info and + warning button colours
    • +
  • DONE Add an 'About' page which gives credit to those working on the facelift.
    • +
    + +
  • Rename the base template back to 'base.html' from 'ietf.html' now that + all templates using the old base have been fixed
    • +
  • Fix the missing IPR values on search and group pages.
    • +
  • Fix style consistency, for instance in WG metadata table vs. document + metadata table, WG doc list vs. release list, and more
    • +
  • The header colours on the meeting requests page have inverted colour + logic compared to other list pages (info background for warnings, warning + background for sub-headers). Empty warning panes are shown. Fix.
    • +
  • The agenda page uses warning colours for day headers. Fix.
    • +
  • On tablets, the ballot grids has a 'click to show more' which has a + z-value larger than the pop-up. This only matters because it doesn't go + away on click on tablets. Fix.
    • +
  • Replace buttons which are links with something which is recognisable + as links, preferably in submenu form. (Could be done post-release).
    • +
  • Final merge to trunk
    • +
+ +
+
+

Post-Release

+ +
    +
  • Maybe change alert, warning, etc. fonts to sans?
    • +
  • Fix input fields to have appropriate type setting, in order to provide + the appropriate keyboard on mobile devices (email address keyboard, + url keyboard, and possibly others). Set autocorrect and autocaptitalise + attributes correctly, also to make things easier on mobile devices.
    • +
  • The materials page has very different column width for the different + areas. Consider normalising. Check IPR list page for possible approach.
    • +
  • The ballot grids don't use the position colours used in the pop-up (the + colours in the pop-up is based on the palette colours). Mabye align grid + position colours with pop-up position colours?
    • +
  • Remove general uglyness (like the overly large section descriptions on + http://zin.tools.ietf.org:31415/sync/discrepancies/)
    • +
  • Change the room map links on the agenda to use pop-overs instead of + pointing off to the room maps on tools.ietf.org
    • +
+ +
+
+ +
+{% endblock %}