<div dir="ltr">Hi,<div><br></div><div>this would be a software/communications project, for which clear requirements would be a good start (not the end.)</div><div><br></div><div>Use cases and constraints go first, don't they?</div><div><br></div><div>The use cases have to be analyzed and documented, and in our case, discussed and stabilized.</div><div><br></div><div>The constraints should include among others: compliance with Internet standards and best current practice; parsimony in the resources required (text better than HTML, push better than having to access a dozen or more Websites), openness, transparency/accountabiilty. Suitability to low-bandwidth, old operating system and browser, limited-capabilities devices for people in island/edge conditions, or for busy travellers, should also be among the desirable properties of any communications system.</div><div><br></div><div>Erik and Carlton have already expressed some keystones which favor email or at least some fundamental properties of email. I join in support. </div><div><br></div><div>Joly, call me an "old-timer" if doing so is a suitable way of polarizing the list. We see all too many "new-timers" discussing ICANN issues with all-too-scant knowledge and respect for Internet basics. Let's find a cooperative way that works for all. </div><div><br></div><div>Let's hope that the now very long-standing Technology WG/TF takes all this into account. </div><div><br></div><div>Let's also note that the "flurry of unsubscribes to the list" was about... 4 messages? (and it has been explained away.)</div><div><br></div><div>Alejandro Pisanty</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 20, 2017 at 12:57 PM, Carlton Samuels <span dir="ltr"><<a href="mailto:carlton.samuels@gmail.com" target="_blank">carlton.samuels@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 19, 2017 at 3:20 PM, Joly MacFie <span dir="ltr"><<a href="mailto:joly@punkcast.com" target="_blank">joly@punkcast.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> it's main and important function is to provide shallow water for new joiners to get their feet wet, get an idea of the community, and a sense of belonging. A newbie playground. The idea being that the keen ones may graduate to traditional vectors such wg's, email lists, wiki's etc </blockquote></div><br><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small">I would not argue that there are more efficient ways to organize the communications. But email is always considered a 'come direct to me' mode instead of the 'come find me' mode of the website/wiki/portal modalities for communication. </div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small">When an ALS is ratified by the ALAC, the email subscription by ALS representative to at least the Worldwide list comes with that ratification. It follows for pretty much the same reasons -flipped - that Joly outlined in the ISOC context.</div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small">Just by modeling of a traditional message, a subject line is meant to indicate channel. The response to the subject line in the content body would have been a useful indicator of interest and, driver for that channelized discussion. </div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small">But um...........well.....</div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:small">-Carlton </div><br><br clear="all"><div><div class="m_-2261173924534264941gmail_signature"><div dir="ltr"><div><br>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Planning, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div>
</div></div>
<br>______________________________<wbr>_________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.<wbr>org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org" rel="noreferrer" target="_blank">http://atlarge.icann.org</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">- - - - - - - - - - - - - - - - - - - - - - - - - - -<br> Dr. Alejandro Pisanty<br>Facultad de Química UNAM<br>Av. Universidad 3000, 04510 Mexico DF Mexico<br>+52-1-5541444475 FROM ABROAD<br>+525541444475 DESDE MÉXICO SMS +525541444475<br>Blog: <a href="http://pisanty.blogspot.com" target="_blank">http://pisanty.blogspot.com</a><br>LinkedIn: <a href="http://www.linkedin.com/in/pisanty" target="_blank">http://www.linkedin.com/in/pisanty</a><br>Unete al grupo UNAM en LinkedIn, <a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614" target="_blank">http://www.linkedin.com/e/gis/22285/4A106C0C8614</a><br>Twitter: <a href="http://twitter.com/apisanty" target="_blank">http://twitter.com/apisanty</a><br>---->> Unete a ISOC Mexico, <a href="http://www.isoc.org" target="_blank">http://www.isoc.org</a><br>. . . . . . . . . . . . . . . .</div>
</div>