Document shepherds and the shepherd writeup should be associated with documents, not working groups

[ietf-svn-bot]

keyword_sprint resolution_fixed type_defect | by rjsparks@nostrum.com

---

Currently, it is not possible to use the document writeup tools with AD sponsored individual submissions because the implementation ties these things to working groups rather than documents.

---

Issue migrated from trac:967 at 2022-03-04 02:43:58 +0000

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from new to closed

[ietf-svn-bot]

@rjsparks@nostrum.com changed resolution from `` to fixed

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Fixed in 6c7f852:

Moves the interface to edit shepherds and sheperd writeups out of the wgtracker interface and into the doc views (via idrfc).
Added a little to the simple authorization code (can_edit_) in idrfc.
Added a way to reset the writeup to the current templates (leaving extension points to take templates for non-ietf stream documents).
Fixes bug #967

Implementation notes:
Currently reused EmailsField - in the long run a better approach will be to build a similar PersonField.

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Fixed in becd10a:

Merged 3bc9e9a from rjsparks@nostrum.com:

Moves the interface to edit shepherds and sheperd writeups out of the
wgtracker interface and into the doc views (via idrfc).
Added a little to the simple authorization code (can_edit_) in idrfc.
Added a way to reset the writeup to the current templates (leaving
extension points to take templates for non-ietf stream documents).
Fixes bug #967.

Implementation notes:
Currently reused EmailsField -- in the long
run a better approach will be to build a similar PersonField.

This also fixes tickets #834 and #691 (which were effectively duplicates
of #967)