From: Dale <rdalek1967@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Formally have Council oversee the Foundation 2.0
Date: Mon, 16 Jan 2017 13:13:33 -0600 [thread overview]
Message-ID: <a5f7ed87-7f40-3135-e517-ecd455e86d1e@gmail.com> (raw)
In-Reply-To: <CAGfcS_nCZUMSnWYDZ-t+sKCjy7A_P13VMMr+=NxZhAiy9jE2Xg@mail.gmail.com>
Rich Freeman wrote:
> On Mon, Jan 16, 2017 at 1:46 PM, Dale <rdalek1967@gmail.com> wrote:
>>
>> That's my thinking as well. If SPI can't be sued, then Gentoo or the top
>> people still in and running Gentoo would be sued.
> Of course SPI can be sued. If I want to sue SPI all I need to do is
> go down to a courtroom and file some papers and pay a filing fee.
> That's what suing somebody is. Now, if I don't have a reasonable
> grounds for the lawsuit it might be quickly dismissed.
>
> Nobody could sue "Gentoo" under the SPI model because "Gentoo" would
> not be a legal entity. They could certainly sue the "top people" in
> it, as they can today.
So nothing changes then.
>> Let's say a dev did something that caused a lawsuit, say violated a
>> copyright or something of that nature. Why would SPI defend that when SPI
>> has no control over what the dev did?
> If SPI was named in the lawsuit they would defend themselves. If they
> weren't named in the lawsuit they wouldn't do anything. If the Gentoo
> project (that is, a loose association of Gentoo developers who have no
> legal existence) told SPI to pay their legal bills using Gentoo's
> money, then they probably would do so.
If SPI is named, they could file to be removed from the lawsuit which
would then leave Gentoo on the hook. Again, what changes?
>> The legal council they have seems to be used to keep SPI legal not
>> the groups underneath them.
> Certainly, but that is all that is needed.
Not hardly. Just because SPI has its legal affairs in order does not
mean the Gentoo people do. That would be when the lawsuit hits Gentoo
not SPI.
>> If a distro, whether it is Debian, Gentoo or
>> someone else, violates someone else or breaks the law, they would have to
>> defend themselves.
> Certainly, though "Debian" is not a legal entity, so it has no need to
> defend itself from a lawsuit, because you can't sue "Debian." Some
> individuals associated with Debian could be sued, and they would have
> to defend themselves from the lawsuit. However, they could only be
> sued for things they're personally responsible for.
>
> If somebody wanted to sue "Debian" they would probably sue SPI,
> because that is who is holding all of Debian's money. Presumably SPI
> operates in such a manner as to make it hard to get it.
>
But SPI does not control Debian and what it does. It doesn't control
its devs either. If one or more devs violate the law with or without it
being common knowledge with other devs, SPI is not on the hook for
that. Debian would be. The money would come from SPI but it would be
Debian's donations paying it either with a court order or Debian telling
SPI to do it. SPI wouldn't be sued because they had no control or say
over what the devs did.
I'm looking forward to seeing what Alec finds out about this. From what
I've read on the SPI website, I don't think this is anything like you
think it is. I think William has already been down this path and based
on what I've read, I think William is right.
Dale
:-) :-)
next prev parent reply other threads:[~2017-01-16 19:13 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 [this message]
2017-01-16 18:46 ` Rich Freeman
2017-01-16 18:52 ` Alec Warner
2017-01-16 19:08 ` Rich Freeman
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=a5f7ed87-7f40-3135-e517-ecd455e86d1e@gmail.com \
--to=rdalek1967@gmail.com \
--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