[BLU/Officers] Face to face meeting

[David Kramer]

I could do that on the 15th but I'll be at Arisia on the 20th still.

On 12/23/19 1:41 PM, Kurt Keville wrote:
> Can you meet on a weekday? Just make a long day of it on Jan 15 ? Or 
> Jan 20, which is a fed holiday?
>
> On Mon, Dec 23, 2019 at 12:47 PM Jerry Feldman <gaf at gapps.blu.org 
> <mailto:gaf at gapps.blu.org>> wrote:
>
>     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.
>
>     --
>     Jerry Feldman <gaf at gapps.blu.org <mailto:gaf at gapps.blu.org>>
>     Boston Linux and Unix
>     PGP key id: 537C5846
>     PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C
>     5846
>
>     On Mon, Dec 23, 2019, 12:22 PM David Kramer <david at thekramers.net
>     <mailto:david at thekramers.net>> wrote:
>
>         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.
>
>         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.
>
>         On 12/8/19 2:15 AM, Bill Horne wrote:
>>         On 12/7/2019 3:41 PM, Jerry Feldman wrote:
>>>         I was talking to Kurt, Bill Ricker and David Kramer. We have
>>>         a few issues. Such as
>>>         It might be time where we should retire the hardware and
>>>         virtualized. I'll try to talk to the guy at Synoptek.
>>         I've been using prgmr.com <http://prgmr.com> for years, and I
>>         recommend them. My yearly server rental is about $120, but
>>         you'll probably want more bandwidth for a BLU server.
>>>         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 blu.org <http://blu.org> should be owned by a
>>>         corporation). And management of the server and web site. We
>>>         probably should use https.
>>
>>         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.
>>
>>         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.
>>
>>         That's my 2¢. YMMV.
>>
>>         Bill Horne
>>
>>
>>
>>         _______________________________________________
>>         Officers mailing list
>>         Officers at blu.org  <mailto:Officers at blu.org>
>>         http://lists.blu.org/mailman/listinfo/officers
>         _______________________________________________
>         Officers mailing list
>         Officers at lists.blu.org <mailto:Officers at lists.blu.org>
>         http://lists.blu.org/mailman/listinfo/officers
>
>     _______________________________________________
>     Officers mailing list
>     Officers at lists.blu.org <mailto:Officers at lists.blu.org>
>     http://lists.blu.org/mailman/listinfo/officers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blu.org/pipermail/officers/attachments/20191223/8d42379a/attachment.html>