From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0FCF5139085 for ; Mon, 16 Jan 2017 19:31:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1F32A21C102; Mon, 16 Jan 2017 19:31:53 +0000 (UTC) Received: from mail2.obsidian-studios.com (mail2.obsidian-studios.com [45.79.71.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B989421C0F3 for ; Mon, 16 Jan 2017 19:31:52 +0000 (UTC) Received: (qmail 18680 invoked from network); 16 Jan 2017 19:31:51 -0000 Received: from unknown (HELO assp2.obsidian-studios.com) (wlt@::ffff:127.0.0.1) by ::ffff:127.0.0.1 with ESMTPA; 16 Jan 2017 19:31:51 -0000 X-Assp-Version: 2.5.3(16294) on assp2.obsidian-studios.com X-Assp-ID: assp2.obsidian-studios.com m1-95111-05487 X-Assp-Session: 3786AACE390 (mail 1) X-Assp-Envelope-From: wlt-ml@o-sinc.com X-Assp-Intended-For: gentoo-project@lists.gentoo.org X-Assp-Server-TLS: yes Received: from unknown ([fdbe:bad:a55:0:1::211] helo=wlt.localnet) by assp2.obsidian-studios.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.5.3); 16 Jan 2017 11:31:50 -0800 From: "William L. Thomson Jr." To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Formally have Council oversee the Foundation 2.0 Date: Mon, 16 Jan 2017 14:31:46 -0500 Message-ID: Organization: Obsidian-Studios, Inc. User-Agent: KMail/5.3.3 (Linux/4.7.5-gentoo; KDE/5.28.0; x86_64; ; ) In-Reply-To: References: <1604622.bZRWYHrp25@pinacolada> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4039472.Tt4iqMPeIp"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-Archives-Salt: 9c3b42be-bd45-4f4b-ad1b-bc4e1a892a78 X-Archives-Hash: f6b3109eb81af8db64ecd16c025f4793 --nextPart4039472.Tt4iqMPeIp Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Monday, January 16, 2017 2:08:36 PM EST Rich Freeman wrote: > > Yes, devs could be sued if they personally did something wrong. That > is true today, it has always been true, and it will always be true. > At best we could pay for insurance to pay for the legal bills and > judgments should such a lawsuit happen. We don't do that today. Short of criminal activity, the Foundation can indemnify Developers, and ta= ke=20 any liability from Developers. Most companies make it very hard if not next to impossible to sue an employ= ee=20 directly for something they did on behalf of their employer. In most cases = it=20 is the employer/company that will be the target of any suit. =2D-=20 William L. Thomson Jr. --nextPart4039472.Tt4iqMPeIp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQTEeldqZjmVut8bVHJNcbKkg6ozUAUCWH0fogAKCRBNcbKkg6oz UI9RAJ9p7NaSi9eMjyKLJutkeQbTcRaoMwCePyCeGqysOJ7Uy7DYWAODUspSO6c= =tZ1d -----END PGP SIGNATURE----- --nextPart4039472.Tt4iqMPeIp--