From 97f2b6eedf2196abce631ba40c88c069f532c227 Mon Sep 17 00:00:00 2001 From: Robert Sparks Date: Sat, 12 Nov 2011 10:35:30 +0000 Subject: [PATCH] Changed the edit info form to allow (force) setting the stream when editing or adding a document to the iesg tracker. Fixes bug 743 - Legacy-Id: 3612 --- ietf/idrfc/fixtures/base.xml | 2648 +++++++++++++++++----------------- ietf/idrfc/tests.py | 6 + ietf/idrfc/views_edit.py | 15 + 3 files changed, 1353 insertions(+), 1316 deletions(-) diff --git a/ietf/idrfc/fixtures/base.xml b/ietf/idrfc/fixtures/base.xml index 7408082a1..78e3d350d 100644 --- a/ietf/idrfc/fixtures/base.xml +++ b/ietf/idrfc/fixtures/base.xml @@ -1,1316 +1,1332 @@ - - - - 1324 - 104942 - - - 1092 - 2324 - - - 1157 - 4763 - - - 1179 - 188 - - - 1190 - 2324 - - - 1193 - 101568 - - - 1199 - 2372 - - - 1264 - 2744 - - - 1260 - 19790 - - - 1249 - 2329 - - - 1541 - 103264 - - - 1008 - 5376 - - - 1324 - 17253 - - - 1092 - 2515 - - - 1190 - 4817 - - - 1052 - 21072 - - - 1346 - 4356 - - - 1541 - 6842 - - - 1199 - 2723 - - - 1179 - 2853 - - - 1193 - 6699 - - - 1179 - 773 - - - 1260 - 19483 - - - - 106956 - - - 934 - 105907 - - - 1683 - 103539 - - - 1052 - 2348 - - - 1683 - 103961 - - - 1249 - 104198 - - - 934 - 102154 - - - business - Mr. - Jari - JARI - - - Arkko - ARKKO - - 1998-03-11 - WEB - 1996-11-22 - juliek - W - - - business - Mr. - Fred - FRED - - - Baker - BAKER - - 1999-11-17 - scoya - - Unknown - W - - - business - - Ronald - RONALD - - - Bonica - BONICA - - 1998-04-28 - WEB - 1998-04-28 - WEB - W - - - business - Mr. - Scott - SCOTT - O. - O. - Bradner - BRADNER - - 1998-03-12 - WEB - - Unknown - W - - - business - Mr. - Scott - SCOTT - O. - O. - Bradner - BRADNER - - 1998-03-12 - WEB - - Unknown - W - - - business - Dr. - Stewart - STEWART - - - Bryant - BRYANT - - 1991-10-16 - Unknown - - Unknown - W - - - business - Mr. - Ross - ROSS - - - Callon - CALLON - - 1998-04-30 - WEB - - Unknown - W - - - business - Mr. - Gonzalo - GONZALO - - - Camarillo - CAMARILLO - - 1999-03-11 - WEB - 1999-03-11 - WEB - W - - - business - Mr. - Stephen - STEPHEN - J. - J. - Coya - COYA - - 2000-08-16 - scoya - - You - W - - - business - Mr. - David - DAVID - H. - H. - Crocker - CROCKER - - 1999-01-14 - WEB - - Unknown - W - - - business - Mr. - Ralph - RALPH - E. - E. - Droms - DROMS - - 2001-07-16 - scoya - - Unknown - W - - - business - Dr. - Lars - LARS - - - Eggert - EGGERT - - 2000-11-30 - nsyracus - 2000-11-30 - nsyracus - - - - business - - Adrian - ADRIAN - - - Farrel - FARREL - - 2009-07-17 - cmm - 2000-02-16 - nsyracus - W - - - business - Mr. - Robert - ROBERT - - - Hagens - HAGENS - - 1995-11-02 - dlegare - - Unknown - W - - - business - Mr. - David - DAVID - - - Harrington - HARRINGTON - - 1997-10-29 - WEB - 1994-11-04 - mbeaulie - W - - - business - - Russ - RUSS - - - Housley - HOUSLEY - - 2001-03-26 - scoya - - Unknown - W - - - business - Ms. - Deirdre - DEIRDRE - C. - C. - Kostick - KOSTICK - - 1998-03-12 - WEB - - Unknown - W - - - business - Ms. - Allison - ALLISON - J. - J. - Mankin - MANKIN - - 2001-03-27 - mbeaulie - - Unknown - W - - - business - Ms. - April - APRIL - - - Marine - MARINE - - 2000-01-04 - mbeaulie - - Unknown - W - - - business - M. - Alexey - ALEXEY - - - Melnikov - MELNIKOV - - 2009-07-08 - cmm - 1998-08-10 - cclark - W - - - business - Mr. - Michael - MICHAEL - D. - D. - O'Dell - O'DELL - - 1998-03-23 - WEB - - Unknown - W - - - business - Mr. - David - DAVID - - - Oran - ORAN - - 2001-01-12 - mbeaulie - - Unknown - W - - - business - Mr. - Tim - TIM - - - Polk - POLK - - 1998-03-16 - WEB - 1996-03-13 - mbeaulie - W - - - business - Mr. - Dan - DAN - - - Romascanu - ROMASCANU - - 2000-10-03 - scoya - - Unknown - W - - - - - Peter - PETER - - - Saint-Andre - SAINT-ANDRE - - 2002-06-24 - INTERNAL - 2002-06-24 - - - - - business - - Robert - ROBERT - - - Sparks - SPARKS - - 2009-07-07 - scoya - 1999-10-21 - nsyracus - - - - - - - - - - TBD - TBD - - 2005-01-25 - INTERNAL - 2005-01-25 - - - - - business - Mr. - Sean - SEAN - - - Turner - TURNER - - 1999-01-21 - WEB - 1996-01-24 - dbates - W - - - business - Mr. - Bert - BERT - - - Wijnen - WIJNEN - - 2000-06-01 - scoya - - Unknown - W - - - business - Mr. - Alex - ALEX - D. - D. - Zinin - ZININ - - 1999-02-26 - cclark - 1999-02-26 - cclark - W - - - scoya - deleted - 3 - Steve - Coya - 188 - scoya - - - - sob - deleted - 2 - Scott - Bradner - 2324 - - 1 - - - mankin - deleted - 2 - Allison - Mankin - 2515 - - 1 - - - bwijnen - deleted - 2 - Bert - Wijnen - 6842 - - 1 - - - marine - deleted - 3 - April - Marine - 4356 - - - - - azinin - deleted - 2 - Alex - Zinin - 103264 - azinin - 1 - - - rhousley - deleted - 1 - Russ - Housley - 5376 - - 0 - - - jari.arkko@ericsson.com - deleted - 1 - Jari - Arkko - 21072 - 0 - 1 - - - dromasca@avaya.com - deleted - 1 - Dan - Romascanu - 6699 - 0 - 1 - - - rcallon@juniper.net - deleted - 2 - Ross - Callon - 2723 - 0 - 1 - - - lars.eggert@nokia.com - deleted - 1 - Lars - Eggert - 104942 - 0 - 1 - - - alexey.melnikov@isode.com - deleted - 1 - Alexey - Melnikov - 102154 - 0 - 1 - - - rbonica@juniper.net - deleted - 1 - Ron - Bonica - 101568 - 0 - 1 - - - tim.polk@nist.gov - deleted - 1 - Tim - Polk - 19790 - 0 - 0 - - - rjsparks@nostrum.com - deleted - 1 - Robert - Sparks - 103961 - 0 - 0 - - - rdroms.ietf@gmail.com - deleted - 1 - Ralph - Droms - 2348 - 0 - 1 - - - klm - deleted - 0 - Karen - Moreland - - - 0 - - - adrian@olddog.co.uk - deleted - 1 - Adrian - Farrel - 104198 - 0 - 1 - - - stpeter@stpeter.im - deleted - 1 - Peter - Saint-Andre - 105907 - - - - - gonzalo.camarillo@ericsson.com - deleted - 1 - Gonzalo - Camarillo - 103539 - - - - - stbryant@cisco.com - deleted - 1 - Stewart - Bryant - 2329 - - - - - turners@ieca.com - deleted - 1 - Sean - Turner - 19483 - - - - - 104942 - INET - 1 - lars.eggert@nokia.com - Email Address - - - 2324 - INET - 1 - sob@harvard.edu - - - - 4763 - INET - 1 - kostick@qsun.att.com - - - - 188 - INET - 1 - scoya@ietf.org - - - - 2324 - INET - 1 - sob@harvard.edu - - - - 101568 - INET - 1 - rbonica@juniper.net - - - - 2372 - INET - 1 - hagens@mci.net - - - - 2744 - INET - 1 - dcrocker@brandenburg.com - this address is his 1st preference - - - 19790 - INET - 1 - tim.polk@nist.gov - - - - 2329 - INET - 1 - stbryant@cisco.com - - - - 103264 - INET - 1 - alex.zinin@alcatel-lucent.com - Email - - - 5376 - INET - 1 - housley@vigilsec.com - Email - - - 17253 - INET - 1 - ietfdbh@comcast.net - - - - 2515 - INET - 1 - mankin@psg.com - Email - - - 4817 - INET - 1 - mo@uu.net - - - - 21072 - INET - 1 - jari.arkko@piuha.net - Email - - - 4356 - INET - 1 - april.marine@nominum.com - - - - 6842 - INET - 1 - bertietf@bwijnen.net - Email - - - 2723 - INET - 1 - rcallon@juniper.net - Email - - - 2853 - INET - 1 - fred.baker@cisco.com - - - - 6699 - INET - 1 - dromasca@avaya.com - Email - - - 773 - INET - 1 - oran@cisco.com - - - - 19483 - INET - 1 - turners@ieca.com - - - - 106956 - INET - 1 - noreply@ietf.org - - - - 105907 - INET - 1 - stpeter@stpeter.im - - - - 103539 - INET - 1 - gonzalo.camarillo@ericsson.com - - - - 2348 - INET - 1 - rdroms.ietf@gmail.com - - - - 103961 - INET - 1 - rjsparks@nostrum.com - - - - 104198 - INET - 1 - adrian.farrel@huawei.com - - - - 102154 - INET - 1 - alexey.melnikov@isode.com - - - - Active - - - Expired - - - RFC - - - Withdrawn by Submitter - - - Replaced - - - Withdrawn by IETF - - - BCP - - - Draft Standard - - - Experimental - - - Historic - - - Informational - - - Proposed Standard - - - Standard - - - None - - - Request - - - Point Raised - writeup needed - IESG discussions on the document have raised some issues that need -to be brought to the attention of the authors/WG, but those issues -have not been written down yet. (It is common for discussions during -a telechat to result in such situations. An AD may raise a possible -issue during a telechat and only decide as a result of that -discussion whether the issue is worth formally writing up and -bringing to the attention of the authors/WG). A document stays in -the "Point Raised - Writeup Needed" state until *ALL* IESG comments -that have been raised have been documented. - - - AD Followup - A generic substate indicating that the shepherding AD has the action -item to determine appropriate next steps. In particular, the -appropriate steps (and the corresponding next state or substate) -depend entirely on the nature of the issues that were raised and can -only be decided with active involvement of the shepherding AD. -Examples include: - - - if another AD raises an issue, the shepherding AD may first - iterate with the other AD to get a better understanding of the - exact issue. Or, the shepherding AD may attempt to argue that - the issue is not serious enough to bring to the attention of the - authors/WG. - - - if a documented issue is forwarded to a WG, some further - iteration may be needed before it can be determined whether a - new revision is needed or whether the WG response to an issue - clarifies the issue sufficiently. - - - when a new revision appears, the shepherding AD will first look - at the changes to determine whether they believe all outstanding - issues have been raised satisfactorily, prior to asking the ADs - who raised the original issues to verify the changes. - - - - External Party - The document is awaiting review or input from an external party (i.e, someone other than the shepherding AD, the authors, or the WG). See the "note" field for more details on who has the action. - - - Revised ID Needed - An updated ID is needed to address the issues that have been raised. - - - Publication Requested - 12 - A formal request has been made to advance/publish the document, following the procedures in Section 7.5 of RFC 2418. The request could be from a WG chair, from an individual through the RFC Editor, etc. (The Secretariat (iesg-secretary@ietf.org) is copied on these requests to ensure that the request makes it into the ID tracker.) A document in this state has not (yet) been reviewed by an AD nor has any official action been taken on it yet (other than to note that its publication has been requested. - - - AD Evaluation - 12 - A specific AD (e.g., the "Area Advisor" for the WG) has begun their -review of the document to verify that it is ready for -advancement. The shepherding AD is responsible for doing any -necessary review before starting an IETF Last Call or sending the -document directly to the IESG as a whole. - - - Expert Review - 5 - An AD sometimes asks for an external review by an outside party as -part of evaluating whether a document is ready for advancement. -MIBs, for example, are reviewed by the "MIB doctors". Other types -of reviews may also be requested (e.g., security, operations impact, -etc.) Documents stay in this state until the review is complete and -possibly until the issues raised in the review are addressed. See -the "note" field for specific details on the nature of the review. - - - Last Call Requested - 12 - The AD has requested that the Secretariat start an IETF Last Call, -but the the actual Last Call message has not been sent yet. - - - - In Last Call - 3 - The document is currently waiting for IETF Last Call to -complete. Last Calls for WG documents typically last 2 weeks, those -for individual submissions last 4 weeks. - - - Waiting for Writeup - 4 - Before a standards-track or BCP document is formally considered by -the entire IESG, the AD must write up a protocol action. The -protocol action is included in the approval message that the -Secretariat sends out when the document is approved for publication -as an RFC. - - - Waiting for AD Go-Ahead - 3 - As a result of the IETF Last Call, comments may need to be responded -to and a revision of the ID may be needed as well. The AD is -responsible for verifying that all Last Call comments have been -adequately addressed and that the (possibly revised) document is in -the ID directory and ready for consideration by the IESG as a whole. - - - IESG Evaluation - 8 - The document is now (finally!) being formally reviewed by the entire -IESG. Documents are discussed in email or during a bi-weekly IESG -telechat. In this phase, each AD reviews the document and airs any -issues they may have. Unresolvable issues are documented as -"discuss" comments that can be forwarded to the authors/WG. See the -description of substates for additional details about the current -state of the IESG discussion. - - - - IESG Evaluation - Defer - 1 - During a telechat, one or more ADs requested an additional 2 weeks -to review the document. A defer is designed to be an exception -mechanism, and can only be invoked once, the first time the document -comes up for discussion during a telechat. - - - Approved-announcement to be sent - 99 - The IESG has approved the document for publication, but the -Secretariat has not yet sent out on official approval message. - - - Approved-announcement sent - 99 - The IESG has approved the document for publication, and the -Secretariat has sent out the official approval message to the RFC -editor. - - - RFC Ed Queue - 13 - The document is in the RFC editor Queue (as confirmed by -http://www.rfc-editor.org/queue.html) - - - RFC Published - 99 - The ID has been published as an RFC. - - - DNP-waiting for AD note - 9 - Do Not Publish: The IESG recommends against publishing the document, -but the writeup explaining its reasoning has not yet been produced. -DNPs apply primarily to individual submissions received through the -RFC editor. See the "note" field for more details on who has the -action item. - - - DNP-announcement to be sent - 9 - The IESG recommends against publishing the document, the writeup -explaining its reasoning has been produced, but the Secretariat has -not yet sent out the official "do not publish" recommendation -message. - - - AD is watching - 99 - An AD is aware of the document and has chosen to place the document -in a separate state in order to keep a closer eye on it (for -whatever reason). Documents in this state are still not being -actively tracked in the sense that no formal request has been made -to publish or advance the document. The sole difference between -this state and "I-D Exists" is that an AD has chosen to put it in a -separate state, to make it easier to keep track of (for his or her -own reasons). - - - Dead - 99 - Document is "dead" and is no longer being tracked. (E.g., it has -been replaced by another document with a different name, it has been -withdrawn, etc.) - - - WG - - - PWG - - - BOF - - - AG - - - TEAM - - - 2010-05-20 - 2010-06-03 - 2010-06-17 - - - none - Individual Submissions - INDIVIDUAL SUBMISSIONS - - - 2010-07-05 - 1st Cut-Off Date (Initial version) - first - - - 2010-07-12 - 2nd Cut-Off Date (Update version) - second - - - 2010-07-26 - Date of Monday of IETF - third - - - 2010-07-29 - All I-Ds will be processed by - fourth - - - 2010-08-02 - Date of Monday after IETF - fifth - - - 2010-06-28 - Date for List of Approved V-00 Submissions from WG Chairs - sixth - - \ No newline at end of file + + + + 1324 + 104942 + + + 1092 + 2324 + + + 1157 + 4763 + + + 1179 + 188 + + + 1190 + 2324 + + + 1193 + 101568 + + + 1199 + 2372 + + + 1264 + 2744 + + + 1260 + 19790 + + + 1249 + 2329 + + + 1541 + 103264 + + + 1008 + 5376 + + + 1324 + 17253 + + + 1092 + 2515 + + + 1190 + 4817 + + + 1052 + 21072 + + + 1346 + 4356 + + + 1541 + 6842 + + + 1199 + 2723 + + + 1179 + 2853 + + + 1193 + 6699 + + + 1179 + 773 + + + 1260 + 19483 + + + + 106956 + + + 934 + 105907 + + + 1683 + 103539 + + + 1052 + 2348 + + + 1683 + 103961 + + + 1249 + 104198 + + + 934 + 102154 + + + business + Mr. + Jari + JARI + + + Arkko + ARKKO + + 1998-03-11 + WEB + 1996-11-22 + juliek + W + + + business + Mr. + Fred + FRED + + + Baker + BAKER + + 1999-11-17 + scoya + + Unknown + W + + + business + + Ronald + RONALD + + + Bonica + BONICA + + 1998-04-28 + WEB + 1998-04-28 + WEB + W + + + business + Mr. + Scott + SCOTT + O. + O. + Bradner + BRADNER + + 1998-03-12 + WEB + + Unknown + W + + + business + Mr. + Scott + SCOTT + O. + O. + Bradner + BRADNER + + 1998-03-12 + WEB + + Unknown + W + + + business + Dr. + Stewart + STEWART + + + Bryant + BRYANT + + 1991-10-16 + Unknown + + Unknown + W + + + business + Mr. + Ross + ROSS + + + Callon + CALLON + + 1998-04-30 + WEB + + Unknown + W + + + business + Mr. + Gonzalo + GONZALO + + + Camarillo + CAMARILLO + + 1999-03-11 + WEB + 1999-03-11 + WEB + W + + + business + Mr. + Stephen + STEPHEN + J. + J. + Coya + COYA + + 2000-08-16 + scoya + + You + W + + + business + Mr. + David + DAVID + H. + H. + Crocker + CROCKER + + 1999-01-14 + WEB + + Unknown + W + + + business + Mr. + Ralph + RALPH + E. + E. + Droms + DROMS + + 2001-07-16 + scoya + + Unknown + W + + + business + Dr. + Lars + LARS + + + Eggert + EGGERT + + 2000-11-30 + nsyracus + 2000-11-30 + nsyracus + + + + business + + Adrian + ADRIAN + + + Farrel + FARREL + + 2009-07-17 + cmm + 2000-02-16 + nsyracus + W + + + business + Mr. + Robert + ROBERT + + + Hagens + HAGENS + + 1995-11-02 + dlegare + + Unknown + W + + + business + Mr. + David + DAVID + + + Harrington + HARRINGTON + + 1997-10-29 + WEB + 1994-11-04 + mbeaulie + W + + + business + + Russ + RUSS + + + Housley + HOUSLEY + + 2001-03-26 + scoya + + Unknown + W + + + business + Ms. + Deirdre + DEIRDRE + C. + C. + Kostick + KOSTICK + + 1998-03-12 + WEB + + Unknown + W + + + business + Ms. + Allison + ALLISON + J. + J. + Mankin + MANKIN + + 2001-03-27 + mbeaulie + + Unknown + W + + + business + Ms. + April + APRIL + + + Marine + MARINE + + 2000-01-04 + mbeaulie + + Unknown + W + + + business + M. + Alexey + ALEXEY + + + Melnikov + MELNIKOV + + 2009-07-08 + cmm + 1998-08-10 + cclark + W + + + business + Mr. + Michael + MICHAEL + D. + D. + O'Dell + O'DELL + + 1998-03-23 + WEB + + Unknown + W + + + business + Mr. + David + DAVID + + + Oran + ORAN + + 2001-01-12 + mbeaulie + + Unknown + W + + + business + Mr. + Tim + TIM + + + Polk + POLK + + 1998-03-16 + WEB + 1996-03-13 + mbeaulie + W + + + business + Mr. + Dan + DAN + + + Romascanu + ROMASCANU + + 2000-10-03 + scoya + + Unknown + W + + + + + Peter + PETER + + + Saint-Andre + SAINT-ANDRE + + 2002-06-24 + INTERNAL + 2002-06-24 + + + + + business + + Robert + ROBERT + + + Sparks + SPARKS + + 2009-07-07 + scoya + 1999-10-21 + nsyracus + + + + + + + + + + TBD + TBD + + 2005-01-25 + INTERNAL + 2005-01-25 + + + + + business + Mr. + Sean + SEAN + + + Turner + TURNER + + 1999-01-21 + WEB + 1996-01-24 + dbates + W + + + business + Mr. + Bert + BERT + + + Wijnen + WIJNEN + + 2000-06-01 + scoya + + Unknown + W + + + business + Mr. + Alex + ALEX + D. + D. + Zinin + ZININ + + 1999-02-26 + cclark + 1999-02-26 + cclark + W + + + business + Mrs. + Karen + KAREN + + + Moreland + MORELAND + + 1999-02-26 + cclark + 1999-02-26 + cclark + W + + + scoya + deleted + 3 + Steve + Coya + 188 + scoya + + + + sob + deleted + 2 + Scott + Bradner + 2324 + + 1 + + + mankin + deleted + 2 + Allison + Mankin + 2515 + + 1 + + + bwijnen + deleted + 2 + Bert + Wijnen + 6842 + + 1 + + + marine + deleted + 3 + April + Marine + 4356 + + + + + azinin + deleted + 2 + Alex + Zinin + 103264 + azinin + 1 + + + rhousley + deleted + 1 + Russ + Housley + 5376 + + 0 + + + jari.arkko@ericsson.com + deleted + 1 + Jari + Arkko + 21072 + 0 + 1 + + + dromasca@avaya.com + deleted + 1 + Dan + Romascanu + 6699 + 0 + 1 + + + rcallon@juniper.net + deleted + 2 + Ross + Callon + 2723 + 0 + 1 + + + lars.eggert@nokia.com + deleted + 1 + Lars + Eggert + 104942 + 0 + 1 + + + alexey.melnikov@isode.com + deleted + 1 + Alexey + Melnikov + 102154 + 0 + 1 + + + rbonica@juniper.net + deleted + 1 + Ron + Bonica + 101568 + 0 + 1 + + + tim.polk@nist.gov + deleted + 1 + Tim + Polk + 19790 + 0 + 0 + + + rjsparks@nostrum.com + deleted + 1 + Robert + Sparks + 103961 + 0 + 0 + + + rdroms.ietf@gmail.com + deleted + 1 + Ralph + Droms + 2348 + 0 + 1 + + + klm + deleted + 0 + Karen + Moreland + 108300 + + 0 + + + adrian@olddog.co.uk + deleted + 1 + Adrian + Farrel + 104198 + 0 + 1 + + + stpeter@stpeter.im + deleted + 1 + Peter + Saint-Andre + 105907 + + + + + gonzalo.camarillo@ericsson.com + deleted + 1 + Gonzalo + Camarillo + 103539 + + + + + stbryant@cisco.com + deleted + 1 + Stewart + Bryant + 2329 + + + + + turners@ieca.com + deleted + 1 + Sean + Turner + 19483 + + + + + 104942 + INET + 1 + lars.eggert@nokia.com + Email Address + + + 2324 + INET + 1 + sob@harvard.edu + + + + 4763 + INET + 1 + kostick@qsun.att.com + + + + 188 + INET + 1 + scoya@ietf.org + + + + 2324 + INET + 1 + sob@harvard.edu + + + + 101568 + INET + 1 + rbonica@juniper.net + + + + 2372 + INET + 1 + hagens@mci.net + + + + 2744 + INET + 1 + dcrocker@brandenburg.com + this address is his 1st preference + + + 19790 + INET + 1 + tim.polk@nist.gov + + + + 2329 + INET + 1 + stbryant@cisco.com + + + + 103264 + INET + 1 + alex.zinin@alcatel-lucent.com + Email + + + 5376 + INET + 1 + housley@vigilsec.com + Email + + + 17253 + INET + 1 + ietfdbh@comcast.net + + + + 2515 + INET + 1 + mankin@psg.com + Email + + + 4817 + INET + 1 + mo@uu.net + + + + 21072 + INET + 1 + jari.arkko@piuha.net + Email + + + 4356 + INET + 1 + april.marine@nominum.com + + + + 6842 + INET + 1 + bertietf@bwijnen.net + Email + + + 2723 + INET + 1 + rcallon@juniper.net + Email + + + 2853 + INET + 1 + fred.baker@cisco.com + + + + 6699 + INET + 1 + dromasca@avaya.com + Email + + + 773 + INET + 1 + oran@cisco.com + + + + 19483 + INET + 1 + turners@ieca.com + + + + 106956 + INET + 1 + noreply@ietf.org + + + + 105907 + INET + 1 + stpeter@stpeter.im + + + + 103539 + INET + 1 + gonzalo.camarillo@ericsson.com + + + + 2348 + INET + 1 + rdroms.ietf@gmail.com + + + + 103961 + INET + 1 + rjsparks@nostrum.com + + + + 104198 + INET + 1 + adrian.farrel@huawei.com + + + + 102154 + INET + 1 + alexey.melnikov@isode.com + + + + Active + + + Expired + + + RFC + + + Withdrawn by Submitter + + + Replaced + + + Withdrawn by IETF + + + BCP + + + Draft Standard + + + Experimental + + + Historic + + + Informational + + + Proposed Standard + + + Standard + + + None + + + Request + + + Point Raised - writeup needed + IESG discussions on the document have raised some issues that need +to be brought to the attention of the authors/WG, but those issues +have not been written down yet. (It is common for discussions during +a telechat to result in such situations. An AD may raise a possible +issue during a telechat and only decide as a result of that +discussion whether the issue is worth formally writing up and +bringing to the attention of the authors/WG). A document stays in +the "Point Raised - Writeup Needed" state until *ALL* IESG comments +that have been raised have been documented. + + + AD Followup + A generic substate indicating that the shepherding AD has the action +item to determine appropriate next steps. In particular, the +appropriate steps (and the corresponding next state or substate) +depend entirely on the nature of the issues that were raised and can +only be decided with active involvement of the shepherding AD. +Examples include: + + - if another AD raises an issue, the shepherding AD may first + iterate with the other AD to get a better understanding of the + exact issue. Or, the shepherding AD may attempt to argue that + the issue is not serious enough to bring to the attention of the + authors/WG. + + - if a documented issue is forwarded to a WG, some further + iteration may be needed before it can be determined whether a + new revision is needed or whether the WG response to an issue + clarifies the issue sufficiently. + + - when a new revision appears, the shepherding AD will first look + at the changes to determine whether they believe all outstanding + issues have been raised satisfactorily, prior to asking the ADs + who raised the original issues to verify the changes. + + + + External Party + The document is awaiting review or input from an external party (i.e, someone other than the shepherding AD, the authors, or the WG). See the "note" field for more details on who has the action. + + + Revised ID Needed + An updated ID is needed to address the issues that have been raised. + + + Publication Requested + 12 + A formal request has been made to advance/publish the document, following the procedures in Section 7.5 of RFC 2418. The request could be from a WG chair, from an individual through the RFC Editor, etc. (The Secretariat (iesg-secretary@ietf.org) is copied on these requests to ensure that the request makes it into the ID tracker.) A document in this state has not (yet) been reviewed by an AD nor has any official action been taken on it yet (other than to note that its publication has been requested. + + + AD Evaluation + 12 + A specific AD (e.g., the "Area Advisor" for the WG) has begun their +review of the document to verify that it is ready for +advancement. The shepherding AD is responsible for doing any +necessary review before starting an IETF Last Call or sending the +document directly to the IESG as a whole. + + + Expert Review + 5 + An AD sometimes asks for an external review by an outside party as +part of evaluating whether a document is ready for advancement. +MIBs, for example, are reviewed by the "MIB doctors". Other types +of reviews may also be requested (e.g., security, operations impact, +etc.) Documents stay in this state until the review is complete and +possibly until the issues raised in the review are addressed. See +the "note" field for specific details on the nature of the review. + + + Last Call Requested + 12 + The AD has requested that the Secretariat start an IETF Last Call, +but the the actual Last Call message has not been sent yet. + + + + In Last Call + 3 + The document is currently waiting for IETF Last Call to +complete. Last Calls for WG documents typically last 2 weeks, those +for individual submissions last 4 weeks. + + + Waiting for Writeup + 4 + Before a standards-track or BCP document is formally considered by +the entire IESG, the AD must write up a protocol action. The +protocol action is included in the approval message that the +Secretariat sends out when the document is approved for publication +as an RFC. + + + Waiting for AD Go-Ahead + 3 + As a result of the IETF Last Call, comments may need to be responded +to and a revision of the ID may be needed as well. The AD is +responsible for verifying that all Last Call comments have been +adequately addressed and that the (possibly revised) document is in +the ID directory and ready for consideration by the IESG as a whole. + + + IESG Evaluation + 8 + The document is now (finally!) being formally reviewed by the entire +IESG. Documents are discussed in email or during a bi-weekly IESG +telechat. In this phase, each AD reviews the document and airs any +issues they may have. Unresolvable issues are documented as +"discuss" comments that can be forwarded to the authors/WG. See the +description of substates for additional details about the current +state of the IESG discussion. + + + + IESG Evaluation - Defer + 1 + During a telechat, one or more ADs requested an additional 2 weeks +to review the document. A defer is designed to be an exception +mechanism, and can only be invoked once, the first time the document +comes up for discussion during a telechat. + + + Approved-announcement to be sent + 99 + The IESG has approved the document for publication, but the +Secretariat has not yet sent out on official approval message. + + + Approved-announcement sent + 99 + The IESG has approved the document for publication, and the +Secretariat has sent out the official approval message to the RFC +editor. + + + RFC Ed Queue + 13 + The document is in the RFC editor Queue (as confirmed by +http://www.rfc-editor.org/queue.html) + + + RFC Published + 99 + The ID has been published as an RFC. + + + DNP-waiting for AD note + 9 + Do Not Publish: The IESG recommends against publishing the document, +but the writeup explaining its reasoning has not yet been produced. +DNPs apply primarily to individual submissions received through the +RFC editor. See the "note" field for more details on who has the +action item. + + + DNP-announcement to be sent + 9 + The IESG recommends against publishing the document, the writeup +explaining its reasoning has been produced, but the Secretariat has +not yet sent out the official "do not publish" recommendation +message. + + + AD is watching + 99 + An AD is aware of the document and has chosen to place the document +in a separate state in order to keep a closer eye on it (for +whatever reason). Documents in this state are still not being +actively tracked in the sense that no formal request has been made +to publish or advance the document. The sole difference between +this state and "I-D Exists" is that an AD has chosen to put it in a +separate state, to make it easier to keep track of (for his or her +own reasons). + + + Dead + 99 + Document is "dead" and is no longer being tracked. (E.g., it has +been replaced by another document with a different name, it has been +withdrawn, etc.) + + + WG + + + PWG + + + BOF + + + AG + + + TEAM + + + 2010-05-20 + 2010-06-03 + 2010-06-17 + + + none + Individual Submissions + INDIVIDUAL SUBMISSIONS + + + 2010-07-05 + 1st Cut-Off Date (Initial version) + first + + + 2010-07-12 + 2nd Cut-Off Date (Update version) + second + + + 2010-07-26 + Date of Monday of IETF + third + + + 2010-07-29 + All I-Ds will be processed by + fourth + + + 2010-08-02 + Date of Monday after IETF + fifth + + + 2010-06-28 + Date for List of Approved V-00 Submissions from WG Chairs + sixth + + diff --git a/ietf/idrfc/tests.py b/ietf/idrfc/tests.py index 39d058c3e..0e1f574b2 100644 --- a/ietf/idrfc/tests.py +++ b/ietf/idrfc/tests.py @@ -46,6 +46,9 @@ from ietf.idtracker.models import * from ietf.utils.test_utils import SimpleUrlTestCase, RealDatabaseTest, login_testing_unauthorized from ietf.utils.test_runner import mail_outbox +from ietf.ietfworkflows.models import Stream +from django.contrib.auth.models import User + class IdRfcUrlTestCase(SimpleUrlTestCase): def testUrls(self): self.doTestUrls(__file__) @@ -179,6 +182,7 @@ class EditInfoTestCase(django.test.TestCase): state_change_notice_to="test@example.com", note="", telechat_date="", + stream=Stream.objects.get(name=u'IETF').id, )) self.assertEquals(r.status_code, 302) @@ -206,6 +210,7 @@ class EditInfoTestCase(django.test.TestCase): job_owner=str(draft.idinternal.job_owner_id), state_change_notice_to="test@example.com", note="", + stream=Stream.objects.get(name=u'IETF').id, ) from ietf.iesg.models import TelechatDates @@ -265,6 +270,7 @@ class EditInfoTestCase(django.test.TestCase): state_change_notice_to="test@example.com", note="This is a note", telechat_date="", + stream=Stream.objects.get(name=u'IETF').id, )) self.assertEquals(r.status_code, 302) diff --git a/ietf/idrfc/views_edit.py b/ietf/idrfc/views_edit.py index c48fc11ea..3cde5ba3a 100644 --- a/ietf/idrfc/views_edit.py +++ b/ietf/idrfc/views_edit.py @@ -22,6 +22,10 @@ from ietf.idrfc.mails import * from ietf.idrfc.utils import * from ietf.idrfc.lastcall import request_last_call +from ietf.ietfworkflows.models import Stream +from ietf.ietfworkflows.utils import update_stream +from ietf.ietfworkflows.streams import get_stream_from_draft + class ChangeStateForm(forms.Form): state = forms.ModelChoiceField(IDState.objects.all(), empty_label=None, required=True) @@ -101,6 +105,7 @@ class EditInfoForm(forms.Form): intended_status = forms.ModelChoiceField(IDIntendedStatus.objects.all(), empty_label=None, required=True) area_acronym = forms.ModelChoiceField(Area.active_areas(), required=True, empty_label='None Selected') via_rfc_editor = forms.BooleanField(required=False, label="Via IRTF or RFC Editor") + stream = forms.ModelChoiceField(Stream.objects.all(), empty_label=None, required=True) job_owner = forms.ModelChoiceField(IESGLogin.objects.filter(user_level__in=(IESGLogin.AD_LEVEL, IESGLogin.INACTIVE_AD_LEVEL)).order_by('user_level', 'last_name'), label="Responsible AD", empty_label=None, required=True) create_in_state = forms.ModelChoiceField(IDState.objects.filter(document_state_id__in=(IDState.PUBLICATION_REQUESTED, IDState.AD_WATCHING)), empty_label=None, required=False) state_change_notice_to = forms.CharField(max_length=255, label="Notice emails", help_text="Separate email addresses with commas", required=False) @@ -279,6 +284,13 @@ def edit_info(request, name): doc.idinternal.event_date = date.today() doc.idinternal.status_date = date.today() + + update_stream(doc, + "Setting stream while adding document to the tracker", + person=request.user.get_profile().person(), + to_stream = r['stream'] + ) + if changes and not new_document: email_owner(request, doc, orig_job_owner, login, "\n".join(changes)) if new_document: @@ -288,6 +300,8 @@ def edit_info(request, name): doc.save() return HttpResponseRedirect(doc.idinternal.get_absolute_url()) else: + stream=get_stream_from_draft(doc) + stream_id = stream.id if stream else None init = dict(intended_status=doc.intended_status_id, area_acronym=doc.idinternal.area_acronym_id, job_owner=doc.idinternal.job_owner_id, @@ -295,6 +309,7 @@ def edit_info(request, name): note=dehtmlify_textarea_text(doc.idinternal.note), telechat_date=initial_telechat_date, returning_item=doc.idinternal.returning_item, + stream=stream_id ) form = EditInfoForm(old_ads=False, initial=init)