<html><head></head><body><div class="ydp7e376be7yahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"><div></div>
<div dir="ltr" data-setdir="false">Ken -- </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Keep us up to date on the Town's Technology Committee and other plans which affect hybrid meetings Town-wide. That's important info and offers us important opportunities to get the equipment and expertise we will need, at little or no cost to our own members. And in exchange, we as tech-savvy group members can offer our help and knowledge to complement the Town's efforts not just for the CC, but Town-wide. Sounds like a win-win strategy.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">But as always, too many engineers may result in an overly-complex solution. Sometimes the best solutions are simpler and less costly to implement. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">That's where those of us who like me are common end-users (what Woody Leonard affectionately <span><span style="color: rgb(0, 0, 0); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;">calls </span></span>"dummies") come into play. We get to "road test" the ideas as the experts roll them out. And to beta-test before official rollout. It's called Quality Control, and the Town will need some of that as we all move forward. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I've been on some "road tests" of Jitsi Meet, and open-source alternative to Zoom. It has been a rocky road at times, especially since this happens under Linux, but it has been rewarding. And reassuring, knowing we won't be spied on as Zoom allegedly may be doing. (The same way Google allegedly spies on Chrome and Amazon allegedly spies on Ring and Echo -- Alexa -- products.) </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Again let me point out that with Windows 11, Microsoft Teams (limited consumer edition) is becoming an integral part of the Windows platform. (Teams <span><span style="color: rgb(0, 0, 0); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;">essentially </span></span>will be replacing and augmenting Skype, which Microsoft has fully "Embraced, Extended, and Extinguished".)</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">-- Bob Primak </div><div><br></div>
</div><div id="yahoo_quoted_6575380295" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, July 6, 2021, 08:08:54 PM EDT, Ken Pogran <pogran@alum.mit.edu> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv4876042933">
<div>My understanding is that
the Town is looking into technology solutions to support hybrid (in-room
+ remote) public meetings. The expectation is that, long term, there
will be legislation amending the Public Meeting Law to permanently
provide for in-person, hybrid, and fully remote public meetings. Folks
got a taste over the past year, and they're now demanding it.<br>
<br>
The idea is to implement a solution that supports an in-person meeting
in a conference room, provides good "coverage" of that meeting to remote
attendees, and allows remote attendees to participate in the same level
as though they were present in the room. Several technology solutions
are being investigated; multiple products that have come out to do this
sort of thing. (Whether these technology solutions are compatible with
the Zoom platform, or would be dependent on some other remote meting
platform, is a good question)<br>
<br>
I don't see why the principal meeting rooms at the Community Center
wouldn't be (or, at least, shouldn't be) included in an eventual Town
"buy" of such technology.<br>
<br>
Ken Pogran<br>
</div>
</div>===============================================<br>::The Lexington Computer and Technology Group Mailing List::<br>Reply goes to sender only; Reply All to send to list.<br>Send to the list: <a ymailto="mailto:LCTG@lists.toku.us" href="mailto:LCTG@lists.toku.us">LCTG@lists.toku.us</a> Message archives: <a href="http://lists.toku.us/private.cgi/lctg-toku.us" target="_blank">http://lists.toku.us/private.cgi/lctg-toku.us</a><br>To subscribe: email <a ymailto="mailto:lctg-subscribe@toku.us" href="mailto:lctg-subscribe@toku.us">lctg-subscribe@toku.us</a> To unsubscribe: email <a ymailto="mailto:lctg-unsubscribe@toku.us" href="mailto:lctg-unsubscribe@toku.us">lctg-unsubscribe@toku.us</a><br>Future and Past meeting information: <a href="http://LCTG.toku.us" target="_blank">http://LCTG.toku.us</a><br>List information: <a href="http://lists.toku.us/listinfo.cgi/lctg-toku.us" target="_blank">http://lists.toku.us/listinfo.cgi/lctg-toku.us</a><br>This message was sent to <a ymailto="mailto:bobprimak@yahoo.com." href="mailto:bobprimak@yahoo.com.">bobprimak@yahoo.com.</a><br>Set your list options: <a href="http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com" target="_blank">http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com</a></div>
</div>
</div></body></html>