<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I could do that on the 15th but I'll be at Arisia on the 20th
still.<br>
</p>
<div class="moz-cite-prefix">On 12/23/19 1:41 PM, Kurt Keville
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABn7E3pbrwfvpg0bMUJp4jEAZWJ1=6hwF_Qc2D9kUphbgdpNrA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Can you meet on a weekday? Just make a long day of
it on Jan 15 ? Or Jan 20, which is a fed holiday?<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Dec 23, 2019 at 12:47
PM Jerry Feldman <<a href="mailto:gaf@gapps.blu.org"
moz-do-not-send="true">gaf@gapps.blu.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">I do agree that we should meet face to face.
While I get free gas I don't mind driving across the world
the North Attleboro. <br>
<br>
<div>--<br>
Jerry Feldman <<a href="mailto:gaf@gapps.blu.org"
target="_blank" moz-do-not-send="true">gaf@gapps.blu.org</a>><br>
Boston Linux and Unix<br>
PGP key id: 537C5846<br>
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607
4319 537C 5846</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Dec 23, 2019,
12:22 PM David Kramer <<a
href="mailto:david@thekramers.net" target="_blank"
moz-do-not-send="true">david@thekramers.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>Because I am IT Chairman of Agile New England and
handle all their IT, I've been researching password
managers that are designed for teams. I think that's
a much better solution than yet another geographically
locked solution that will only be accessible by 1 or 2
people with physical keys. <br>
</p>
<p>Back to the start of the thread, we kinda dropped
organizing this meeting, which I think should happen.
Even if we pick late January I think we should pick
that date in the next week or two so it actually
happens.<br>
</p>
<div>On 12/8/19 2:15 AM, Bill Horne wrote:<br>
</div>
<blockquote type="cite"> On 12/7/2019 3:41 PM, Jerry
Feldman wrote:<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-size:large;color:rgb(0,0,255)">I was
talking to Kurt, Bill Ricker and David Kramer.
We have a few issues. Such as</div>
<div class="gmail_default"
style="font-size:large;color:rgb(0,0,255)">It
might be time where we should retire the
hardware and virtualized. I'll try to talk to
the guy at Synoptek. <br>
</div>
</div>
</blockquote>
I've been using <a href="http://prgmr.com"
rel="noreferrer" target="_blank"
moz-do-not-send="true">prgmr.com</a> for years, and
I recommend them. My yearly server rental is about
$120, but you'll probably want more bandwidth for a
BLU server.
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-size:large;color:rgb(0,0,255)">Also,
we need backups for each of us as we are all
aging. One issue is if John goes away, we wont
have access to the domain. (Maybe <a
href="http://blu.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">blu.org</a>
should be owned by a corporation). And
management of the server and web site. We
probably should use https. <br>
</div>
</div>
</blockquote>
<p>I think everyone in the leadership should write out
a list of applicable user id's and passwords, and
put them in a safe-deposit box or fire safe that two
or three people can access: if blu decides on a more
formal arrangement, lawyers will store them for a
nominal fee. As a practical matter, almost all
Domain Name services like GoDaddy can change a
domain's details with only a User ID and password,
so there's little need to incorporate just as a
placeholder for a domain name: incorporation is
expensive, and it requires yearly reports and tax
filings, so I'd avoid it if it were up to me. <br>
</p>
<p>I don't feel that paying for SSL certificates is in
the BLU's best interest: all they do is close the
"lock" icon on the browsers that access the site. I
know that browser designers shill for the X.509
industry, by putting "insecure" warnings on
http-only sites, but I think there are still some
free SSL certs available if the BLU decides it's
essential.<br>
</p>
<p>That's my 2¢. YMMV.</p>
<p>Bill Horne<br>
</p>
<br>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Officers mailing list
<a href="mailto:Officers@blu.org" rel="noreferrer" target="_blank" moz-do-not-send="true">Officers@blu.org</a>
<a href="http://lists.blu.org/mailman/listinfo/officers" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.blu.org/mailman/listinfo/officers</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Officers mailing list<br>
<a href="mailto:Officers@lists.blu.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">Officers@lists.blu.org</a><br>
<a href="http://lists.blu.org/mailman/listinfo/officers"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">http://lists.blu.org/mailman/listinfo/officers</a><br>
</blockquote>
</div>
_______________________________________________<br>
Officers mailing list<br>
<a href="mailto:Officers@lists.blu.org" target="_blank"
moz-do-not-send="true">Officers@lists.blu.org</a><br>
<a href="http://lists.blu.org/mailman/listinfo/officers"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.blu.org/mailman/listinfo/officers</a><br>
</blockquote>
</div>
</blockquote>
</body>
</html>