Skip to content

IESG: Who has the action #3146

@ietf-svn-bot

Description

@ietf-svn-bot

owner:jennifer@painless-security.com resolution_fixed type_enhancement | by rjsparks@nostrum.com


The IESG would like to have a new mechanism to track who has the action on a given document. Based on the conversation we will separate this from the desire to track time in state/substate (see #2771).

As a first step, we plan to add the ability to associate a set of people (Person objects) with the document. The association would track when each person was added to the set. This should be displayed on the document page, and in the AD dashboard, labeled "Action Holders".

The ability to use this mechanism would start when the document entered a non "ID Exists" IESG state, (which is usually publication requested). This mechanism will not (initially) be available to chairs to use during WG processing, nor will it be initially available for use in other streams. Design of the mechanism will anticipate that at least those two other use cases are likely to be requested in the future.

ADs will, in general, add people manually to the set. The UI will make it easy to add authors, shepherd, chairs and similar roles.

There will be a small amount of initial automation for maintaining the set:

  • The set will start out set to the responsible AD
  • The set will be reset to the responsible AD whenever a major state change occurs, with the exception of transitioning into any states at or beyond approved annc to be sent, where the set will be reset to empty.
  • Authors will be added to the set when the revised-id needed tag is added, and removed when the tag is removed.

A comment (DocEvent) will be added to the document's history any time the set changes.

The set will be shown on the AD dashboard, and any other page that shows search results (such as the WG documents pages). When a threshold has passed (Barry suggests 20 days) they will be decorated with time in the set.

There will also be a mechanism available to the AD to cause a reminder to be sent to the people in the set that they have something to do.

Note that there are special cases where the token holder is a pseudo-person. IANA is a good example. We have a Person record for IANA already and the controls to add people (reusing the existing person choosers) need to allow that Person object to be selected.

The initial implementation will only allow ADs and the secretariat to manage the set. However the design should anticipate that sometimes it will make sense to remove people before a state change. For example, one of several authors may opt out, leaving a designated editor holding the action. One of several discuss holders might clear a discuss. We will look at adding the ability for these people to self-manage their entry in the set at a later time.


Issue migrated from trac:3146 at 2022-03-04 08:07:04 +0000

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions