<div>I think George and Paul have very good suggestions, and appreciate the kind letter of encouragement from the co-chairs.</div><div><br></div><div>I hope the folks who have changed to observer status will reconsider re-joining as full participants as we continue to make improvements going forward. There is no deadline to join. We all benefit from having your involvement and perspective inside this very talented and diverse group.</div><div><br></div><div>Have a great weekend.</div><div><br></div><div>Best,</div><div>Claudio</div><div><br></div><div><br><div class="gmail_quote"><div>On Fri, May 5, 2017 at 4:17 PM Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com">gpmgroup@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div>Hi Mary,<br></div><div><br>One thing that ICANN could do that would really help in finding documents sent as attachments would be to modify the mailing list software so it doesn't add a</div></div></div></div><div><div><div><div><br><br>___________________________________________<br>gnso-rpm-wg mailing list<br><a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a> <br><br></div></div></div></div><div><div><div><div></div>to emails.<br><br></div>Example here: <a href="http://gpm.info/msg.txt" target="_blank">http://gpm.info/msg.txt</a> (txt copy of an example ICANN email). Scroll to the bottom to see the added text or see email-1.png attachment.<br><br></div><div>The reason why it would be very helpful to remove this text is because what happens in many email clients is this information gets stripped off as a separate attachment. Where there are lots of emails this makes it very hard to quickly locate emails with attachments that contain useful information.<br><br></div><div>This can be seen in the email-2.png attachment. In this you can see:<br></div><div>(a) the arrow on the left hand side points to the emails with a paperclip indicating an attachment (22 of 24 the emails)<br></div><div>(b) the circle on the right around the attachment from Massimo ATT00067.txt (240B) which only contains <br></div></div><div><div><br>___________________________________________<br>gnso-rpm-wg mailing list<br><a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br><br></div></div><div><div></div><div>which is also shown circled in notepad. <br><br></div><div></div><div></div><div>(c) the email from Julie which is the only email in that screenshot which has a real attachment worth reading!<br><br></div><div>Many thanks,<br><br><br></div><div>Paul.<br></div><div><br></div><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 5, 2017 at 6:02 PM, George Kirikos <span><<a href="mailto:icann@leap.com" target="_blank">icann@leap.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks,<br>
<span><br>
On Fri, May 5, 2017 at 12:34 PM, Mary Wong <<a href="mailto:mary.wong@icann.org" target="_blank">mary.wong@icann.org</a>> wrote:<br>
> We welcome your responses, and in particular your suggestions for how we can<br>
> narrow our discussion points at any given time and encourage members to stay<br>
> focused on the main point under discussion -- while also accommodating the<br>
> fact that there is some substantial interdependency between the issues we<br>
> are grappling with.<br>
<br>
</span>I had a few suggestions:<br>
<br>
1. I suggest that folks try to trim the quoted emails that they're<br>
responding to, in order to shorten the length of the text to just the<br>
relevant/essential part(s) of the prior emails (as I just demonstrated<br>
above), plus anything new they wish to contribute. It makes it a lot<br>
easier to follow the threads, especially when some of the threads<br>
included 50+ prior emails within the body of the message. It also<br>
improves searching one's own email archives, to generate fewer matches<br>
when searching for something (e.g. if I searched for specific text,<br>
I'd currently find that text not only in the original email, but also<br>
in dozens of followup emails, making it tougher to find what I'm<br>
looking for).<br>
<br>
To pick a random example, see how the following message has "+1" as<br>
the "new" text:<br>
<br>
<a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2017-May/001945.html" rel="noreferrer" target="_blank">http://mm.icann.org/pipermail/gnso-rpm-wg/2017-May/001945.html</a><br>
<br>
but one would really have a hard time figuring out what's being<br>
supported, unless one read all the prior messages included below that<br>
new text.<br>
<br>
2. Sometimes it's worth changing the Subject line of the email<br>
entirely, especially to make it easier to find things later when using<br>
the web-based archives. There are numerous emails in the archive for<br>
May 2017:<br>
<br>
<a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2017-May/date.html" rel="noreferrer" target="_blank">http://mm.icann.org/pipermail/gnso-rpm-wg/2017-May/date.html</a><br>
<br>
concerning "Agenda and documents for Working Group call this week",<br>
but the actual content of some of those messages concernsabout policy<br>
discussions (e.g. about GIs, etc.), so the subject line could have<br>
been changed to reflect that.<br>
<br>
3. Some of the "legal disclaimers" that are included automatically at<br>
the bottom of emails perhaps can be removed entirely (e.g. "This<br>
message is confidential, blah blah blah"), to further reduce message<br>
length. This is a public mailing list, and is archived on the web. For<br>
those who've setup a dedicated email address/account for ICANN mailing<br>
lists, that's easy to do. For those who are currently using just one<br>
email address for business and ICANN-related matters, it might be wise<br>
to consider creating a separate email address for public mailing<br>
lists.<br>
<br>
Have a great weekend, everyone!<br>
<br>
Sincerely,<br>
<br>
George Kirikos<br>
<a href="tel:416-588-0269" value="+14165880269" target="_blank">416-588-0269</a><br>
<a href="http://www.leap.com/" rel="noreferrer" target="_blank">http://www.leap.com/</a><br>
_______________________________________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
</blockquote></div><br></div>
_______________________________________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></blockquote></div></div>