Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we add a document link to the discuss/comment header text? #916

Closed
ietf-svn-bot opened this issue Dec 11, 2012 · 8 comments
Closed

Can we add a document link to the discuss/comment header text? #916

ietf-svn-bot opened this issue Dec 11, 2012 · 8 comments

Comments

@ietf-svn-bot
Copy link

keyword_easy keyword_sprint resolution_fixed type_enhancement | by barryleiba@computer.org


When an AD records a ballot comment on a document and clicks "Save and Send Email", the following format is used:

==========================
Joe Slobotnik has entered the following ballot position for
draft-ietf-fubar-lmnop: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.




----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This whole document is fubar.

----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

And I don't like it, either.

==========================

Especially if this is part of continuing discussion of an older document that's been on a telechat and is off the agenda now, it would be nice to have one-click access to the document. Could we add that, like this (and maybe trim extra blank lines at the same time)?:

==========================
Joe Slobotnik has entered the following ballot position for
draft-ietf-fubar-lmnop: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-fubar-lmnop/

----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This whole document is fubar.

----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

And I don't like it, either.

==========================

Issue migrated from trac:916 at 2022-03-04 02:39:39 +0000

@ietf-svn-bot
Copy link
Author

@barryleiba@computer.org edited the issue description

@ietf-svn-bot
Copy link
Author

@rjsparks@nostrum.com changed priority from n/a to medium

@ietf-svn-bot
Copy link
Author

@rjsparks@nostrum.com changed keywords from `` to sprint, easy

@ietf-svn-bot
Copy link
Author

@rjsparks@nostrum.com edited the issue description

@ietf-svn-bot
Copy link
Author

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

@ietf-svn-bot
Copy link
Author

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

@ietf-svn-bot
Copy link
Author

@adam@nostrum.com commented


Fixed in personal/adam/v4.60@5901

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com commented


Fixed in d787997:

Merged 30dec0e from adam@nostrum.com:
Added a document link to the emails sent on discuss/comment changes. Fixes bug #916

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant