Requirements for Improvements to the IETF Email List Archiving, Web-Based Browsing, and Search Tool
draft-sparks-genarea-mailarch-improvements-02
Yes
(Alia Atlas)
(Ben Campbell)
(Jari Arkko)
No Objection
(Alvaro Retana)
(Benoît Claise)
(Deborah Brungard)
(Joel Jaeggli)
(Martin Stiemerling)
(Terry Manderson)
Note: This ballot was opened for revision 02 and is now closed.
Alia Atlas Former IESG member
Yes
Yes
()
Unknown
Ben Campbell Former IESG member
Yes
Yes
()
Unknown
Jari Arkko Former IESG member
Yes
Yes
()
Unknown
Spencer Dawkins Former IESG member
Yes
Yes
(2016-03-02)
Unknown
In this text:
o Provide a link on each row of the list to the URL for that row's
message.
o Add an export type that produces a file containing a list of URIs
to each message in in the list.
o Add a hint to the UI that double-clicking on a row in the list
will open a single-message view of the associated message in a
separate view.
"in the list" means "in the message list display", doesn't it? That may be obvious in context, but I found myself wondering if someone could think things like "oh, they want a list of URIs to each message in the mailing list", or something equally confused.
"in (in) the list" has an extra "in", since I'm commenting on this text anyway.
Alvaro Retana Former IESG member
No Objection
No Objection
()
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
(2016-03-01)
Unknown
I agree with Stephen that it'd be very nice to still have access to the old "by date" and "by thread" archive format.
Benoît Claise Former IESG member
No Objection
No Objection
()
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
()
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
()
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
()
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2016-03-01)
Unknown
I have a requirement to ask about. Note that I am not trying to convince you now to accept this if you don't want to, I'm just asking for clarification, as to whether or not you mean you'll meet my requirement. If your answer is "no, that's not what's meant" then please do consider this as a new feature request, and handle those as you think best, as part of this work, or later, or never. Here's my question: - Does section 3 mean that there'll be a way to get from the usual https://mailarchive.ietf.org/ view to an equivalent mhonarc view? I'd like if one could do that for an individual message or (maybe) a thread. I'd be ok if that function stopped working if we decided to not keep mhonarc archives too, but I, and I think some others, prefer mhonarc's simplicity when I don't need to search, and a lot of IETF list information pages now send me to this new archive so having a way to get to the mhonarc equivalent would be great. (That might also be a way to meet some of your non-JS requirement maybe?) - section 2.7: thank you!
Terry Manderson Former IESG member
No Objection
No Objection
()
Unknown