Discussion:
[Tools-discuss] Enable reply-all for draft announcements
Martin Thomson
2018-06-27 22:20:36 UTC
Permalink
(this might be the wrong venue, but it's what I came up with)

I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
bit of a summary of changes. Because i-d-***@ietf.org (or
internet-***@ietf.org) is on the CC, this results in me opening a
ticket.

I never want to do that. Sometimes I remember to trim the list of
recipients, but I forget more often than not.

Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?

Do both of the mail aliases need to be on the CC?

___________________________________________________________
Tools-discuss mailing list
Tools-***@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
or send email to datatracker-***@ietf.org

Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
or send email to ***@tools.ietf.org
Warren Kumari
2018-06-28 15:16:18 UTC
Permalink
Post by Martin Thomson
(this might be the wrong venue, but it's what I came up with)
I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
ticket.
I never want to do that. Sometimes I remember to trim the list of
recipients, but I forget more often than not.
Wow, you sometimes remember? I always mean to, but basically never manage.

This sounds like a great suggestion -- why are those there? It must get
super annoying to keep closing those tickets.

W
Post by Martin Thomson
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?
Do both of the mail aliases need to be on the CC?
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
--
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
---maf
Robert Sparks
2018-06-29 17:16:32 UTC
Permalink
This should be straightforward to implement - see
<https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97>.
Should be an easy sprint task.

I've created ticket <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530>

RjS
On Wed, Jun 27, 2018 at 5:20 PM Martin Thomson
(this might be the wrong venue, but it's what I came up with)
I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
the CC, this results in me opening a
ticket.
I never want to do that.  Sometimes I remember to trim the list of
recipients, but I forget more often than not.
Wow, you sometimes remember? I always mean to, but basically never manage.
This sounds like a great suggestion -- why are those there? It must
get super annoying to keep closing those tickets.
W
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?
Do both of the mail aliases need to be on the CC?
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org <http://datatracker.ietf.org>
and mailarchive.ietf.org <http://mailarchive.ietf.org>
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org <http://tools.ietf.org> bugs at
http://tools.ietf.org/tools/issues
--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
Russ Housley
2018-06-29 18:16:30 UTC
Permalink
That one is too easy to let wait for the code sprint. I just offered a commit.

Russ
This should be straightforward to implement - see <https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97> <https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97>. Should be an easy sprint task.
I've created ticket <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530> <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530>
RjS
Post by Martin Thomson
(this might be the wrong venue, but it's what I came up with)
I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
ticket.
I never want to do that. Sometimes I remember to trim the list of
recipients, but I forget more often than not.
Wow, you sometimes remember? I always mean to, but basically never manage.
This sounds like a great suggestion -- why are those there? It must get super annoying to keep closing those tickets.
W
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?
Do both of the mail aliases need to be on the CC?
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss <https://www.ietf.org/mailman/listinfo/tools-discuss>
Please report datatracker.ietf.org <http://datatracker.ietf.org/> and mailarchive.ietf.org <http://mailarchive.ietf.org/>
bugs at http://tools.ietf.org/tools/ietfdb <http://tools.ietf.org/tools/ietfdb>
Please report tools.ietf.org <http://tools.ietf.org/> bugs at
http://tools.ietf.org/tools/issues <http://tools.ietf.org/tools/issues>
--
I don't think the execution is relevant when it was obviously a bad idea in the first place.
This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
---maf
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss <https://www.ietf.org/mailman/listinfo/tools-discuss>
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb <http://tools.ietf.org/tools/ietfdb>
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues <http://tools.ietf.org/tools/issues>
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
Martin Thomson
2018-07-02 00:10:29 UTC
Permalink
Thanks Robert!
Post by Russ Housley
That one is too easy to let wait for the code sprint. I just offered a commit.
Russ
This should be straightforward to implement - see <https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/submit/mail.py#L97>. Should be an easy sprint task.
I've created ticket <https://trac.tools.ietf.org/tools/ietfdb/ticket/2530>
RjS
Post by Martin Thomson
(this might be the wrong venue, but it's what I came up with)
I am probably not the only one doing this, but I tend to reply-all to
draft announcements, especially for working group drafts to provide a
ticket.
I never want to do that. Sometimes I remember to trim the list of
recipients, but I forget more often than not.
Wow, you sometimes remember? I always mean to, but basically never manage.
This sounds like a great suggestion -- why are those there? It must get super annoying to keep closing those tickets.
W
Post by Martin Thomson
Is there some mail hackery (Reply-To with a blackhole address, for
instance) that can be used to avoid this happening?
Do both of the mail aliases need to be on the CC?
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
--
I don't think the execution is relevant when it was obviously a bad idea in the first place.
This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
---maf
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
___________________________________________________________
Tools-discuss mailing list
https://www.ietf.org/mailman/listinfo/tools-discuss
Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
___________________________________________________________
Tools-discuss mailing list
Tools-***@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org and mailarchive.ietf.org
bugs at http://tools.ietf.org/tools/ietfdb
or send email to datatracker-***@ietf.org

Please report tools.ietf.org bugs at
http://tools.ietf.org/tools/issues
or send email to ***@tools.ietf.org

Loading...