From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Formally have Council oversee the Foundation 2.0
Date: Mon, 16 Jan 2017 14:08:36 -0500 [thread overview]
Message-ID: <CAGfcS_n+di8nOO9UJCh4pQVajttDYOdncPa+3Tyo=cg_fSKUgg@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr8OGLiGbu92ko95rSeffdSAKOVpX=Vt5YahgxXgw_GefQ@mail.gmail.com>
On Mon, Jan 16, 2017 at 1:52 PM, Alec Warner <antarus@gentoo.org> wrote:
>
>
> SPI reduces the liability of the Gentoo Foundation (since the board and
> officers have specific legal duties that get taken over by SPI.)
SPI eliminates the liability of the Gentoo Foundation, because under
that model there wouldn't be a Gentoo Foundation. It wouldn't have a
board or officers, since it wouldn't exist.
> I don't
> think the SPI changes the liability of the foundation members (who do not
> receive indemnification either way) or non-members.
There would be no members, since there would be no Foundation.
Foundation members in general are not liable for the actions of the
Foundation, just as shareholders in any corporation are generally not
liable for the actions of a corporation. (There are exceptions, but
they're not going to apply here.)
Now, somebody who happens to be a foundation member might be liable if
they happen to also personally do something that exposes them to
liability. If I own a share of Exon-Mobil stock and an employee of
Exon-Mobil hits somebody over the head with a gas can then I bear no
liability because of this association with the corporation. However,
if I were to hit somebody over the head with a gas can then of course
I'd be liable for it. Being a Foundation member neither increases nor
decreases your liability as far as Gentoo is concerned.
Now, being a Trustee or Officer is a different matter.
> So saying "there is no
> Gentoo to sue" to me is disingenuous. For most people on this thread the
> situation is the same; the board and officers encompass only 5 humans.
So, we have to pick which way we're going with things.
Are we of the school that:
There is only one "Gentoo" and it is the Gentoo Foundation, and
everything else is just a legal fiction, and the Foundation is
responsible and in charge of everything as far as the law is
concerned.
or not?
Part of the problem here is that we're using terms loosely, which is
made more complicated by the fact that we're talking about something
that would change the nature of those terms anyway. Gentoo today is
legally a Foundation that owns the trademark on "Gentoo." Under the
proposal "Gentoo" would be nothing more than a trademark owned by SPI.
You can't sue a trademark, only its owner.
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.
However, what we personally do is something we can all control. You
can sue me for things I do wrong. You can't sue me for things others
do wrong. That isn't the same as the situation today, where I as a
developer can do something wrong, and the Foundation could be sued for
it, and now the Trustees have to deal with it, and if they fail to
discharge their duties as Trustees properly they could also be sued.
--
Rich
next prev parent reply other threads:[~2017-01-16 19:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 21:43 [gentoo-project] Formally have Council oversee the Foundation 2.0 Andreas K. Huettel
2017-01-14 23:03 ` Matthew Thode
2017-01-14 23:08 ` Kristian Fiskerstrand
2017-01-14 23:19 ` Matthew Thode
2017-01-14 23:22 ` Kristian Fiskerstrand
2017-01-14 23:25 ` Matthew Thode
2017-01-15 20:26 ` William L. Thomson Jr.
2017-01-15 1:16 ` Rich Freeman
2017-01-15 20:28 ` William L. Thomson Jr.
2017-01-15 21:00 ` Rich Freeman
2017-01-15 22:23 ` Raymond Jennings
2017-01-16 1:01 ` Rich Freeman
2017-01-16 14:56 ` William L. Thomson Jr.
2017-01-15 20:31 ` William L. Thomson Jr.
2017-01-15 20:59 ` Rich Freeman
2017-01-16 14:52 ` William L. Thomson Jr.
2017-01-16 15:06 ` Rich Freeman
2017-01-16 16:31 ` William L. Thomson Jr.
2017-01-16 16:56 ` Rich Freeman
2017-01-16 17:35 ` William L. Thomson Jr.
2017-01-16 17:59 ` Rich Freeman
2017-01-16 18:08 ` William L. Thomson Jr.
2017-01-16 18:23 ` Rich Freeman
2017-01-16 19:10 ` William L. Thomson Jr.
2017-01-16 18:13 ` Dale
2017-01-16 18:19 ` Rich Freeman
2017-01-16 18:25 ` Alec Warner
2017-01-16 18:46 ` Dale
2017-01-16 18:58 ` Rich Freeman
2017-01-16 19:13 ` Dale
2017-01-16 18:46 ` Rich Freeman
2017-01-16 18:52 ` Alec Warner
2017-01-16 19:08 ` Rich Freeman [this message]
2017-01-16 19:20 ` Dale
2017-01-16 19:34 ` William L. Thomson Jr.
2017-01-16 19:54 ` Dale
2017-01-16 20:11 ` Rich Freeman
2017-01-16 20:31 ` Dale
2017-01-16 20:40 ` Rich Freeman
2017-01-16 20:47 ` William L. Thomson Jr.
2017-01-16 20:57 ` Dale
2017-01-16 20:27 ` William L. Thomson Jr.
2017-01-16 20:38 ` Dale
2017-01-16 20:51 ` William L. Thomson Jr.
2017-01-16 21:09 ` Roy Bamford
2017-01-16 19:31 ` William L. Thomson Jr.
2017-01-16 19:20 ` Dale
2017-01-16 18:43 ` Dale
2017-01-16 18:52 ` Rich Freeman
2017-01-16 19:21 ` William L. Thomson Jr.
2017-01-16 19:19 ` William L. Thomson Jr.
2017-01-16 17:50 ` Alec Warner
2017-01-16 18:01 ` Rich Freeman
2017-01-16 18:02 ` Alec Warner
2017-01-16 18:10 ` William L. Thomson Jr.
2017-01-16 20:16 ` Andreas K. Huettel
2017-01-16 20:23 ` M. J. Everitt
2017-01-16 20:27 ` Ciaran McCreesh
2017-01-16 20:42 ` Dale
2017-01-16 21:41 ` William L. Thomson Jr.
2017-01-16 21:37 ` William L. Thomson Jr.
2017-01-16 18:40 ` Matthew Thode
2017-01-16 18:49 ` Dale
2017-01-15 15:00 ` Roy Bamford
2017-01-15 15:30 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_n+di8nOO9UJCh4pQVajttDYOdncPa+3Tyo=cg_fSKUgg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox